Who We Insure
Autonomous Vehicle Insurance: When Liability Moves From the Driver to the Software
Autonomous vehicle insurance answers a question the auto market was not built for: who pays when there is no driver to blame. In a conventional crash the at-fault driver's auto liability policy responds. When the driving system is the driver, the same crash becomes a products liability claim against the developer, a professional liability claim over the software and its validation, and often a cyber claim about the remote-operations link, all at once. Test fleets, pilot deployments, and driver-out commercial service each shift that mix.
Why autonomous vehicle companies carry specialized insurance
The exposure is set by the operating design domain and the deployment stage. A company running safety-driver test vehicles on public roads needs commercial auto with high limits and state permits that require them; a company shipping an autonomy kit to a trucking fleet needs products liability sized to the fleet's miles; a robotaxi operator carrying passengers needs all of it plus the liability of a commercial carrier. Underwriters price the stage, the domain, and the safety case rather than the vehicle count alone. This guide covers products liability, commercial auto for test and service fleets, Tech E&O for the autonomy stack, cyber for teleoperation and fleet systems, D&O, and the permit, partner, and underwriting requirements that follow an AV company from closed-course testing to driverless service.
Who this guide is for
Written for founders, heads of safety, general counsel, and finance leads at companies developing or operating automated driving systems. Robotaxi, autonomous trucking, and middle-mile delivery companies at any stage from closed course to driver-out service; Autonomy software and sensor-stack developers that license to vehicle manufacturers or fleets; Sidewalk, yard, campus, and off-road autonomy companies operating outside public roads; Not for conventional fleets adding driver-assistance features — the commercial auto guide covers that program.
The risk profile of an autonomous vehicle company
AV claims are severe, public, and technical. A single crash can produce bodily injury claims, a regulatory investigation, a permit suspension, and a shareholder suit within the same month. Key exposures: Bodily injury and property damage from test and service vehicles, including incidents involving pedestrians, cyclists, and emergency scenes; Products liability for the automated driving system as a product, extending to vehicles operated by partners and customers; Professional liability for the safety case, validation, map data, and remote-assistance decisions that shape how the system behaves; Cyber exposure through teleoperation links, over-the-air updates, fleet management systems, and the sensor and ride data collected; Regulatory and permit actions by state motor vehicle departments and federal safety authorities after incidents or reporting failures; Securities and investor claims when a safety event changes the company's deployment timeline or valuation.
Products Liability for the Automated Driving System for autonomous vehicle companies
When the software drives, crash liability attaches to the system's design and manufacture. Products liability covers bodily injury and property damage caused by the automated driving system wherever it operates, including in partner and customer vehicles, and it is the policy that responds after a driver-out incident. The form must not exclude autonomous operation, software, or vehicles the company does not own, and limits are set with reference to catastrophic single-event severity rather than premium budget. Typically responds to: third-party injury and damage caused by the driving system in any deployment; claims arising from software updates, map errors, and sensor-perception failures; defense of the design and validation decisions behind the system.
Commercial Auto for Test and Service Fleets for autonomous vehicle companies
Owned and operated vehicles need commercial auto liability and physical damage regardless of who or what is driving, and state AV testing and deployment permits set minimum liability limits well above ordinary fleet norms. The auto policy and the products policy must be coordinated so a crash during testing is defended by one of them without a dispute over whether the safety driver or the system was in control.
Technology E&O for autonomous vehicle companies
Companies that license autonomy software, sensors, or simulation and validation tools to manufacturers and fleets face contract claims when the product underperforms, delays a program, or fails a validation milestone. Tech E&O covers those financial-loss claims, which products liability does not, and it is the coverage automotive customers write into licensing and development agreements.
Cyber Liability for autonomous vehicle companies
Teleoperation, over-the-air updates, and fleet management are remote-control surfaces for safety-critical machines, and the fleet collects detailed video, location, and rider data. Cyber covers incident response, business interruption from a fleet-wide grounding, extortion, and privacy liability for recorded data, and it should be checked for bodily injury exclusions that would remove a cyber-caused crash from both policies.
Directors & Officers (D&O) for autonomous vehicle companies
AV companies raise large rounds on deployment timelines that safety events can change overnight. D&O defends directors and officers against investor, securities, and regulatory claims, and it is a condition of most financings and of the independent directors a company adds as it approaches commercial service.
Contract and certificate requirements
Requirements come from state permit regimes first: testing and deployment permits specify minimum liability limits and proof of financial responsibility, and they are enforced by suspension. Vehicle manufacturers, fleet customers, and logistics partners add products liability, auto, Tech E&O, and cyber at stated limits, with additional-insured status and indemnities for incidents involving the system. Cities and airports hosting pilots attach their own insurance exhibits. Development and licensing agreements should allocate liability between the system developer and the vehicle integrator clearly — who is responsible for sensor hardware, for the base vehicle, for maps, for remote assistance — and the insurance program should follow that allocation. A contractual indemnity for crashes caused by the system is only as useful as the products liability limit behind it.
What coverage costs
Pricing for an autonomous vehicle company is driven by deployment stage, operating design domain, miles driven with and without a safety driver, the number of vehicles and their weight class, passenger or cargo service, incident and disengagement history, the safety case and validation program, and the limits permits and partners require. Driver-out passenger service is the most expensive profile; closed-course and licensing-only models sit at the other end. Products liability and auto limits are typically layered — a primary policy plus excess — because a single catastrophic event defines the exposure. Cyber and Tech E&O follow the usual software-company drivers: security controls, update processes, revenue, and contract limits.
What underwriters will ask for
Underwriters for this class want the safety case and the operations data, not only an application form. Have ready: Operating design domain, deployment stage, and the roadmap from safety-driver testing to driver-out service; Fleet schedule by vehicle, weight class, ownership, and jurisdiction, with the permits held; Miles, disengagements, incidents, and collision history, with the reporting the company makes to regulators; Safety case documentation: validation methodology, simulation coverage, remote-assistance procedures, and update governance; Partner and customer agreements with their liability allocations and insurance requirements; Cybersecurity program for teleoperation, over-the-air updates, and fleet data.
Illustrative example: The driverless crash with a cyclist
A robotaxi operating without a safety driver strikes a cyclist who entered the lane from between parked cars. The cyclist is seriously injured. State regulators open an investigation, the company pauses the fleet in that city, and investors ask whether the deployment timeline still holds. Products liability defends the bodily injury claim and funds any settlement, with commercial auto responding where the vehicle is an owned auto and the policies are coordinated. D&O responds to the investor inquiries. The event logs and the safety case are the evidence in every forum at once.
Illustrative example: The autonomy kit that missed the milestone
A trucking fleet licenses an autonomy system under an agreement with validation milestones tied to payments. The developer's system fails a highway-merge validation set twice, delaying the fleet's launch by two quarters. The fleet claims its lost revenue and the cost of extending its driver contracts. Tech E&O responds to the fleet's financial-loss claim for the alleged failure to perform under the development agreement; products liability does not, because no one was injured. The agreement's limitation of liability and the milestone definitions decide the exposure.
What does autonomous vehicle insurance cost?
Pricing depends on deployment stage, operating design domain, miles with and without a safety driver, vehicle count and weight class, passenger or cargo service, incident history, the safety case, and the limits permits and partners require. As of 2026, programs are built in layers around products liability and commercial auto, with Tech E&O, cyber, and D&O alongside, and there is no standard figure.
Does commercial auto insurance cover a vehicle with no driver?
Commercial auto covers the owned vehicle's liability and physical damage, but a driverless crash is also a products claim against the system. Both policies should be in place and coordinated, with neither excluding autonomous operation, so the crash is defended without a dispute over which policy applies.
What limits do state AV permits require?
Minimums vary by state and by permit type, and they are generally far above ordinary commercial fleet norms, so expect layered primary and excess liability from the first public-road test. The permit application typically requires proof of insurance or a surety bond or self-insurance certificate at the stated amount.
Does a company that only licenses autonomy software need products liability?
Yes. The software controls a vehicle, and injured third parties will name its developer regardless of who owns the truck. Products liability covers bodily injury and property damage from the system; Tech E&O covers the customer's financial losses when the product fails to perform.
Does cyber insurance cover a crash caused by a hacked vehicle?
Often not, because most cyber forms exclude bodily injury and property damage, and most products forms do not exclude cyber causes. Confirm that the products policy has no cyber exclusion and that the cyber policy's bodily injury exclusion does not reach the response and recovery costs, so a cyber-caused crash is covered somewhere.
Caveats and common gaps
Autonomous-operation, software, and non-owned-vehicle exclusions appear in auto and products forms and must be removed for this class. Cyber bodily-injury exclusions and products-policy cyber exclusions can leave a gap in the middle. Permit minimums, partner contracts, and catastrophic severity set the limits, not the premium budget.
Related guides
Robotics and automation companies — the broader industry page for autonomous systems · Insurance for Logistics Tech Companies — freight platforms and the fleets that deploy autonomy · Commercial auto insurance — the fleet program AV programs are built on · Insurance for Defense Tech Startups — autonomy for government and test-range customers · Insurance for Fleet Management Software Companies · Product liability and completed operations coverage · Tech E&O insurance · Insurance for Drone & UAV Companies — aviation liability for uncrewed aircraft · Insurance for Micromobility Companies · Insurance for Semiconductor & Chip Startups — the accelerator chips inside the stack
Frequently asked questions
What does autonomous vehicle insurance cost?
Pricing depends on deployment stage, operating design domain, miles with and without a safety driver, vehicle count and weight class, passenger or cargo service, incident history, the safety case, and the limits permits and partners require. As of 2026, programs are built in layers around products liability and commercial auto, with Tech E&O, cyber, and D&O alongside, and there is no standard figure.
Does commercial auto insurance cover a vehicle with no driver?
Commercial auto covers the owned vehicle's liability and physical damage, but a driverless crash is also a products claim against the system. Both policies should be in place and coordinated, with neither excluding autonomous operation, so the crash is defended without a dispute over which policy applies.
What limits do state AV permits require?
Minimums vary by state and by permit type, and they are generally far above ordinary commercial fleet norms, so expect layered primary and excess liability from the first public-road test. The permit application typically requires proof of insurance or a surety bond or self-insurance certificate at the stated amount.
Does a company that only licenses autonomy software need products liability?
Yes. The software controls a vehicle, and injured third parties will name its developer regardless of who owns the truck. Products liability covers bodily injury and property damage from the system; Tech E&O covers the customer's financial losses when the product fails to perform.
Does cyber insurance cover a crash caused by a hacked vehicle?
Often not, because most cyber forms exclude bodily injury and property damage, and most products forms do not exclude cyber causes. Confirm that the products policy has no cyber exclusion and that the cyber policy's bodily injury exclusion does not reach the response and recovery costs, so a cyber-caused crash is covered somewhere.
This material is general educational information, not legal, tax, or insurance advice. Coverage availability, policy terms, and regulatory requirements vary by state, carrier, and applicant.