- Date:
- 2026 – present
- Status:
- [live] ruxs.in
- Stack:
- Next.js 16, Cloudflare Workers (OpenNext), PostgreSQL, Drizzle, Bun, Playwright
- Role:
- Founder; sole engineer
Subject: RUXs: replacing a vendor's WhatsApp chats and paper khata
In Indian neighbourhoods, daily tiffin, milk and 20-litre water cans run on WhatsApp messages and a paper ledger (a khata). RUXs puts that routine in one web app: households skip or confirm a day, the vendor gets a locked count at the cutoff, and both sides see the same ledger and one bill a month.
The problem
A tiffin vendor with 80 customers reconciles skips, extra meals and payments by hand every evening. Mistakes cost money on both sides, and nobody trusts the other's notebook.
What I built
- Four route groups in one Next.js app: a public site, the household app, a merchant panel and an admin console, each with its own access rules.
- Daily skip-or-confirm with a cutoff that locks the kitchen count, a driver run sheet, a shared ledger and a monthly UPI bill.
- A wider marketplace on the same core: local stores, children's classes and kits, fitness and physiotherapy. Each vendor type turns on only the workflows it needs.
- A per-minute Worker cron for scheduled jobs, and Playwright end-to-end tests over the main flows.
Decisions
- The vendor pays; households and delivery staff use it free. Households don't even need an account: they get one private link to their khata and bills.
- Money and fulfilment correctness come before visual polish. Prices, schedules and service areas always come from the provider, never a platform-wide default.
- Kids' services shipped with a written child-safeguarding policy, and I ran my own security and route audits before opening them up.
What I took from it
The hard part of local commerce is not the catalogue. It is the daily state machine: who skipped, what got delivered, what is owed. Getting that right is what earns a vendor's trust.
Live: ruxs.in
Code: playlikeboy/ruxs