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 your car like a smartphone on wheels. Instead of features being fixed forever, the car can download updates that fix bugs or add new abilities while it sits in your driveway.
At work
SDVs let automakers improve vehicles after sale, fix recalls remotely, and sell optional features, changing how they earn money over a car's life.
At home
Older cars had many small computers, each running one job. SDVs combine those jobs onto a few bigger computers, which makes it easier to update everything at once.
At work
SDV architectures use zonal controllers that connect sensors and actuators by location, linked to central compute over high-speed Ethernet. Software is separated from hardware through middleware and hypervisors, allowing independent updates and app-like feature releases.
At home
Some automakers charge monthly fees to unlock features already built into the car, like heated seats. In my opinion, that's where SDVs can feel less like progress and more like renting what you thought you bought.
At work
Challenges include functional safety (ISO 26262), cybersecurity compliance (UN Regulation No. 155) and software update management (UN R156), long support lifecycles, supplier contracts, and data governance. Organizational change, such as hiring and retaining software talent, is often the hardest part.
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.