Tavra Labs
← Back to site

Technical case studies

How we engineer products we build and own: the constraints we accepted, the architecture we chose and the trade-offs we made.

Legal tech · Own product · Pilot · 2026

PetitionOS

Registry-ready in minutes: a court-filing engine for the High Court of Karnataka that runs entirely in the browser.

Problem
Filing bundles assembled by hand in Word drift from the Registry's formatting rules and come back close to deadlines.
Architecture
Typst compiled to WebAssembly in a Web Worker; pdf-lib assembles the bundle with scanned annexures. The server handles only sign-in.
Key decision
Deterministic layout over AI drafting: the same facts always produce the same pages.
Ownership
Tavra Labs' own product: designed, engineered and operated by us, from feasibility to pilot.
  • React 19
  • TypeScript
  • Typst · WASM
  • pdf-lib
  • Cloudflare Pages

Read the case study →

Venue operations · Client build · Live · 2026

Shree Gowri Shankara

A Kannada-first booking, payment and receipt system that runs a wedding hall from first enquiry to final receipt.

Problem
Dates, advances, balances and three businesses' receipts kept in a handwritten register, in Kannada, across a financial year.
Architecture
Next.js on Vercel talking straight to Firestore. Security rules are the access control; there is no server code to run.
Key decision
One write path for money: every payment fans out into numbered receipts per business, in one transaction.
Client
Shree Gowri Shankara Kalyana Mantapa, Hanur, Karnataka. Live in production.
  • Next.js 16
  • React 19
  • TypeScript
  • Firestore
  • Vercel

Read the case study →

More products we've built

Shorter write-ups for now. Full technical case studies are on the way.

Design & prototyping studio · Bengaluru

3KONA ↗

A product platform for a design and 3D printing studio, so prospects understand the work and reach the team with serious enquiries.

Problem

The studio needed a clear way to present capabilities, show real work and take quote requests without losing enquiries across channels.

What we built

A product presence shaped around how 3KONA operates: capabilities, selected work and quote requests that feed into their intake. They own the product, content and workflow.

What changed

Prospects move from discovery to a quote request in one place, and enquiries land with the studio instead of scattering across messages.

Building a product with hard constraints?

Regulated documents, privacy-first data, rules that have to become software. Talk to the engineers who'll build it.

Talk to an engineer →