For drivers

For the people who
live on the road.

Cab drivers. Auto drivers. Delivery riders. Daily commuters. Saarathi has been shaped by riding along with beta drivers — and rewritten when they told us we'd got it wrong.

Get early access Fleet partners ▾
Real shifts. Real moments.

The four moments that break every other map.

We watched these moments fail, over and over, in beta sessions. So we built around them.

01

Pickup at a side gate.

You arrive at the address. The customer is at the side gate. Google says "you have arrived". Saarathi knows which gate.

"Pull up at the side gate — not the main one. Customer is at 4 o'clock, blue jacket."— Saarathi · Hindi · pickup hint
02

The driver in front has the same map.

So does the truck behind. So does every Ola in a 2 km radius. Google sends everyone the same way. Saarathi knows the gali behind the temple.

"Take the right after the mandir — inner road, no truck. You'll be three minutes ahead of the highway."— Saarathi · Hindi · inner‑lane reroute
03

The customer's address is "near".

"Near the petrol pump." "Near Reliance Smart." Half the addresses on a ride app are landmark‑based. Most maps choke. Saarathi was trained on them.

"Reliance Smart ke peeche wali gali — second cross. I'll narrow it down once you're 300 metres out."— Saarathi · Hindi · landmark resolver
04

No signal. Tunnel. Underpass. 4G drop.

The exact moment you need the next turn is the exact moment the network dies. Voice runs on‑device. Saarathi keeps talking.

"Tunnel mein hain — agla turn 400 metres baad. Don't worry, mujhe pata hai."— Saarathi · Hindi · on‑device, no signal needed
Eyes on the road

Built to be glanced at twice a ride.

Most navigation apps are designed for tapping. Saarathi is designed for not tapping. Voice does the work — your eyes stay on the road, your hands stay on the wheel.

  • 01
    No menus

    Search by saying it. Reroute by asking. Save by speaking.

  • 02
    Turn cues, not metres

    "Right after the temple" — not "in 47 metres".

  • 03
    Night driver mode

    HUD goes amber on dark. Voice slows down on rain. Real defaults.

  • 04
    CarPlay & Android Auto

    On the roadmap, designed for the dashboard from day one.

The questions drivers ask

What it'll cost you to run.

Four honest things every driver wants to know before they install. We're still benchmarking through the beta — exact numbers go here when we have them.

Battery
LighterWe don't stream voice or imagery during navigation, so the draw stays below most streaming map apps. Exact figures from the beta to come.
Data
Mostly cachedFirst drive in a city pulls map data; after that, voice runs on‑device and routing uses the cache.
Voice
On‑deviceSpeech and language understanding run on the phone — no round‑trip to a server, no silence in tunnels.
Works on
Android firstiOS is on the roadmap. We'll publish supported device tiers before the public launch.
Fleet operators

For rideshare, logistics, fleet ops.

If you run more than 20 cars or bikes, talk to us before public launch. Discounted seats, dashboard analytics, and a private channel into our routing team.

  • →Fleet dashboard: time‑to‑destination, rider feedback, lane heatmaps
  • →Private channel for adding landmarks & corrections
  • →SLA on voice latency, in writing
  • →Volume discount, white‑label voice option
Talk to fleet team
Personal useThrough the beta and after
Free
Rideshare & auto driversPricing announced before launch
TBD
Fleet · 20 – 200 vehiclesDashboard, SLA, landmarks API
Talk to us
Fleet · 200+White‑label voice available
Talk to us
Drive the beta

Get on the road. Skip the line.

Tell us you drive — auto, cab, delivery, fleet — and we'll move you up the list. Beta seats are limited; drivers come first.

Drivers get priority access · Tell us your city after signup