Robotaxi fleet software for owners: what exists in 2026

Short answer: as of October 26, 2026, no off-the-shelf software runs a privately owned robotaxi end to end. General fleet platforms such as Fleetio, Samsara and Geotab track vehicles, maintenance, fuel and safety for fleets with drivers. Tesla’s Fleet API lets approved developers read data from Tesla vehicles and send them signed commands. Neither parks, charges, cleans or dispatches a driverless car into a ride network. For Tesla’s own Robotaxi fleet, Tesla does that work itself, and it has published no terms for owners’ cars to join.

DockDuty publishes this page and sells depot services to robotaxi owners, so it is not neutral. DockDuty is pre-launch: no DockDuty depot is open, and no site lease is signed. Every outside claim below links to the page we read and the date we read it.

What a robotaxi owner actually needs software for

A driverless car still needs the jobs a driver used to do: energy, cleaning between riders, inspection, staging toward demand, maintenance and incident response (our Cybercab fleet management page lists all six). Software can see most of that and can send commands for some of it. It cannot plug in a charger, wipe a seat or tow a stuck car. That split, between tools that show you the car and people who handle the car, is the thing to keep in mind through the rest of this page. Our post on where to park a fleet of Cybercabs covers the physical side.

General fleet software: Fleetio, Samsara, Geotab

These are the names that come up when someone searches “fleet management software.” Each describes itself in its own words (all three home pages checked October 26, 2026):

• Fleetio calls itself “One place to run fleet maintenance,” with modules for maintenance (“keep service on schedule, repairs on track and costs in check”), fuel data, inspection forms and integrations with telematics providers (fleetio.com).
• Samsara lists fleet telematics (“Real-time GPS, routing, fuel, compliance”), equipment management (“Diagnostics, maintenance, location tracking”), an AI safety platform and AI dash cams (samsara.com). Its OEM telematics page describes pulling data from manufacturers’ own connected systems as an alternative to its hardware.
• Geotab describes telematics as “a method of monitoring cars, trucks, heavy-duty equipment and other assets,” and says its MyGeotab software retrieves real-time charge levels for electric vehicles (geotab.com).

None of the three home pages we read mentions autonomous vehicles or robotaxis. That is not a criticism: they are built for fleets with drivers, where the job is knowing where vehicles are, keeping them maintained and keeping drivers safe. For a privately owned robotaxi, the limits are practical:

• They record work; they do not do it. A maintenance reminder still needs someone to take the car to service. A low-charge alert still needs a charger and someone to plug it in.
• Driver features do not apply. Dash-cam coaching, hours-of-service logs and driver scorecards assume a human at the wheel. In a driverless car there is no driver to coach or log.
• No ride network on the other end. None of the pages we read describes sending a car into a ride-hail network or receiving trips and fares back from one.

Tesla’s Fleet API, in plain terms

Tesla describes Fleet API as “a data and command service providing access to Tesla vehicles and energy devices” for developers working with devices they own or that a customer has authorized them to reach (Tesla developer docs, checked October 26, 2026). What the docs describe:

• What it exposes. Vehicle data, vehicle commands, charging, energy-device, user and partner endpoints. Example commands include starting a charge, locking the doors, flashing the lights, honking and sending a destination to the car’s navigation (vehicle commands, checked October 26, 2026).
• Streaming data. Fleet Telemetry lets vehicles “stream data directly to a server” instead of being polled. The developer runs that server, exposed to the public internet, and the car needs firmware 2024.26 or later (Fleet Telemetry, checked October 26, 2026).
• Registration. A developer needs a Tesla account with multi-factor authentication, then requests app access by giving legal business details, the app’s purpose and the permissions (“scopes”) it wants, hosts a public key on its own domain and registers in each region it operates in. Tesla notes some requests can be automatically rejected (Tesla).
• The owner stays in control. Owners grant an app permission to see account details, check vehicle status or send commands, and can change those permissions at any time (same page).
• Signed commands. For most vehicles, commands must be signed with the app’s virtual key, which the owner pairs to the car in the Tesla app. Tesla’s docs say: “If a command is not signed, the vehicle will reject the request and perform no action.” Tesla publishes a vehicle command proxy that does the signing, and says it is not required for most business vehicles and pre-2021 Model S and X (vehicle commands).
• Cost. Fleet API is pay-per-use, with a $10 monthly discount for individual developers and small apps, and per-vehicle rate limits such as 30 command requests per minute (billing and limits, checked October 26, 2026).

What the Fleet API pages we read do not describe: any way to enroll a car in Tesla’s Robotaxi network, or to send it riders. It is a way for software to see and command a Tesla. It is not a ride network.

Tesla’s Robotaxi network vs. owner tools

Tesla’s Cybercab First Responder Interaction Plan (version 1.2, dated September 3, 2026, checked October 26, 2026) describes Robotaxi as “an autonomous ride-hailing taxi service that enables customers to book rides” and says: “All Robotaxi vehicles are owned and operated by Tesla at this time. Robotaxi Mission Control coordinates and manages rides on Robotaxi vehicles, and handles any charging and maintenance” (Tesla, PDF). So for Tesla’s own cars, the rider app, dispatch, charging and maintenance all sit with Tesla.

For owners’ cars, Tesla has given a spoken target, not terms. On the October 21, 2026 earnings call, Ashok Elluswamy, Tesla’s vice president of AI software, said: “We suspect somewhere around Q2 next year is when we can turn on some of the first customer vehicles to be part of the Robotaxi fleet,” describing the remaining step as making customer cars “part of the geofences and the fleet management that Tesla has.” On the same call Elon Musk said “the vast majority of the Cybercab stuff will be essentially Tesla-owned” (The Motley Fool transcript, October 22, 2026). Tesla has not published eligibility rules, a revenue split, insurance requirements or an onboarding process for owner cars; our Q3 2026 earnings write-up tracks each of those as unpublished.

The practical read for an owner: if and when owner cars join Tesla’s network, Tesla’s own fleet management would decide where and when the car carries riders. What Tesla has not said is who handles the car’s parking, charging and cleaning when it belongs to an owner rather than to Tesla.

Side by side

What each kind of tool does, and what it leaves for an owner of a driverless car. Outside rows are from the pages linked above, checked October 26, 2026.

Where DockDuty fits

DockDuty is not a software-only product and not a ride network. It plans to run the physical side for privately owned robotaxis at a depot: an assigned stall in a fenced lot, on-site DC charging, cleaning and a readiness check between rides, staging toward demand, maintenance coordination and 24-hour incident response, with an owner dashboard on top for trips, charging, documents and statements. To be precise about dispatch: the ride network dispatches the car; a depot makes sure it is charged, clean and available when that happens. The full list of what is and is not included is on what DockDuty handles.

You can click through a demo of the owner dashboard with sample data (no login). Pricing is a monthly retainer per stall plus a per-ride service fee; the current numbers are on the rate card.

Status, plainly: DockDuty is pre-launch. Orlando is the lead market, with its depot targeted for Q4 2026; no lease is signed, no site is secured and no depot is operating. No customer vehicle is in DockDuty’s care. DockDuty is independent. Not affiliated with, endorsed by, sponsored by, or partnered with Tesla, Inc.; “Tesla” and “Cybercab” are trademarks of Tesla, Inc., used here for descriptive reference only.

Comparing companies that offer to run an owner’s robotaxi, rather than software? That is a separate page: robotaxi and Cybercab management companies, compared.

Robotaxi fleet software: FAQ

Is there software that manages a privately owned robotaxi?

Not end to end, as of October 26, 2026. General fleet platforms (Fleetio, Samsara, Geotab) track vehicles, maintenance and fuel, and Tesla’s Fleet API lets approved developers read data and send signed commands to Tesla vehicles. None of them parks, charges, cleans or dispatches a driverless car into a ride network, and Tesla has published no terms for owner cars to join its Robotaxi network.

Can Fleetio or Samsara manage a Cybercab?

They are software for tracking and maintaining fleets. Their home pages, checked October 26, 2026, describe maintenance, fuel, telematics and driver safety, and do not mention autonomous vehicles or robotaxis. They can record that a car needs charging or service; someone else still has to do it.

What is the Tesla Fleet API?

Tesla’s data and command service for its vehicles and energy devices. Developers register, request app access with their business details and the permissions they need, and owners authorize each app. Most vehicle commands must be signed with a virtual key the owner pairs to the car, or the car rejects them. It is pay-per-use.

Does the Tesla Fleet API put a car on the Robotaxi network?

The Fleet API documentation we read on October 26, 2026 describes no way to enroll a car in Tesla’s Robotaxi network or send it riders. Tesla’s Cybercab first responder guide (version 1.2) says all Robotaxi vehicles are owned and operated by Tesla at this time.

When can owners put their own cars on Tesla’s Robotaxi network?

Tesla has not published terms. On its October 21, 2026 earnings call, Ashok Elluswamy said “somewhere around Q2 next year” is when Tesla can turn on some of the first customer vehicles as part of the Robotaxi fleet. That is a spoken target, with no eligibility rules, revenue split or insurance terms published.

Where does DockDuty fit?

DockDuty plans the physical side, a depot that parks, charges, cleans and stages privately owned robotaxis and handles incidents, plus an owner dashboard. It is pre-launch: Orlando is the lead market with a depot targeted for Q4 2026, no lease is signed and no depot is operating. The ride network, not DockDuty, dispatches the car.