Get started
Tell us what you're building. We respond within one business day with a clear plan, price, and timeline.
One backend, three surfaces, one city moved.
Raahi is one product with three surfaces — a rider PWA, a driver console, and a desktop admin dashboard. Every booking flows through one ledger, one auth layer, and one pricing engine so the city's trips reconcile in real time.
Live in your browser — no install, no signup.
One backend, three surfaces, one city moved.
Why one platform
Auth, payments, pricing, and trips share a single source of truth.
Driver location, ETAs, and ops counters update across surfaces in seconds.
Every trip carries a ledger entry the admin dashboard can inspect.
Rider surface
Book a ride. Watch it come to you.
The rider side of Raahi is built for confidence in a city you don't always know. Fare you can see, driver you can watch, payment you can pick — and quick-actions for the trips you take every week.
Driver surface
Heads-up UI for the long shift.
The driver app is what you want one hand on the wheel and one on the phone. Big targets, clear status, and the four numbers that matter — trips today, earnings, online time, and rating — always one glance away.
Admin surface · Desktop-first
The control tower behind every trip.
The Raahi admin is desktop-first because operations teams live in spreadsheets. Live trip board, driver fleet, pricing zones, payouts, and disputes — all wired to the same backend as the rider and driver apps.
The admin dashboard is a desktop experience — open it in a new tab to see the live trip board, fleet console, and payouts in their full glory.
Shared platform
The rider app, the driver console, and the admin dashboard share auth, payments, and a trip ledger — so a booking in any surface is immediately auditable from the others.
Every booking, leg, and payment writes to one append-only ledger that the admin dashboard reads in real time.
Riders and drivers live on the same auth layer, so vetting, suspension, and refunds tie to a single user record.
Base + per-km + per-minute with zone overrides; ops can stage new tables and push them live in a single click.
Live trip stream on the admin dashboard with driver, rider, status, and an inline incident timeline.
Per-driver payout summary tied to the ledger plus a dispute queue rooted in each trip's audit log.
Want one of these?
Tell us the workflow you want on a phone — we'll come back within one business day with a clear plan, price, and timeline.