Skip to content
Driverless Transportation

Briefing · Robotaxi

What 'Public Driverless Service' Actually Requires, Operator by Operator

Every operator uses similar language. The permit conditions behind that language are not identical.

Briefing

Waymo, Zoox, and every other operator in this space reach for roughly the same vocabulary: driverless, autonomous, self-driving, robotaxi. The permit conditions and operational realities behind that vocabulary are not identical, and the gap between announcing a launch and letting an ordinary member of the public hail a vehicle with nobody from the company inside it is where a lot of the confusion in press coverage comes from.

That second description is the actual bar this site's tracker uses for public driverless service. It's a narrow definition on purpose. A member of the public, not an employee, not a journalist on a press ride, not a friend-and-family tester, has to be able to open an app, request a ride, and get into a vehicle with no one from the operator sitting in it.

Plenty of real milestones fall short of that bar without being meaningless. Employee-only pilots test the software against real internal riders before opening to strangers. Safety-operator demonstrations let a company show regulators and the press what the system does under supervision. Press rides generate coverage and, often, the first public sense of what riding in the vehicle actually feels like. All of these matter. None of them is the same claim as public driverless service, and treating them interchangeably flattens a distinction that regulators themselves generally don't flatten.

Between an employee-only pilot and unrestricted public access sits another common stage: a public waitlist. A member of the public can sign up and eventually get invited in, but access is still gated and rationed, sometimes for months, before anyone who downloads the app can simply request a ride. That's closer to the public-service bar than a press ride or a safety-operator demo, since a real stranger does eventually get in the vehicle, but it's still a narrower claim than open access, and a company's own announcement doesn't always make clear which of the two it's describing.

Hours of operation and coverage area are a related, and easy to miss, qualifier on top of that. A service that only operates driverless rides during daylight hours, or only within a fraction of a metro area's total geofence, is making a narrower public-service claim than one running around the clock across its full mapped territory, even if both would get described with the same word, launched, in a headline. None of that makes an hours-limited or waitlist-gated service meaningless as a milestone; it just means the milestone needs to be read for what it specifically grants rather than assumed to mean full, unrestricted access.

A vehicle with nobody in the driver's seat is not necessarily unmonitored altogether, either. Many operators pair a driverless fleet with a remote assistance center that can offer guidance when a vehicle encounters an ambiguous situation, even though that person isn't riding inside the car and can't take over steering and braking directly. Whether that counts as fully unattended operation is more a matter of definition than of the public-access bar this site applies, which cares only about whether a company employee is physically present in the vehicle a stranger gets into, not about what support exists behind the scenes.

Comparing operators fairly means running each one through the same test rather than taking each company's own press release at face value; a company that calls a safety-operator demo a launch is using the word differently than one that means an app a stranger can download today. This site's robotaxi deployment tracker applies the narrower bar consistently across every operator it lists, which sometimes puts a company further behind than its own announcements suggest.

Whether that's a fair way to keep score is itself a reasonable question. It's at least a consistent one.

All briefings are reference and analysis pieces, distinct from the 2013–2018 news archive.

Questions

What bar does this site use to call a service public driverless service?

A member of the public, not an employee, journalist, or friend-and-family tester, has to be able to open an app, request a ride, and get into a vehicle with no one from the operator sitting inside it.

Is a robotaxi service with a waitlist considered publicly available?

It's closer to public availability than an employee-only pilot or a press ride, since a genuine stranger does eventually get a ride, but it's still a narrower claim than open access, since the company keeps controlling who and how many people get in at a given time.

Does operating only during certain hours disqualify a service from being called public?

Not entirely, but it's a real qualifier worth noting. A service limited to daytime hours or a partial geofence is making a narrower claim than one running around the clock across its full territory, even if both get described the same way in a press release.

Why do companies sometimes blur the line between a demo and a public launch?

A safety-operator demonstration or a press ride generates coverage similar to what an actual launch would, which creates an incentive to describe an earlier-stage milestone using launch-adjacent language even when access remains restricted.

Does an employee-only pilot count as evidence the technology works?

It's a legitimate step in validating software against real internal riders, but it's a different claim than public availability, since employees are a controlled population a company can brief and survey differently than an anonymous stranger off the street.

How does this site's deployment tracker decide when to mark a city as launched?

It applies the narrower public-access bar consistently across every operator rather than accepting each company's own description of its own milestone, which sometimes places a company further behind than its press materials suggest.