Europe builds EV powertrains but who writes the code that drives them?
In 2026, Chinese brands are gaining ground in Europe, and European carmakers are turning to Chinese partners for technology in what has been called a “reverse joint venture”. Volkswagen and Audi, for example, have both signed software deals with Chinese firms in the last few years.
While electronic architecture can be bought and partners can speed up development, there is one element that should stay in European hands: the software that decides how the car drives, and the ability to prove that it behaves correctly.
To see why, imagine an electric car approaching a downhill bend on a winter morning. Its cold battery can absorb little recovered energy, so when the driver brakes, the software must blend regenerative and friction braking without the deceleration shifting mid-corner. Acceleration poses the same problem in reverse, as battery protection, traction control, and thermal limits each cap the torque the driver requests, and the software has to turn those competing limits into one smooth, predictable response.
When this software works, the driver never notices it. When it doesn’t, the car feels unpredictable at exactly the moment it matters most. This is the part of the car Europe can least afford to outsource.
Whose architecture will Volkswagen use?
Volkswagen shows how quickly this shift is happening. Its China Electronic Architecture (CEA), developed with Xpeng, entered production in early 2026. According to Volkswagen, it went from concept to production in 18 months and uses about 30% fewer control units than its predecessor.
In late October 2026, Manager Magazin and Reuters reported that Volkswagen brand chief Thomas Schäfer was preparing a proposal to bring the CEA to Europe, where it would underpin around three-quarters of next-generation Volkswagen, Škoda, and Cupra models. This would bring reported savings of €4–5 billion. The proposal still needs group approval, but if it goes ahead, it would sideline Volkswagen’s software joint venture with Rivian, backed by up to $5.8 billion, for those brands.
Yet whichever platform wins, adopting it does not hand over ownership of every motor-control algorithm or battery calibration. Fewer control units mean fewer boxes, not less need to prove that the whole system behaves correctly.
Can testing keep pace?
Meanwhile, Renault is demonstrating how fast a European program can run. The Twingo E-Tech, the first car from its Leap 100 program, was developed in under two years, against an industry norm of two to five years. Ampere led development from France, drawing on Chinese suppliers and engineers through Renault’s Shanghai center, while production takes place in Slovenia. In its Q3 2026 results, Renault reported Twingo sales of nearly 26k units since launch. The company now aims to bring the same pace to the rest of its range, potentially halving time to market. But at that speed, there is no room for a long tail of calibration fixes, so testing has to move earlier.
This is where simulation comes in. According to Renault, the Renault Operational Advanced Driving Simulator (ROADS) can test “nearly every aspect of how a vehicle operates,” reducing the need for physical prototypes. Its supplier, AVSimulation, says Twingo engineers used the simulator to assess vehicle dynamics and emergency braking.
Why does BMW code in-house?
BMW, by contrast, treats driving dynamics as too central to outsource. In the Neue Klasse iX3, its in-house Heart of Joy computer runs Dynamic Performance Control software, which coordinates the powertrain, brakes, recuperation, and parts of the steering as a single system. Based on its own prototype testing, BMW says the iX3 can stop without using its friction brakes in 98% of cases. That matters on a winter bend like the one above. When a cold battery limits recuperation, the software must blend in friction braking without the driver noticing. Because BMW owns that code, it can tune the transition itself and update it over-the-air (OTA) without waiting for a supplier.
Who carries the liability?
Owning the code also matters because, legally, the automaker answers for it. In Europe, UNECE Regulations 155 and 156, which cover cybersecurity and software updates, have been mandatory for all new vehicles since July 2024. Under EU type approval, the carmaker is accountable for all vehicle software, including supplier and open-source code, and R155 requires it to manage cyber risks across that supply chain. ISO 26262 safety cases are also expected to cover partner code. Under R156, every OTA update must be assessed for its impact on safety and type approval before release. In practice, even a change to recuperation means regression testing across battery temperatures and states of charge, both in simulation and on hardware-in-the-loop rigs.
Where the code comes from is a separate question. No EU law bans Chinese software; however, the December 2025 automotive package and a forthcoming Industrial Accelerator Act point to “made in Europe” conditions on public support. France has proposed that vehicles should reach a threshold of 75% EU added value, including critical electronics, to qualify.
What should Europe own?
Taken together, these cases point to a balance, where Europe should share the architecture but own how the car behaves. Trying to own everything has proved expensive. For example, Volkswagen’s software unit, CARIAD, lost €2.4 billion in 2024 alone. Sharing is already gaining ground, with BMW, Mercedes-Benz, Volkswagen, and Stellantis among 32 companies building S-CORE, an open-source software core that German industry association VDA (Verband der Automobilindustrie) says could cut effort on non-differentiating software by up to 40%. That frees in-house teams to focus on what shapes how the car drives.
Source: GlobalData
Analysis
Not every carmaker needs to write all of that software itself, though. Since 2023, Lotus has licensed ZF’s cubiX software for the Eletre’s brakes, steering and drive, tuned to Lotus’s own specification. ZF still offers cubiX to automakers that want its expertise without its hardware, and for a low-volume brand, licensing is cheaper, although rivals can buy the same base software.
However, partnerships are spreading fastest in driver assistance, with Volkswagen working with Horizon Robotics, and Audi with Huawei. BMW’s driver-assistance stack, developed jointly with Qualcomm, shows co-development can work, provided the carmaker owns the safety case.
Back on the downhill bend, the driver will never know whose architecture sits under the floor. But they will notice whether the car slows exactly as their foot asks. Manufacturers that can specify, verify, and refine that response can take on partners without handing over the driving experience.
Sarath Nair, Analyst, Powertrain, GlobalData