Software-defined vehicle (SDV)
Also known as: SDV, software defined vehicle, software-defined car
A software-defined vehicle (SDV) is a car whose features, from driver assistance to battery management and infotainment, are controlled mainly by software running on a few powerful central computers rather than dozens of separate fixed-function modules.
That lets automakers fix problems and add features through over-the-air updates. While SDVs promise cars that improve over time, they also bring subscription features, cybersecurity risks, and a software skills gap that many traditional automakers have struggled to close.
Software-defined vehicle (SDV), explained at three levels
At home
Think of the difference between an old flip phone and a smartphone. The flip phone did what it did on day one, while the smartphone keeps changing with updates. A software-defined vehicle is built like the smartphone: a few powerful computers run most features in software, so the automaker can send updates over the internet that fix bugs or add new abilities.
At work
A software-defined vehicle is a car designed so its features run mainly as software on central computers, not in fixed electronics. Automakers can then update, fix, and add features over the air throughout the car's life. For businesses, that means fewer dealer visits for recalls, features that improve after purchase, and new costs such as subscriptions and data agreements.
At home
A traditional car has dozens of small computers called electronic control units, each running one job, like the windows or the engine. A software-defined vehicle consolidates those jobs onto a few central computers, with smaller zone controllers wiring up nearby sensors and motors. Because the software lives in one place, an over-the-air update can change many features at once, such as how the brakes feel or how the battery warms up in winter.
At work
SDV architectures have three layers. Zonal controllers sit in each area of the car and connect local sensors and actuators, cutting wiring. High-speed automotive Ethernet links them to one or more central computers. On those computers, a hypervisor separates safety-critical software, such as braking on a real-time operating system, from infotainment running Android Automotive or Linux. Middleware such as AUTOSAR Adaptive lets features update independently, enabling app-like releases.
At home
Once features live in software, the automaker decides which ones you can use. Hardware like heated seats or extra range can ship in every car and be unlocked by subscription, as BMW tried with heated seats before backing down. While that can lower purchase prices and allow useful upgrades, in my opinion it can also feel like renting parts of a car you already paid for.
At work
SDV programs must meet ISO 26262 for functional safety, UN Regulation 155 for cybersecurity management, and UN Regulation 156 for software updates, along with ISO/SAE 21434. Failure modes include bad updates that disable features and the burden of long-term support, since software must be patched for 15 years or more. Volkswagen's Cariad delays showed how hard the organizational shift is. For fleets, I'd review update policies, data access, and subscription terms before buying.
Real-world examples
At home
Lena's electric car received an over-the-air update that improved its winter range estimate and added a new camera view for parking. She didn't need to visit the dealer.
At work
Jerome manages a utility's vehicle fleet in Alberta. Because his trucks are software-defined, a recall for a braking software issue was fixed overnight through remote updates instead of taking each truck out of service.
How it compares
| feature | Software-defined vehicle (SDV) | Traditional vehicle |
|---|---|---|
| Computers | A few central computers | Many separate ECUs |
| Updates | Over the air, frequent | Dealer visit, rare |
| New features after sale | Possible | Rarely |
| Cyber risk | Higher, more connected | Lower |
SDVs can keep improving, but they're also more connected and harder to secure.
For analysts
For fleets, SDVs can cut downtime from recalls and add useful features over time. I'd review update policies, data access terms, and subscription costs before committing.
History & origin
For decades, cars added one electronic control unit (ECU) per feature, and luxury models ended up with more than 100 ECUs from different suppliers. Tesla broke from that model with the Model S in 2012, pushing over-the-air updates that changed how the car drove. Traditional automakers scrambled to follow. Volkswagen created its software unit, Cariad, in 2020, but delays hurt launches, and in 2024 VW announced a joint venture with Rivian worth up to US$5.8 billion to share Rivian's software and electrical architecture. Chinese automakers such as BYD, NIO, and Xiaomi moved quickly with software-heavy cars. In my view, the SDV shift is less about technology than about whether century-old car companies can learn to behave like software companies.