For most of automotive history, the deal was simple.
You walked into a showroom. You picked a car. You paid for it. You drove it home. And from that day forward, the car you owned was the car you would always own. It might age. It might wear. But it would never fundamentally change. A 2010 Swift bought in Chennai is the same 2010 Swift today — same features, same limitations, same character.
That deal is ending.
For the first time in automotive history, a car's value may increasingly depend on software support as much as mechanical reliability. Not gradually. Not theoretically. It is ending right now, in cars being manufactured today, in software being written in Bengaluru and Shenzhen and Stuttgart that will govern how your next vehicle thinks, behaves, and ages.
The car is no longer a finished product the day it leaves the factory. It is a platform. And most Indian buyers have no idea what that means for them.
From Iron to Silicon
To understand what is changing, you need to understand what a modern car actually is — not mechanically, but architecturally.
A car from 2005 had perhaps 20 to 30 Electronic Control Units — small dedicated computers each responsible for one job. The engine ECU managed fuel injection. The ABS controller managed braking. The airbag module managed deployment. Each unit was isolated, purpose-built, and largely unchangeable after manufacture. To add a feature, you needed new hardware.
A car from 2024 has anywhere from 70 to 150 ECUs. Adding features over the years meant adding more controllers — a reverse camera module here, a tyre pressure monitor there, an ADAS processor somewhere else. The result is a vehicle with a fragmented, deeply complex electronic nervous system where dozens of computers speak dozens of different protocols, and nobody has full visibility into all of it simultaneously.
This architecture has a fundamental problem: it cannot be meaningfully updated after manufacture. It was never designed to be.
Now manufacturers are doing something radical. They are scrapping it entirely.
Why the Architecture Had to Change
Here is what most automotive journalism misses when describing this shift.
A modern car with 100 ECUs resembles a large enterprise application built from dozens of independently managed systems. Every feature requires coordination across multiple controllers, software versions, and communication protocols. Adding navigation updates requires talking to the infotainment ECU. Adding a new ADAS feature requires reprogramming the ADAS processor, the sensor fusion module, and the braking controller — separately, in sequence, with compatibility checks at every step. Complexity grows faster than capability. At some point, the architecture itself becomes the bottleneck.
The shift to centralised compute is not fundamentally about adding features. It is about reducing architectural complexity.
This is the same problem large enterprises solved by moving from siloed legacy systems to centralised platforms. The car industry is a decade behind enterprise software in recognising this — but the logic is identical. When you centralise compute, you decouple software from hardware. Features become deployable. Updates become possible. The vehicle becomes programmable.
That is the shift. Everything else follows from it.
The smartphone industry made this transition between 2005 and 2010. Before the iPhone, a Nokia had dedicated chips for GSM, Bluetooth, and the camera — each separate, each fixed. After the iPhone, a single powerful processor ran everything, and what the phone could do was defined by software, not soldered components. Your car is undergoing the same transition. A decade late, but with the same consequences.
What This Actually Enables
When a car's capabilities are defined by software running on a central computer, the product relationship between manufacturer and buyer changes permanently.
Features after purchase. A software update can add capability to hardware already in your driveway. Tesla has pushed automatic emergency braking improvements and parking assist upgrades to cars already owned. The owner woke up to a vehicle that could do something it could not do the night before.
ADAS that improves. In a distributed architecture, the ADAS processor is a sealed box — it does what it was programmed to do at the factory, forever. In a centralised architecture, ADAS algorithms can be retrained and redeployed. A car bought today with Level 2 ADAS could gain meaningfully improved capabilities next year — not because you bought new sensors, but because the software improved.
Diagnostics that see everything. The vehicle's compute unit has simultaneous visibility across all systems. Battery health, brake pad wear, suspension load history, engine thermal profile — not as isolated readings but as a connected picture. Predictive maintenance becomes a genuine engineering function, not a dealer upsell.
The vehicle as a subscription platform. This is the part Indian automotive media is not covering. When the car is a software platform, the manufacturer retains a commercial relationship with the vehicle — not just at the point of sale, but throughout ownership and across every subsequent owner. BMW tested heated seat subscriptions in some markets. The hardware was already in the car. The warmth was locked behind a monthly fee. The backlash forced a reversal. But the intention, the infrastructure, and the commercial logic all remain intact.
The Manufacturers Shaping This Shift
Hyundai is the most relevant example for Indian buyers. Its Pleos software platform is being deployed across its global lineup — including vehicles sold in India. Pleos is not a feature list. It is an operating architecture built around OTA updates, centralised computing, and AI assistant integration. The next Creta, the next Tucson, the next Ioniq you consider will increasingly be products of this platform. Hyundai is not the global leader in this transition. But it is the manufacturer whose decisions will directly affect the largest number of Indian buyers.
Tesla pioneered the model and remains the benchmark — but also the cautionary tale. Tesla has pushed continuous software improvements to existing vehicles for over a decade. It has also removed features via OTA — including the radar sensor that once powered its automatic emergency braking — leaving owners with hardware sitting unused because a software decision changed the product they thought they had purchased. Both sides of that story matter.
BYD and Xiaomi represent the most aggressive version of this shift. BYD's centralised architecture treats the vehicle as a connected platform from the ground up. Xiaomi entered the automotive market not to make cars but to extend its device ecosystem into the vehicle — the SU7 is explicitly designed to integrate with Xiaomi phones, home devices, and cloud services. The car as a node in a larger software network. That is a fundamentally different product philosophy from anything that existed in automotive before 2020.
A Possible Ownership Story: Pune, 2034
Rajan buys a connected Hyundai Creta in Pune in 2026.
Eight years later, the engine runs perfectly. The suspension is healthy. The body is in good condition. The car has been serviced regularly and has another five years of mechanical life ahead of it.
But Hyundai has ended software support for that platform generation.
The connected services no longer work. Navigation updates have stopped. Some ADAS features are no longer receiving safety improvements. Independent workshops in his area cannot fully diagnose software faults without manufacturer tools that are no longer licensed for that platform.
Nothing is mechanically wrong with the vehicle.
Yet its technology has aged faster than its hardware.
For the first time in automotive history, a car can become software-obsolete before it becomes mechanically obsolete.
What This Means for the Indian Buyer
Resale value will increasingly depend on software support. Today, a five-year-old car's resale value is determined by mechanical condition, kilometres driven, and brand reputation. In a software-defined vehicle, a new variable enters: is the manufacturer still supporting this vehicle's software platform in India? A car with a healthy engine but an abandoned software platform is a harder sell than current resale frameworks account for. This will become visible in the used car market within this decade. Most buyers today compare mileage, safety ratings and service costs. Within a decade, software support may belong on that list.
Independent service becomes harder. A mechanically skilled technician in a Tier 2 city can diagnose and repair most problems on a conventional car with standard tools. A software-defined vehicle with proprietary centralised architecture requires manufacturer-controlled diagnostic software, access credentials, and sometimes remote authorisation for certain repairs. Right to repair — already contested in consumer electronics — will become a live question in Indian automotive ownership sooner than most expect.
Feature subscriptions will reach India. The BMW experiment failed in Germany because consumers pushed back loudly. The same backlash cannot be assumed in every market. The first manufacturer to successfully normalise feature subscriptions in India will quietly establish a precedent that reshapes ownership economics for everyone. It will likely happen through small, seemingly reasonable additions — premium navigation, enhanced ADAS, remote diagnostics — before the model becomes visible for what it is.
The Maruti question. Maruti's dominance was built on mechanical simplicity, widespread service accessibility, and predictable ownership costs — the opposite of what software-defined vehicles introduce. Maruti is aware of this. Its Toyota partnership, Suzuki's global R&D access, and quiet development of connected vehicle capabilities suggest the transition is being planned. But Maruti's pace will be set by its existing customer base, which largely values simplicity over software sophistication. How Maruti navigates this transition is one of the most consequential slow-moving stories in Indian automotive.
Before You Buy, Ask
Every car purchase in 2025 and beyond carries a new set of questions that did not exist five years ago. Before you sign:
- Does this vehicle receive OTA updates — and for how long has the manufacturer committed to supporting this platform?
- What happens to connected features if I keep this car for eight to ten years?
- Can an independent workshop fully diagnose and repair this vehicle, or am I tied to authorised service centres?
- Are any current features on this vehicle already subscription-based, or is the manufacturer planning to introduce subscriptions on this platform?
- If I sell this car in five years, will a buyer inherit full software functionality — or a partially supported platform?
These are not hypothetical concerns. They are the questions that smartphone buyers learned to ask about iOS and Android support timelines. Car buyers will learn to ask them too. The ones who ask them first will make better decisions.
The Finish Line Has Moved
For a century, a car was finished when it left the factory. The engineering was locked in. The features were fixed. Ownership was simple.
That model assumed the car was a product — a discrete object, complete in itself, handed over at the point of sale.
The car is becoming a platform. The wheels still need rubber. The engine still needs oil. The chassis still needs steel. But the layer that increasingly defines what a car does, how it behaves, what it costs to own, and how long it remains useful — that layer is now software.
The day cars stopped being finished products did not make headlines. It happened in software updates pushed at 3am, in centralised compute units quietly replacing a hundred ECUs, in manufacturers designing cars the way phone companies design operating systems.
Your next car is not a machine with software in it.
It is software, with a machine around it.
Understanding that distinction is the difference between buying a car and buying into a platform — with everything that implies about updates, subscriptions, support lifecycles, and who, ultimately, controls what you own.