What's mocked
Independent hackathon prototype for all of India; three demo citizens live in Bengaluru, Karnataka and one in Pune, Maharashtra. Not affiliated with the Ministry of Road Transport & Highways, Parivahan, Sarathi, Vahan or any state transport department.
- Login by plate / licence / “I’m new”, with the stale-number → Aadhaar fix
- The Feed: priority order, consequence lines, filters, pay-all, snooze (guarded), calendar, explain
- Challan case file: photo, map, rule, options; pay → receipt → timeline; contest (with “were you driving?”) → filed → tracked; already paid; sold
- Virtual Court item explained
- Licence renewal: preflight, cost cliffs, Form 1A, pay, “we filed Form 9 + 1A”
- PUC: nearest centres on a map, hold a time, mark done
- Bank removal from RC: NOC check, pay, Form 35
- Vehicle transfer: readiness check with live blockers, seller steps, Arjun confirms from his account, both trackers update
- Messages with real/fake SMS check
- Quick checks on the home page without login
- Plan your errand, services catalogue and 12 service pages: generated from the same rules as the app
- Intent search incl. form numbers; free text → model
- Documents / police-stop mode
- Reset demo
- OTP (any 4 digits) and Aadhaar verification
- All people, plates, challans, photos (illustrated), places: no real data
- Payments (UPI sheet): no money moves
- Government systems: Vahan, Sarathi, eChallan, Virtual Court, police feeds, IIB, PUC database, bank lien registry: nothing is called
- Message delivery (shown in-app; real channel would be SMS/WhatsApp). WhatsApp / SMS / helpline channels on service pages are planned, not built
- PUC “hold a time”: real PUC is walk-in; the hold is a convenience
- Maps: schematic, not to scale; QR codes: decorative, not scannable; every picture is a labelled dummy image
- Court and RTO timelines: expected dates, they don’t auto-advance
- Ravi → Arjun transfer: works in the same browser (log out, log in as Arjun); no shared server state
- Fine and fee amounts: indicative; the rules file uses Karnataka's schedule (Priya's Maharashtra challan uses an amount that matches the MH schedule, but the underlying rules file is Karnataka-sourced; a real rollout is one rules file per state)
- Authority names (Bengaluru Traffic Police, HDFC Bank, RTOs): illustrative labels, no affiliation
- Campaign and update cards on the home page: illustrative content
- Contest SLA (30 working days, refund in 5 days), renewal windows, late-fee ladder and “Next” steps: from the rules file, indicative; refund to a UPI ID is mocked
- Transfer Reject / Withdraw: reversible only until the buyer confirms, as at a real RTO
- The model’s answers when no API key is configured: pre-written fallbacks, marked “offline”
Park+, Paytm and ACKO built the challan-checking screen the official system never did, but they stop at reading. Nirvahan is built to act: pay and contest, every document and deadline rather than challans alone, warnings before the fine instead of a lookup after it, no ads and no data resale. The comparison we are making is with Parivahan itself, not with them.
Next.js, React, Tailwind CSS, Lucide icons (ISC), Google Fonts: Inter, Fragment Mono, Anton (OFL). OpenAI API for four grounded language jobs. Hosted on Vercel. No cookies, no analytics, nothing stored server-side. All illustrations are inline SVG placeholders.