At the start of January 2026, around the timing of CES, Germany’s automotive industry association (VDA) and the Eclipse Foundation confirmed that their Automotive-Grade Open Source Software Ecosystem has expanded significantly. The collaboration, launched in mid-2025 with a smaller group of participants, now counts over 30 companies across the global automotive supply chain.
The initiative is positioned as a pre-competitive effort focused on so-called non-differentiating software—the foundational layers needed for modern, software-defined vehicles but not seen as sources of brand or feature advantage. Organizers and participants argue that sharing this software can meaningfully cut development costs and shorten vehicle development cycles.
What changed in the last 14 days
Expansion of membership
- The consortium grew from 11 original signatories to 31–32 participating companies, depending on how signatories are counted in public statements.
- Newly referenced participants include additional global OEMs, Tier-1 suppliers, semiconductor companies, and enterprise software and consulting firms.
- The announcement was coordinated around CES, signaling a desire to frame the expansion as part of the industry’s broader shift toward software-defined vehicles.
Recent disclosures emphasized quantified targets:
- Up to 40% reduction in development, integration, and maintenance effort for shared software components.
- Up to 30% faster time-to-market for vehicle software platforms built on the shared stack.
While these figures are aspirational, their prominence signals how central cost and speed pressures have become in automotive software strategy.
Structure and technical focus
Governance model
- The initiative is supported by the VDA but hosted within the Eclipse Foundation’s open-source governance framework.
- This structure is intended to ensure vendor neutrality, transparent contribution rules, and broad industry participation.
Technical scope
- The collaboration centers on an automotive-grade reference stack designed to be:
- production-ready,
- suitable for safety-critical environments,
- and adaptable across different vehicle programs and suppliers.
- The Eclipse S-CORE project is positioned as the technical backbone, with early versions already released and fuller releases planned during 2026.
The emphasis is not on end-user features, but on middleware, tooling, and foundational infrastructure that nearly every modern vehicle program now requires.
Why this matters for the automotive sector
Software costs have become structurally unsustainable
As vehicles evolve into software-defined platforms, OEMs and suppliers are spending heavily on:
- operating systems and middleware,
- integration across dozens of electronic control units,
- long-term maintenance and updates.
Much of this work is duplicated across companies. The expanded pact is a direct response to the realization that software economics are becoming a bottleneck for both incumbents and suppliers.
Speed is now a competitive constraint
Traditional automotive development cycles struggle to keep pace with:
- frequent software updates,
- rapid advances in compute hardware,
- expectations set by consumer electronics and tech companies.
Shared foundations are meant to reduce integration friction and allow companies to focus resources on higher-level functionality rather than rebuilding the same base layers.
Platformization in a legacy industry
This development reflects a broader pattern: legacy industrial sectors adopting platform and consortium models long used in enterprise software and cloud infrastructure. Rather than vertical, fully proprietary stacks, the industry is experimenting with shared cores plus differentiated layers above them.
Points of uncertainty and tension
Defining “non-differentiating” software
While participants broadly agree on the principle, the boundary is inherently subjective. Middleware, tooling, or even certain system services may be viewed as strategic by some players and commoditized by others. Managing this tension will be an ongoing challenge.
Safety, liability, and certification
Open-source software in safety-critical systems raises questions about:
- responsibility for certification artifacts,
- accountability in the event of defects,
- and how updates are validated across multi-supplier stacks.
Although the initiative stresses “automotive-grade” quality, these issues are complex and unresolved at scale.
Governance and influence
With more than 30 companies involved, decision-making can become slow, and influence imbalances may emerge. Large OEMs, major suppliers, or platform vendors could shape roadmaps in ways that smaller participants find difficult to counter.
Competition and regulatory optics
The collaboration is framed as pre-competitive, but large-scale cooperation among direct competitors always carries latent antitrust sensitivities, depending on scope and information sharing. No regulatory intervention has been reported in the last 14 days, but governance discipline will matter.
Broader industry context
CES 2026 as a signaling moment
The timing aligns with a wave of CES messaging around software, AI, and digital platforms in vehicles. Suppliers such as Bosch have publicly reinforced expectations of strong growth in software and services revenue, underlining why shared cost structures are increasingly attractive.
European coordination with global reach
VDA’s involvement highlights a European coordination angle, but the participant list is global. This suggests the initiative is less about regional standard-setting and more about aligning the entire automotive value chain around common software foundations.
Outlook
In the near term, the significance of this expanded pact will depend less on headline membership numbers and more on execution:
- the maturity and adoption of shared software components,
- visible use in real vehicle programs,
- and the ability of participants to balance openness with competitive differentiation.
Regardless of outcome, the expansion itself is a clear signal that software collaboration has moved from experiment to necessity in the automotive industry.