Software we
put our name on.
Rahviq is a product-engineering studio in India. We take on custom product engineering and AI automation — and the proof we offer is not a portfolio of work we handed over and walked away from. It is two products we designed, built, shipped and still run ourselves.
Everything below is stated at its real status. Where a thing is not built, the slot is empty and says so.
- DocketDesk
- Legal practice management · in development
- AssetDiary
- Family asset register · in development, v1.2.32
- Client engineering
- Open — taking work now
Both products are pre-launch. Neither has paying customers yet, and we would rather you read that here than find out later.
- TypeScript
- React
- Next.js
- React Native
- Expo
- Postgres
- Supabase
- Row-level security
- Vercel
- PWA
Not a capability list — this is what the two products above are actually running on.
Most studios hand it over.
We are still on the hook for ours — the schema, the release, the support inbox, the 2 a.m. page. That is a different kind of engineering than delivery work, and it is the kind we sell.
One place to run an advocate’s practice.
Built for Indian practice rather than translated into it. The vocabulary is matters, cause lists, hearing dates and advocates — not the imported American docket and attorney. Every firm gets a real per-organisation database and its own subdomain, because client confidentiality is a professional obligation, not a feature flag.
- For
- Advocates and firms of 2–40 in India
- Architecture
- Multi-tenant, per-org isolation
- Stack
- React · Supabase · Vercel
- Access
- Onboarded by hand, no self-serve yet
- Clients and contactsIn service
- Invoicing, per-org numberingIn service
- Payments and payment historyIn service
- Invoice email deliveryIn service
- Advocate and team rosterIn service
- Roles and module permissionsIn service
- Per-tenant theming and logosIn service
- Installable PWA, light and darkIn service
Case management and the court-date engine are specified and not yet written. Billing shipped first on purpose — it is the pain that gets a practice to switch. Until these exist, this slot stays empty.
Everything a family owns, in one private place.
Most money apps track only what a bank can see. An Indian household holds far more than that: deposits, gold by weight and purity, land with a payment schedule against it, vehicles, and a drawer of documents. AssetDiary tracks what a family actually holds, with separate logins under one Family ID and per-member permissions.
- Platform
- iOS · Android · installable web
- Built with
- React Native · Expo · Supabase
- Security
- Passcode and biometric lock
- Documents
- Private storage, never a public link
- Deposits, accounts and cashIn service
- Gold and ornaments, by weight and purityIn service
- Property, with payment schedulesIn service
- Vehicles and their paperworkIn service
- Government and bank recordsIn service
- Ledger — earnings, expenses, savingsIn service
- Family logins and per-member accessIn service
The app runs today in a browser and on internal builds. Neither store listing is live, so neither is offered here as a download.
The same hands, pointed at your system.
Two channels. We do not run a menu of everything — cloud migrations, staffing, strategy decks and the rest are other people’s work.
Custom product engineering
Web and mobile products taken from a spec to something shipped and maintained. Schema, interface, releases, and the unglamorous parts — auth, billing, permissions, migrations — that decide whether software survives its first year.
- Greenfield product builds
- Multi-tenant and permissions architecture
- Mobile apps and installable web apps
- Rescue and hardening of an existing build
AI and automation
Language models wired into a business where they earn their keep, and the workflows around them. The interesting engineering is rarely the model — it is the evaluation, the fallbacks, and the boring plumbing that makes it dependable.
- LLM features inside an existing product
- Document and data extraction pipelines
- Internal tooling and assistants
- Workflow automation between systems
How we work.
Four rules we hold ourselves to. They are also the rules our own products are built under, which is the only reason to believe we’ll hold to them on yours.
- 01
Never claim what is not built
Roadmap is labelled roadmap. You have already seen this applied on this page — the empty slots above are real, and we could easily have left them out.
- 02
Ship the painful part first
The module that makes someone switch goes first, not the one that demos best. On DocketDesk that meant billing before case management.
- 03
Speak the user's own language
Cause list, matter, hearing, advocate. Lakh and crore. An interface that renames what a user already knows is making them translate.
- 04
Own it after launch
We stay responsible for what we build. A handover that ends the relationship also ends the incentive to build it properly.
Tell us what you need built.
A paragraph is enough to start. If it is a fit we will say so, and if it is not we will say that instead of booking a call to find out.
Reach us directly at hello@rahviq.com.
- 01
We read it ourselves
There is no sales layer between you and the people who would do the work.
- 02
A straight answer on fit
If it is not something we should build, we say so and tell you what we would do instead.
- 03
A written scope before anything starts
What is being built, what it costs, and what is explicitly out of it.