Why the price is settled before you ride
A meter transfers every risk in a taxi trip onto the passenger. Quoting a fixed fare up front moves that risk to us, which changes what we have to build.
A taxi meter is a device for transferring risk. Traffic, a closed road, a driver who takes the long way, a light that stays red — every one of those becomes the passenger’s problem, discovered at the end, with no way to argue about it.
The fixed fare inverts that. We quote a number before you ride, and if the trip takes longer than we estimated, that is our estimate that was wrong, not your bill that goes up.
This is a constraint, not a feature
It is easy to say “fixed fares” on a landing page. What it actually commits you to is harder:
You have to be able to estimate well. The quote comes from driving distance, estimated duration, vehicle class and applicable surcharges. If those estimates are bad, we absorb the difference. That is the correct incentive — it means we are the ones paying for a bad model.
You cannot operate where you do not know the ground. This is why coverage grows region by region rather than switching on nationally. A service region carries its own driver pool, pricing configuration, payment methods and document requirements. We would rather tell someone their town is not live yet than quote a price we cannot stand behind.
You have to compute it in one place. The fare is calculated server-side, never in the app. If the client could compute it, two riders could see two different numbers for the same trip and a modified client could quote itself anything. One calculation, one answer, on the receipt and on the charge.
You have to say no to surge. There is no dynamic multiplier applied after a ride is requested. Regions differ in their configured rates; they do not differ minute to minute because demand moved while you were typing an address.
What it does not mean
It does not mean nothing can ever change what you pay. A cancellation or no-show fee can apply per your region’s rules, and a change made mid-trip can too. Both are things you trigger, and both are the kind of change you can see coming — unlike a meter.
Why we are writing this down
Because the claim is only worth anything if the mechanism behind it is inspectable. So the mechanism is written down: how a fixed fare is calculated, and what we are building toward more broadly.
If it ever stops working the way this post describes, that is a bug, and it is worth telling us about.