Volkswagen and Bosch end driving alliance

Volkswagen and Bosch end driving alliance

Volkswagen and Bosch have ended their automated driving partnership today. The split exposes the difficulty of scaling software-defined vehicle systems.


Volkswagen and Bosch have ended their automated driving partnership, bringing a major German software and driver assistance collaboration to a close after four years.

The project was launched in 2022 through Volkswagen’s software unit Cariad and Bosch, with the aim of developing advanced driver assistance and automated driving systems for Volkswagen Group brands. The work focused on Level 2 driver assistance, where the driver remains responsible for monitoring the road, rather than Level 3 systems that can take over environmental monitoring under defined conditions.

Both companies will retain access to the intellectual property and data developed during the partnership and may continue work independently. Volkswagen has said the technological foundation created through the alliance will remain valuable, while the group is expected to define its next steps separately.

The end of the alliance follows continuing pressure on Volkswagen’s software strategy. Cariad has faced repeated delays and financial strain since its creation in 2020, while European manufacturers more broadly are trying to close the software gap with Tesla, Chinese EV makers, and technology-focused suppliers.

Automated driving is no longer limited by one sensor, processor, or algorithm. It depends on a complete system combining software architecture, perception, maps, compute, validation, safety assurance, cybersecurity, vehicle integration, regulatory compliance, and customer acceptance. Development becomes expensive and slow when systems have to be deployed across multiple brands, vehicle classes, and regional markets.

Bosch remains one of the world’s largest automotive suppliers, with deep capability in sensors, control systems, software, braking, steering, and vehicle electronics. Volkswagen’s decision does not remove the need for those technologies; it changes how the carmaker wants to source, integrate, and scale them.

Vehicle electronics are moving toward zonal architectures, central compute platforms, and high-speed in-vehicle networks. Hardware development is following that path, with 25Gbps automotive Ethernet connector systems being introduced to support ADAS, LiDAR, central compute, and software-defined vehicle functions. The software partnership split is part of the same transition reshaping the vehicle architecture.

Automated driving economics are also being reassessed across the sector. Several manufacturers have narrowed autonomy ambitions as the cost of development, validation, and legal responsibility becomes clearer. Level 2 systems are widely deployed, but moving further toward higher automation requires a far larger evidence base, especially in mixed traffic, poor weather, roadworks, and unusual edge cases.

Platform strategy adds another complication. Carmakers want software systems that can be reused across brands and models, but vehicle diversity makes that difficult. A compact EV, premium saloon, commercial van, and performance model may share parts of a software stack, yet differ in sensors, packaging, compute, electrical architecture, braking systems, steering response, and customer expectations. Reuse is attractive, but validation cannot be assumed across different vehicle contexts.

The industrial effect reaches beyond software teams. Automated driving programmes influence electronics manufacturing, sensor suppliers, test equipment, simulation providers, data centres, wiring harnesses, thermal management, and quality assurance. A change in partnership strategy can ripple through supplier roadmaps because components and architectures are often designed around expected platform volumes.

Volkswagen’s next sourcing decisions will be watched closely. The group may look to external hardware and software partners, continue parts of the work internally, or adopt a more modular approach that reduces dependence on a single alliance. Each route carries a trade-off. Buying more technology externally can speed deployment, while building internally can preserve control but demand heavy investment.

Software-defined vehicles remain manufacturing products. The code has to work with real sensors, real wiring, real compute hardware, real thermal limits, and real production tolerances. Partnerships can create capability, but they must also deliver at vehicle programme speed. Volkswagen and Bosch have created a technical base; the commercial test now is how each side converts that work into systems that reach production vehicles.


Stories for you