Self-Driving Vehicles

Buying advice

Describe your routes in ODD terms

Comparing operating domains is easier when every maker uses the same vocabulary. ISO 34503:2023 sets out a hierarchical taxonomy for specifying the operational design domain of Level 3 and Level 4 systems, written for developers as well as insurers and regulators. Describe your own routes in those terms first: road types, junction layouts, speed limits, weather, lighting and seasonal events such as roadworks or snow. Then ask each maker to mark where its domain matches yours and where it falls short. The gaps show where a safety driver, remote assistance or a change of route will still be needed, and they give you a fair basis for comparing quotes.

Ask for the safety case and crash record

A credible supplier should be able to show you its safety argument, not only its mileage. UL 4600 provides a framework for building evidence-based safety cases, and UL Standards & Engagement reports that Gatik uses it as the foundation of its own. Ask each maker how its case deals with a mud-covered camera, weather the system cannot drive in, and a pedestrian stepping out unexpectedly. In the US, NHTSA's Standing General Order requires manufacturers and operators to report crashes involving automated driving systems, so ask for the reports filed for the system you are considering and what changed afterwards.

Check status and exit terms before signing

On the October 2026 review, the Tesla Cybercab was the lowest-priced listing here at about $30,000, while the Cruise Origin topped the page at about $50,000, and another five were quote-only. Plans in this field can change, so read the commercial terms as closely as the specification. Ask who owns the driving data your vehicles collect, how software updates are validated before they reach your fleet, and who carries liability while the system is driving. Agree what happens to your vehicles, maps and support if the maker withdraws the product or leaves your service area.

What to look for

• Level of autonomy, and whether a safety driver or remote operator is needed
• Operating domain: the roads, speeds and weather the system is designed for
• Whether you are buying a vehicle, a driving system or a commercial programme

Common questions

Can I buy a self-driving vehicle outright?

Some listings are vehicles; others represent a driving system or a programme offered to operators. Read each listing and request a quote to confirm exactly what is supplied.

What is an operational design domain?

It is the set of conditions a self-driving system is designed to handle, such as road types, speeds, weather and time of day. Ask about it for every system you shortlist.

Sources and further reading

• ISO 34503:2023 Road vehicles: test scenarios for automated driving systems, specification for operational design domain — International Organization for Standardization (ISO).
  A shared taxonomy for describing where and when an automated driving system is designed to operate.
• NHTSA Releases Initial Data on Safety Performance of Advanced Vehicle Technologies — National Highway Traffic Safety Administration (NHTSA).
  Explains the Standing General Order that requires crash reports for vehicles with automated driving systems.
• The Safety Questions All Autonomous Truck Companies Need to Answer Before Deployment — UL Standards & Engagement.
  Questions autonomous truck developers should answer on sensors, weather and pedestrians, framed by UL 4600.