Purvex
An aerial view of a coastline where turquoise water meets red sand.
We engineer systems
that do not go down.
The studio

Purvex Labs builds backends, AI features and apps that have to keep working: job queues that survive crashed workers, real-time tools, and the software a team opens every morning. Everything below is shipped and running.

Work

Shipped, running,
and measured

  1. 01 — Client work · City Fire Services India · 2025–26

    Marka

    The attendance and payroll platform the whole company runs on: two Flutter apps and a Next.js admin portal on Supabase. GPS-verified check-in with biometrics, a live crew map, on-device OCR for expense receipts, leave approvals and salary slips that calculate themselves.

    employees use it daily
    20 / 20
    employees use it daily
    apps on one Postgres, RLS on every table
    3
    apps on one Postgres, RLS on every table

    Flutter · Next.js · TypeScript · Supabase · Mapbox · ML Kit

    Marka's employee app showing a GPS-verified check-in at a site in Noida.
  2. 02 — Own product · open source

    RelayQ

    A multi-tenant background-job service built to survive workers being killed mid-job. A transactional outbox and an idempotent effect log mean a crash never loses or repeats work. LLM jobs get per-tenant budgets, fallback models and a cost ledger.

    jobs per minute on one laptop
    33,424
    jobs per minute on one laptop
    lost or duplicated across 10k jobs and 10 worker kills
    0
    lost or duplicated across 10k jobs and 10 worker kills

    TypeScript · Node.js · BullMQ · Redis · PostgreSQL · OpenTelemetry · AWS

    RelayQ's demo: jobs drawn as boulders that workers push up a hill, with the queue, Postgres and webhook labelled.
  3. 03 — Own product · open source

    PulseBoard

    A real-time Kanban board with live cursors and an "Ask the board" assistant that answers with citations. Hybrid search (pgvector plus full-text, fused with RRF), LLM evals that fail CI on regressions, deployed to ECS Fargate behind CloudFront with CDK.

    p95 with 100 live users on two 0.25-vCPU tasks
    78.5 ms
    p95 with 100 live users on two 0.25-vCPU tasks
    Recall@5, with 10 of 10 prompt-injection attacks resisted
    0.957
    Recall@5, with 10 of 10 prompt-injection attacks resisted

    Next.js · Socket.io · PostgreSQL · pgvector · Redis · Bedrock · AWS CDK

    PulseBoard's Kanban board with the Ask the board panel answering a question and citing the cards it used.
  4. 04 — Team project · I built the simulation core

    Urban Policy Simulation

    An agent-based model for testing zoning, transit and housing policy before it is enacted. Commuters move over Delhi's real road network, with congestion calibrated against RITES mode-share and DMRC ridership data.

    commuter agents on Delhi's road network
    5,000
    commuter agents on Delhi's road network
    travel modes, BPR congestion model
    8
    travel modes, BPR congestion model

    Python · Mesa · OSMnx · FastAPI · Next.js

    The Policy Simulation Engine landing screen, with a particle cloud behind the title.
Purav Bhatt sitting on a log in a pine forest.
Who you work with

Purav Bhatt

Founder · Full-stack & AI engineer · Delhi

I started Purvex Labs to do the kind of work I like best: backends that keep running when something breaks, AI features that cite their sources, and apps people open every morning.

Before this I built Marka for City Fire Services, which their whole team now uses daily, and before that I built data pipelines for a graph neural network research group at IIIT Delhi.

How we work

We start by reading
your code

Before we build

We audit the running system first: the code, the data model, the deploy path and the incidents you already know about.

We decide the interface and the architecture together, so whatever you sign off on can actually run on your infrastructure.

We load-test for the traffic you expect, fix whatever bends, and only then ship it.

While we build

Every Friday there is a deployed build you can click through, with a short note on what changed.

Your repo, your board, your code review. You see every commit as it lands.

Architecture docs, runbooks and a walkthrough with your team, so they can run it after we leave.

What we do

Four disciplines,
one delivery team

Scalable Systems

Distributed architecture, event pipelines and data models sized for the traffic you expect over the next few years.

UI/UX Design

Interaction and visual systems built as real components from day one, so the design survives contact with engineering.

Web Development

Fast, accessible front ends that search engines can read. We pick server or client rendering route by route.

App Development

Cross-platform products with offline-first sync and a release process that does not require heroics.

A single peak lit from behind at first light.
Start here
Ready to build something that holds?