Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Open source gives automakers and suppliers a way to build and improve shared software foundations for software-defined vehicles (SDVs)—vehicles whose features, functions, and operations increasingly depend on software. Projects such as Eclipse S-CORE, Eclipse OpenSOVD, and Automotive Grade Linux’s SoDeV address different layers of that work. They show active collaboration and technical development, not proof that open-source software is already deployed across the industry or that any project is certified for safety-critical use.

What role does open source play in software-defined vehicles?

An SDV relies on software to shape more than its infotainment system: software increasingly controls vehicle features, coordinates electronic systems, supports diagnostics, and enables updates and fleet management. Building every underlying component independently can duplicate effort across manufacturers and suppliers.

Open-source projects offer a shared development model for some of those foundations. Companies and individual contributors can work on common code, interfaces, and processes, then adapt and validate them for particular vehicles and products. The Eclipse SDV Working Group describes its goal as a collaborative forum for software, specifications, and working models for a scalable, modular vehicle-software platform. Its charter groups activity into developer tools and workflows (SDV.Dev), fleet software management (SDV.Ops), and cloud-native in-vehicle technologies (SDV.Edge), alongside quality, safety, security, compatibility, and interoperability work (Eclipse SDV Working Group Charter).

The phrase “higher-level SDVs” is not a formal technical category in the sources discussed here. It is best understood as an editorial description of vehicles whose features and operations depend increasingly on software.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

What are the main projects building?

These initiatives are not interchangeable. One focuses on shared in-vehicle middleware, another on diagnostics, and a third was announced as an integrated development reference platform.

Project Focus and intended role Status and evidence
Eclipse S-CORE Middleware for embedded high-performance electronic control units (ECUs), between the operating system and application layer. Shared services include application orchestration, inter-process communication, logging, and data persistence. The Eclipse Foundation announced the project on 12 June 2025. Its development process was then under audit to define a methodology for software intended to support safety-critical automotive standards such as ISO 26262; that announcement does not establish completed certification. Eclipse Foundation announcement.
Eclipse OpenSOVD An open-source implementation of Service-Oriented Vehicle Diagnostics (SOVD), as defined in ISO 17978. The project describes a diagnostics gateway, adapters linking newer high-performance computers with legacy ECUs, and a diagnostic manager. It is intended to complement and integrate with S-CORE. The Eclipse project page identifies OpenSOVD as incubating. Incubating status should not be read as proof of broad deployment or production maturity. Eclipse OpenSOVD project page.
AGL SoDeV A reference platform intended to support software-first SDV development decoupled from hardware constraints. The announced components include Automotive Grade Linux’s Unified Code Base, Linux containers, VirtIO, Xen, Yocto Project, Zephyr, and ELISA. Automotive Grade Linux announced SoDeV on 5 December 2025 and said availability was planned for early 2026. That was a schedule in the announcement, not confirmation that the release occurred. Linux Foundation / Automotive Grade Linux announcement.

S-CORE: shared services, not a complete vehicle stack

S-CORE targets embedded high-performance ECUs and supplies common middleware functions that applications can use. Its intended position between the operating system and applications makes it a potential shared foundation, not a finished vehicle architecture. The 12 June 2025 announcement described an audit of the development process; it did not report that the project had achieved ISO 26262 certification.

“Open collaboration is key to managing complexity in modern vehicle software architectures,” said Eclipse Foundation executive director Mike Milinkovich in that announcement. The quotation represents the view of the foundation hosting the project, rather than an independent assessment.

OpenSOVD: a diagnostic layer

OpenSOVD addresses access to vehicle diagnostics across different computing generations. Its described adapters are intended to connect newer high-performance computers with legacy ECUs, while the gateway and diagnostic manager provide the surrounding diagnostic functions. Its connection to S-CORE is complementary: diagnostics and core middleware are distinct parts of a larger software environment.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Rank #3
MPC 1932 Ford Switchers Roadster/Coupe 1:25 Scale Model Kit
  • 1:25 scale, skill level 2, paint & glue required
  • 120 parts
  • Molded in white, clear, and some chrome-plated parts
  • Black vinyl tires
  • Metal axel

SoDeV: an announced reference platform

SoDeV was presented as a way to develop and integrate SDV components without tying early software work to a particular hardware configuration. The named components span Linux-based development, virtualization, embedded operating systems, and safety-related work. Because the announcement only gave an early-2026 target, readers should check the project’s current release information before treating SoDeV as available.

What benefits and challenges does open-source automotive software bring?

The Eclipse Foundation’s 27 March 2025 announcement summarized a survey of 300 automotive developers and business leaders. Respondents identified performance, security, and customisability as perceived benefits of open-source adoption. These are reported perceptions, not guarantees that every open-source project delivers those outcomes.

The same summary identified integration complexity, ongoing real-time performance improvements, and scalability as technical blockers requiring continued investment. Shared code can reduce duplicated work, but it does not remove the effort needed to adapt components, integrate them with existing systems, validate behavior, and maintain them over time. The survey announcement did not provide percentage breakdowns, so the findings should not be treated as quantified rankings or as a measure of adoption across the whole automotive market.

The Eclipse Foundation’s 2025 Annual Community Report counted 63 Eclipse SDV Working Group members as of 31 March 2025. That figure describes membership in the working group at that date; it is not a count of automakers deploying SDV software in production (Eclipse Foundation 2025 Annual Community Report).

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Best Value
Inno Models (A90) WBK DarwinPro Air Force Matt Gray with Carbon Accents 1/64 Diecast Model Car IN64-A90DP-MGRAY
  • Brand new box. Detailed exterior. Real rubber tires. True-to-scale detail. Officially licensed product. Does not have any openings. Comes in a plastic display showcase. Manufacturer's original unopened packaging. Made of diecast metal with some plastic parts. Dimensions approximately L-2.75 inches long.

Sources: Eclipse Foundation automotive open-source research announcement; Eclipse Foundation 2025 Annual Community Report.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Can open-source automotive software meet safety requirements?

Open-source licensing and collaboration do not, by themselves, establish that software is safe for use in a vehicle. Safety-critical use depends on engineering and quality processes, evidence, and validation appropriate to the intended application. The Eclipse SDV charter explicitly includes quality management, functional safety, supply-chain security, compatibility, and interoperability as areas of work (Eclipse SDV Working Group Charter).

For S-CORE, the June 2025 announcement said its process was under audit to define a methodology intended to support standards such as ISO 26262. That is a dated statement about process development, not a certification result. The available project descriptions likewise do not establish that OpenSOVD or SoDeV is certified for a particular safety use. A vehicle program must assess the specific software version, its intended function, the evidence available, and how it is integrated and validated.

How should teams assess SDV open-source projects?

Before choosing a project for a vehicle program, compare it with the intended application rather than relying on the general label “open source.” Useful checks include:

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
  • Layer and function: Is the project for core runtime services, diagnostics, developer workflows, fleet operations, or an integrated reference platform?
  • Deployment target: Does it address embedded high-performance ECUs, mixed vehicle compute, legacy ECU integration, or cloud-connected fleet systems?
  • Maturity evidence: Is it incubating, announced, released as a reference implementation, or supported by documented production deployments? These stages are not equivalent.
  • Safety and quality process: What process is documented, what has been audited, and is there verified certification evidence for the intended use?
  • Interoperability and governance: Are interfaces and standards compatibility clear? How are contributions, releases, and compatibility managed?
  • Integration and maintenance effort: What adaptation, validation, security review, and long-term maintenance will the vehicle program still need to fund?

This distinction matters because the project sources establish goals, architectures, and announcements, but do not establish general production deployment across automakers. Current release and audit details can also change; consult each project’s own page or announcement when making a deployment decision.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.