Accelerating the Path to Software-Defined Vehicles with Open Source

SOAFEE, Eclipse, COVESA – these names and acronyms represent a new era in automotive development. They are organizations and alliances united by a common goal: to standardize open-source software for automotive applications. This approach enables faster and more cost-effective development in the age of software-defined vehicles. Since open source makes source code publicly accessible, it inherently offers efficiency advantages.

In June 2025, major players in the German automotive industry, including ZF, signed a declaration to intensify cooperation on open-source software. The focus is on so-called “non-differentiating” software. “A significant portion of a vehicle’s software is not directly visible to drivers and doesn’t offer manufacturers a competitive edge,” explained Gunther Bauer, Senior Manager Delivery Lead Software Innovation.

Such software modules, for example, for vehicle diagnostics, can be developed collaboratively by multiple manufacturers and suppliers within an open ecosystem. “We highly value this kind of open development, especially with other suppliers and OEMs,” said Bauer.

This kind of ecosystem, where competing companies collaborate, is already well established in the tech industry – in computers, smart devices, and apps. Hardware specialists work hand in hand with developers of foundational software, such as operating systems with standardized interfaces. Applications build on this technical foundation to deliver high-value functions to end users. Competition only begins at the final stage. Cross-company collaboration in earlier stages works well in tech – and open source plays a vital role, as seen with Android. With over 100 billion downloads, Android is the most widely used mobile operating system.

“To collaborate effectively in the automotive space, we need to make the open-source model suitable for automotive use,” Bauer explained. While the industry has used open-source software for years, it has mostly been limited to in-car entertainment. Applying the concept to driving functions introduces new safety and quality requirements that are not yet standardized, but urgently needed. “If a navigation screen briefly goes black and restarts, that’s acceptable. But with brakes or steering, that must never happen,” Bauer emphasized.

The core idea: instead of each company developing its own proprietary solutions, industry players collaborate via open source. The resulting modules, called “stacks”, can be used, adapted, extended, and customized by all participants, provided they contribute their own insights and improvements. This community-driven approach often results in foundational software that is more powerful and reliable than isolated proprietary code. “Active participation is key,” said Bauer. “Open source is not a grab-and-go store. It thrives on long-term commitment. And those who join early can help shape the standards,” he added, explaining ZF’s motivation.

This brings us back to SOAFEE, Eclipse Foundation, and COVESA – three organizations advocating closer collaboration between automakers and tech providers, long before the June 2025 memorandum. These consortia promote open-source software collaboration, define roadmaps, and initiate pilot projects. ZF has been involved in this foundational work for years and is a founding member of the Eclipse SDV Working Group, established in 2022.

One current project within the Eclipse SDV Working Group aims to develop an operating system for central vehicle computers capable of integrating ECU software. In the S-CORE project, ZF is responsible for standardizing the interface between foundational software and applications through the “Automotive API Framework.” As a function developer, ZF has a strong interest in a standard that meets automotive industry requirements. Currently, integrating ZF functions into proprietary software from different manufacturers requires significant customization.

Another project, “Open SOVD,” focuses on “Service Oriented Vehicle Diagnostics.” Here, ZF is adapting open-source software to meet automotive-specific needs. The goal is to transfer cross-manufacturer diagnostic software standards to high-performance computers – the hardware that will power the new E/E architectures of modern vehicles.

“ZF is not only active in application and function software,” Bauer added. “Through our joint venture partner Qorix, we’re also involved in developing foundational software and middleware.” Qorix also supports safety certifications and general process documentation. It could even act as a distributor – licensing and selling automotive-grade open-source software. Similar to Linux distributors in the computer world, buyers would benefit from not having to manage safety qualifications or long-term maintenance themselves.

All of this is part of the ecosystem the industry is striving to build. And the fact that this ecosystem is steadily taking shape shows how close the software-defined vehicle is to becoming reality – with ZF software deeply embedded in its code.