Robotaxi fleet management software: the complete guide
Robotaxi fleet management software is the control layer that runs a fleet of driverless taxis as a business: it assigns rides to vehicles, monitors every car's state in real time, escalates unusual situations to remote human operators, schedules charging and cleaning at the depot, and produces the safety and compliance records regulators expect. The autonomous driving system inside each car handles steering and braking; the fleet platform handles everything a taxi company's dispatchers, mechanics and managers used to coordinate by phone and habit. The two layers are separate products, and the fleet layer is where a taxi operator keeps its leverage: local demand knowledge, depot infrastructure and operations staff. At scale the pattern is visible in operators like Waymo, which coordinates 500,000 paid rides per week across 10 cities through exactly this kind of platform sitting above the vehicles.
Why does a driverless fleet need its own software layer?
A human driver is a distributed operations department. One person accepts orders, chooses waiting spots, notices a strange noise, decides when to refuel, cleans the seats and calls the office when something breaks. Remove the driver and none of those decisions disappear; they concentrate in software. Understanding what a robotaxi is makes the split clear: the car drives itself, and the fleet platform runs the business around it.
The consequence for cost is direct. Analyst models project robotaxi operating costs on a path toward $0.25 to $0.35 per mile against $1.50 to $2.00 for human-driven ride-hail, and most of that gap survives only if the software layer keeps utilization high and downtime short.
What does the dispatch module do?
Dispatch for driverless cars looks like classic taxi dispatch with the human negotiation removed. The platform matches each ride request to a vehicle using battery state, position, and predicted demand, with no acceptance step and no shift schedule. It rebalances idle cars toward zones where orders will appear, sequences pickups to cut empty kilometers, and routes around closures using the fleet's own recent traces.
Key dispatch functions:
- Ride matching with battery and position constraints
- Predictive rebalancing between city zones
- Routing that learns from the fleet's own trips
- Hybrid mode: human-driven and autonomous cars in one queue
The hybrid queue is the part that matters for an existing operator. A company does not switch to autonomy in one day; it runs both kinds of vehicles side by side for years, and the dispatch layer has to treat them as one fleet. That transition path is the subject of our guide to adding autonomous vehicles to an existing fleet.
What is vehicle telemetry for?
Telemetry is the fleet's nervous system. Every vehicle streams battery level, sensor health, door state, cabin camera flags, tire pressure and software version to one screen. The platform turns the stream into alerts with thresholds: a battery trending low before a long trip, a sensor reporting degraded range, a door that failed to latch. Operations staff see problems before passengers do, and maintenance moves from a fixed calendar to condition-based scheduling.
How does remote assistance fit in?
No automated driving system resolves every scene alone. When a car meets an ambiguous construction layout or a police officer directing traffic by hand, it asks for help, and a remote operator answers with context and guidance. Waymo's Fleet Response works this way: the agent responds to the vehicle's questions while the vehicle keeps control, and reported staffing sits near 70 remote assistants for roughly 3,000 cars. The fleet platform's job is queueing those escalations, giving the operator the right camera views instantly, and logging every intervention. The full picture of how this desk works is in remote assistance for driverless fleets.
What happens at the depot?
Robotaxi fleets today are electric, so the depot is a charging operation with a cleaning and maintenance line attached. The software plans charging windows against demand forecasts so cars top up when the city is quiet, books cleaning slots between peaks, and sequences maintenance so the fewest vehicles are offline at once. Depot planning is a scheduling problem the platform solves continuously, and we walk through a full day of it in depot operations.
What records does the platform keep?
Every trip produces a log: route, events, interventions, incidents. The UN's draft global regulation for automated driving, adopted by the UNECE working party in January 2026, is built on a safety-case approach with a safety management system across the vehicle's life, which in practice means operators must show documented, auditable fleet records. A fleet platform generates that documentation from live data instead of reconstructing it by hand after the fact.
Module summary
| Module | Replaces | Core output |
|---|---|---|
| Dispatch and ride matching | Dispatcher and driver decisions | Assigned, routed, balanced rides |
| Telemetry | Driver's eyes and ears | Live vehicle state, alerts |
| Remote assistance | Driver judgment in edge cases | Resolved escalations, logs |
| Depot and charging | Refueling habits, garage planning | Charging, cleaning, maintenance schedule |
| Safety and compliance | Paper trip sheets | Trip logs, incident reports, audit files |
Where aiTAXI fits
aiTAXI is a robotaxi fleet management platform by aiNOW (Tbilisi, Georgia): the five modules above in one console, designed for taxi companies that plan to run hybrid fleets in smaller markets rather than for operators building everything in-house. The platform is in early access, and the robotaxi fleet management platform pilot is open for Georgian taxi companies that want to shape the first integration.
FAQ
Is fleet management software the same as the self-driving system?
No. The automated driving system lives in the vehicle and does the driving. Fleet management software lives in the cloud and runs the business: rides, monitoring, depot, records. Operators need both, from the same or different vendors.
Can one platform manage vehicles from different manufacturers?
That is the goal of vehicle-agnostic platforms. Integration happens per AV platform through APIs for ride assignment, state streaming and assistance escalation, so a fleet can mix vehicle sources as the market matures.
Does the software drive the car remotely?
No. In the standard model the vehicle always keeps control. Remote operators answer questions and give guidance; direct joystick driving is not part of mainstream robotaxi operations.
What does a taxi company gain by adopting the fleet layer early?
Operational readiness. Dispatchers learn the console on the existing human-driven fleet, data starts accumulating, and when autonomous vehicles arrive in the market the company plugs them into a running operation instead of starting from zero.