Alternatives
ZervX Alternatives for Fleet Operators
ZervX sells a white-label ride-hailing stack on flat monthly ride buckets — commonly quoted around $300 to $600 for three to eight thousand rides, though you should check your own quote. It suits launch-stage marketplaces that want an app on the street quickly. Operators start shopping when the bucket stops matching the business: rides pre-bought and unused, a ceiling crossed mid-month, or a dispatch desk the app-hailing model was never designed around.
The trigger
Why operators start looking past ZervX
You buy the rides before you run them
The bucket is pre-paid capacity. A fleet ramping from a standing start pays the entry tier — commonly quoted near $300 a month, indicative only — whether it completes two hundred rides or three thousand. Early-stage cost per ride is therefore highest exactly when cash is tightest, and the money is spent on headroom rather than on supply.
The meter is trips, not the fleet
Ride-count billing charges the same for a four-minute school hop as for a long airport run, so the model quietly penalises high-frequency, low-value work. Two operators with very different driver counts and very different revenue per trip can land on the same invoice. Before signing, get in writing what counts as a ride — cancellations, no-shows and rebookings included or not.
Ceilings arrive as steps, not slopes
Crossing a bucket boundary is a jump, not an increment — the published tiers are commonly quoted at roughly three thousand and eight thousand rides. A seasonal fleet whose December doubles its August either carries the higher tier for twelve months or manages tier changes as an ongoing admin job. Growth is billed in blocks rather than tracking demand.
Built around app-hailing, not a dispatch desk
The product is shaped by the on-demand marketplace model: rider opens app, driver accepts, trip completes. If most of your work arrives by phone, is booked days ahead, is invoiced monthly to account customers, or is a fixed school contract, ask the demo to run those flows end to end rather than assuming a hailing stack covers them.
The other side
When staying on ZervX is the right call
Stay if your supply is loose and numerous: hundreds of independent drivers, each doing a handful of trips. Per-driver billing is the wrong meter for that shape, and buckets are simply cheaper arithmetic. Stay too if rides, delivery and rentals run on one stack under one bill — TaxiDex does not do that.
The options
What operators actually move to
TaxiDex
That’s usFleets with a settled driver roster taking phone, app and account bookings
Billed per active driver — £11/$14 up to twenty drivers, £9/$11 to a hundred, from £7/$9 above, with a £79/$100 monthly minimum and a 14-day trial. Setup is one-time, scoped on the demo call. Your passenger app and web booker carry your brand; the driver app is TaxiDex-branded. No ride ceiling.
Onde
Launch-stage marketplaces with unpredictable volume that want cost to move with revenue
Onde is white-label ride-hailing built on the same marketplace assumptions as ZervX, but its commercials are commonly quoted as a low base fee plus a variable per-ride or revenue share — indicative, confirm directly. If you cannot forecast volume, a meter that idles when you do beats a bucket you pre-pay.
TaxiCaller
Small fleets running very high trip counts per car, where branding is secondary
Per-active-vehicle cloud dispatch with no trip caps — commonly quoted around $28–29 per vehicle, indicative only. Twelve cars grinding out thousands of short trips are billed on twelve meters, not on the trips, which beats both buckets and per-driver pricing. The catch is branding: a white-label passenger app is typically a separate one-time cost.
Autocab
UK operators whose growth depends on inbound work from an affiliate network
Autocab's value is the work-exchange network between member fleets, not the software alone. If overflow jobs passed between operators are a real revenue line for you, weigh that heavily — a network accrues over years and no newer platform can hand you one. Pricing is quote-only; we hold no price sheet, so treat figures quoted elsewhere sceptically.
Competitor pricing and terms quoted anywhere on this site are indicative market figures, not quotations we hold. Confirm the current number, and the line items around it, directly with the vendor.
Practicalities
What moving off ZervX involves
ZervX is cloud-hosted and commonly sold monthly, so notice is rarely the constraint — app-store republication is. Ask for a CSV or SQL export of riders with saved addresses, drivers, vehicles, tariffs and full trip history, and check whether rider and driver wallet balances come out as ledgers you can reconcile. Branded apps ship under new bundle IDs, so riders re-download.
If the trigger was the renewal quote rather than the software, the anatomy of that bill is broken down separately in what ZervX actually costs — the billing unit, and the charges that sit outside the headline rate.
The mechanics are the same whichever platform you land on: export and establish what you actually own while you are still a paying customer, then run both systems in parallel and cut over shift by shift with the old one still licensed behind you. That method is published in full as the 14-day migration protocol.
Free guide
Score them all on the same scale
The buyer's guide is the requirements worksheet and weighted scorecard we use — vendor-neutral, so it works just as well for shortlisting someone other than us.
Is TaxiDex cheaper than ZervX?
It depends entirely on which meter fits you, and the arithmetic is quick. TaxiDex is £11 per active driver up to twenty drivers, £9 from twenty-one to a hundred, and from £7 above that, with a £79/$100 monthly minimum. ZervX's flat buckets are commonly quoted at $300 to $600 — indicative only, check your own quote. Divide their quote by your active driver count: if it comes out under our per-driver rate, they are cheaper for your shape.
Does ZervX charge per driver or per ride?
Its published model is commonly described as flat monthly ride allowances rather than a per-driver licence — that is the core difference and it decides who each platform suits. Ride metering favours operators with many lightly-used drivers, because supply is free and only completed trips count. Per-driver metering favours operators whose drivers work full shifts, because a busy driver costs the same as an idle one. Neither is generous; they are different bets.
Can I keep my branded passenger app if I move?
You keep the brand, not the build. On TaxiDex the passenger app and web booker carry your operator branding; the driver app is always TaxiDex-branded, and we would rather say that plainly than let you find out at launch. Practically, a new passenger app is published under new bundle identifiers, so existing riders re-download rather than update. Plan the rider comms alongside the cutover, not after it.
How long does moving off ZervX take?
We publish a 14-day migration protocol and follow it rather than promising a date. Days one to three are export, reconciliation and pricing twenty historical jobs through both systems until fares match. Days four to ten run both platforms live, with the old one authoritative. Days eleven to fourteen cut over shift by shift, old system still licensed as rollback. We do not promise zero downtime, and nobody honest does.
I run rides and deliveries — should I still look at TaxiDex?
Probably not, if deliveries are a genuine second business rather than an occasional parcel. TaxiDex is built for passenger transport: dispatch, tariffs, corporate accounts, driver settlements, flight tracking. Multi-vertical platforms like ZervX exist precisely because running rides, food and rentals on one stack under one bill is awkward otherwise. Choosing us there would mean running two systems, and that is usually worse than an imperfect bucket.
Comparing ZervX with TaxiDex?
Bring your driver count, your current rate and your contract end date. We will tell you on the call whether switching is worth it for your fleet — including when it is not.