Free tool
Your optimal surgemultiplier — explained
Sharp enough to reward drivers. Gentle enough not to scare passengers. Slide the controls and see what TaxiDex would charge in real time.
Market conditions
Slide the controls to a moment in your week — a rainy rush hour, a stadium let-out, New Year's Eve — and watch the fare TaxiDex would quote update live.
Model: optimal = base × (1 + demand × 0.4 + shortage × 0.6), then clamped to your cap. Tuned from 48M completed TaxiDex rides across 7+ verticals.
Final fare passenger sees
$17.80
TaxiDex applies your own caps and floors. Surge audit logs are exportable per ride.
48M
Rides behind the model
7+
Verticals tuned
2.5×
Typical surge cap
100%
Decisions auditable
Surge best practices
How TaxiDex handles surge responsibly
Dynamic pricing only works long-term if it's fair, defensible, and predictable. TaxiDex is built so a surge event protects your driver supply without burning trust with riders or regulators.
Caps & floors
You set the maximum surge — say 2.5× — and a floor below which no surge ever fires. Passengers never face shock pricing, and your team never has to apologise for a fare that ran away. The cap is enforced by the fare engine on the server, so a misconfigured zone or a runaway demand signal can never exceed the ceiling you signed off on.
- Per-zone and per-vehicle-type ceilings
- Surge suppressed entirely below your floor
- Ceiling enforced server-side, never on the device
Explainable audit log
Every surge decision is logged with the exact signals that fired it — demand, live driver shortage, time-of-day rule, weather or event window — and the multiplier that resulted. Defend the price to a regulator, a corporate client, or an angry passenger with a timestamped record instead of a shrug. Logs are exportable per ride.
- Signals + multiplier stored against every booking
- Exportable per ride for disputes and compliance
- Reproducible: the same inputs always yield the same fare
VIP & corporate exemptions
Surge is automatically suppressed for corporate accounts, contract clients, and VIP customers. Your highest-value riders get a consistent, predictable fare while the open market clears at the rate it needs to — so a surge event protects your driver supply without alienating the accounts that pay your invoices on time.
- Per-account and per-tier exemption rules
- Contract fares stay fixed during surge windows
- VIP riders shielded automatically, no manual overrides
Inside the console
Surge rules you can see, tune, and trust
Surge in TaxiDex isn't a hidden algorithm — it's a set of rules your team configures and an engine your team can audit. Define demand thresholds, attach them to zones drawn on a live map, layer time-of-day and event windows on top, and set the cap and floor that keep every fare inside the bounds you approved.
When the market tightens, the fare engine reads live demand and driver-coverage signals, computes the multiplier, clamps it to your ceiling, and writes the decision to an exportable audit log. Because it's deterministic and server-side, the price a passenger sees is always one you can reproduce and explain.
The fare engine behind it
One enterprise fare engine, fully under your control
The simulator above models a single surge multiplier. In production, surge is just one input to TaxiDex's unified fare engine — all backend-computed, all auditable, all yours to configure.
Questions
Surge pricing, answered
How the model works, what it does and doesn't promise, and how TaxiDex keeps dynamic pricing fair.
How is the surge multiplier in this simulator calculated?
The tool uses the same shape as TaxiDex's production model: optimal multiplier = 1 + (demand × 0.4) + (driver shortage × 0.6), then clamped to the surge cap you set. Demand reflects how busy the market is (1.0 is a normal hour, 3.0 is something like New Year's Eve) and driver shortage is the share of demand you can't currently cover. The result is applied to your base fare to show the price a passenger would actually see.
Is this the exact pricing TaxiDex will charge my passengers?
No — it's an illustrative simulator to help you reason about surge before a demo. Your live fares depend on your own caps, floors, zone pricing, surcharges, per-region tax, and any account exemptions, all of which the TaxiDex fare engine computes and audits on the server. On a demo we configure those rules to your market so the numbers reflect your real fares.
Can I cap surge so passengers never see shock pricing?
Yes. You set a maximum multiplier (for example 2.5×) and a floor below which surge never fires. The cap is enforced by the fare engine server-side, so no zone misconfiguration or runaway demand signal can ever produce a fare above the ceiling you approved. You can set different caps per zone and per vehicle type.
How do I justify surge pricing to regulators or customers?
Every surge decision is logged with the signals that triggered it and the resulting multiplier, stored against the booking and exportable per ride. Because the model is deterministic, the same inputs always reproduce the same fare — so you can show exactly why a price was what it was, rather than relying on a black box.
Can corporate and VIP riders be exempted from surge?
Yes. Surge is automatically suppressed for corporate accounts, contract clients, and VIP tiers. Those riders get consistent, predictable fares while the open market clears at the rate it needs to protect driver supply — exemptions are rule-based, so no operator has to override fares by hand during a surge event.
Configure surge for your market on a demo
30 minutes. We'll set up caps, floors, exemptions, and surge zones for your fleet live — on your zones, your fares, your accounts.