German Carmakers Back a Shared Open-Source Base for Safety-Oriented Vehicle Software
A June 2025 VDA-backed memorandum puts eleven automotive companies behind pre-competitive open-source development for non-differentiating vehicle software. The announcement is notable because it couples a code-first model with an explicit certification-preparation story instead of treating open source and safety as separate tracks.
What the memorandum actually says
Under a VDA-backed memorandum announced in June 2025, eleven automotive companies agreed to collaborate on pre-competitive open-source software development. The stated target is the large share of vehicle software that is important for platform capability but not directly differentiating to end users. The project sits inside the Eclipse Foundation's S-CORE environment and explicitly aims for a transparent, vendor-independent development model.
The more important claim is about process. The release says the participants developed a process intended to prepare open-source software for certification against the relevant automotive standards. It also emphasizes a code-first approach, arguing that executable modules can drive standardization and development speed more effectively than detailed paper specifications alone.
Why this matters
For systems engineers, this is less a story about "open source cars" than a story about where common infrastructure ends and product differentiation begins. The automotive software stack is now complicated enough that manufacturers and suppliers have a real incentive to share some of the foundation while competing higher up the stack.
That is especially interesting in a safety context. Shared code is not new. Shared code accompanied by an explicit certification-preparation process is more consequential, because it speaks to how reusable safety-relevant software might be industrialized rather than negotiated program by program.
What Hacker News focused on
The HN discussion quickly split between optimism and architecture skepticism. Some commenters pointed out that Linux, Wayland, and open-source UI stacks are already common in vehicle infotainment environments. Others questioned whether desktop-adjacent software components belong anywhere near high-reliability automotive systems.
That distinction is actually useful. The discussion repeatedly separated the "must work" control surfaces from the convenience and infotainment layers around them. That is exactly the systems boundary question this announcement will live or die on.
Read the original article at vda.de.