- Client
- Izafa Labs (own product)
- Engagement
- Architecture, build, operations
- Stack
- Next.js 16, Supabase, Edge Functions, IndexedDB
- Status
- Beta · 2026 Q2
Most legal case-management software is built by people who have never sat through a Rajasthan High Court hearing. I have, so I built one around what actually breaks there.
Not client work — but I publish it here because the engineering decisions are the same ones I make for clients.
The premise.
NyayHub is built around the constraints that break legal software in India: unreliable Wi-Fi inside court buildings, multi-tenant data segregation across firms, and the fact that lawyers need their interface to load before the judge calls the matter.
The architecture.
A strict multi-tenant isolation model — tenant isolation at the database: row-level security in Postgres on every table that holds tenant data, a separate authentication scope per tenant, and a written audit trail. The frontend is offline-first — cache-first rendering, IndexedDB-first UI, non-blocking realtime, and aggressive query invalidation reduction. The default state assumption is offline; the network is treated as enhancement, not requirement.
What this proves about how I engineer.
Constraints first, features second. Multi-tenancy designed at the database layer, not bolted on. Realtime and offline reconciled at the architecture level, not patched at the component level. This is the engineering posture I bring to client work.