Germany's Automotive Software Strategy in 2026: VW, BMW, Mercedes, and the SDV Pivot

The German automotive industry's software pivot is the largest single technology transition any major industry is attempting. Where it actually stands in 2026.

Germany's Automotive Software Strategy in 2026: VW, BMW, Mercedes, and the SDV Pivot

The German automotive industry is attempting the largest single software transition in any major industry’s history. The pivot from mechanical-engineering-centric vehicle development to software-defined-vehicle (SDV) architecture has been more difficult, more expensive, and more time-consuming than initial projections suggested. By 2026 the pivot is real but uneven — Mercedes is materially ahead of BMW which is materially ahead of Volkswagen — and the cumulative competitive disadvantage versus Tesla, BYD, and the Chinese new-energy-vehicle entrants is real.

I want to walk through where each major German OEM actually sits and what the broader competitive landscape looks like.

Germany automotive software

What “software-defined vehicle” actually means#

A few definitional points to anchor the discussion.

A traditional vehicle has dozens of distinct ECUs (electronic control units) from dozens of different suppliers, each running its own firmware. Software updates require physical service visits or are not possible. Each vehicle generation is largely fixed at production date.

A software-defined vehicle has consolidated computing — typically a small number of high-performance compute units (HPCs) handling the vehicle’s functions, with the supplier-provided ECUs serving as thin actuators. The software stack is increasingly developed by the OEM rather than by the suppliers. Over-the-air updates are routine. The vehicle’s capabilities can evolve substantially over its lifecycle.

Tesla pioneered the architecture at scale. The Chinese EV makers (NIO, Xpeng, BYD, Li Auto) have adopted similar architectures with varying degrees of maturity. The German OEMs have been catching up.

Volkswagen Group and CARIAD#

VW’s CARIAD (the in-house software subsidiary established in 2020) was meant to be the unified software platform across the VW Group brands (Volkswagen, Audi, Porsche, Skoda, Seat, Cupra). The reality has been more complicated:

  • The original timeline for the unified “VW.OS” software platform has slipped multiple times.
  • Specific high-profile launches (the Porsche Macan EV, the Audi Q6 e-tron) were delayed because of CARIAD software issues.
  • Leadership changes have been frequent.
  • The relationship with major Chinese partnerships (notably Horizon Robotics) and US partnerships (Rivian for software collaboration) has been an attempt to accelerate.

The 2024-2026 period has seen CARIAD increasingly focused on near-term deliverables rather than the original unified-platform ambition. The PPE (Premium Platform Electric) and SSP (Scalable Systems Platform) architecture has been the framework; the software work on top has been progressively more incremental.

The honest assessment: VW has been the slowest of the three major German OEMs on the SDV transition.

Mercedes-Benz and MB.OS#

Mercedes has been the most-advanced. MB.OS — the Mercedes-developed proprietary operating system — has been progressively deployed across the model range, with substantial new architecture in the recent vehicles (the new E-Class, the EQS, and the upcoming GLC variants).

Key elements:

  • Proprietary OS architecture rather than dependence on Android Automotive (which BMW has used).
  • Vertical integration of software, vehicle electronics, and the broader product.
  • NVIDIA Drive partnership for high-performance compute.
  • Substantial OTA capability for software updates.

The trajectory has been more measured than Tesla’s but has produced credible SDV deployment. Mercedes’ relative position versus the Chinese competition is the best of the three German OEMs.

BMW and Operating System 9#

BMW Operating System 9 (deployed from 2023) is the company’s current-generation software platform, built primarily on Android Automotive with substantial BMW-developed extensions. The OS architecture is more modular than Mercedes’ approach; the dependence on Google’s Android ecosystem is greater.

BMW’s position:

  • Substantial OTA capability is operational.
  • The strong relationship with Google’s Android is both an advantage (ecosystem leverage) and a strategic consideration (dependency on a US platform).
  • The Neue Klasse architecture for the upcoming 2025-2027 vehicles represents a substantial leap forward.

BMW’s overall position is between Mercedes and VW in terms of SDV maturity.

The supplier ecosystem#

The German automotive supplier ecosystem — Bosch, Continental, ZF Friedrichshafen, Schaeffler, and the long tail of Tier 1 and Tier 2 suppliers — has been substantially affected by the SDV transition. The traditional supplier model (supplying ECUs with embedded firmware) is being disrupted as OEMs consolidate computing and develop software in-house.

Suppliers have responded:

  • Bosch has invested heavily in software services and is increasingly positioning as a software-and-services supplier rather than only hardware.
  • Continental has split into multiple business units, with software increasingly central.
  • ZF Friedrichshafen has acquired and built software capabilities.
  • Smaller suppliers have been consolidating or pivoting.

The dynamic resembles what happened in the consumer electronics industry’s pivot to software-defined products — substantial supplier disruption with new winners and losers.

The Chinese competition#

The Chinese EV makers’ competitive pressure on German OEMs is real and increasing. BYD, NIO, Xpeng, Li Auto, and others ship vehicles with mature SDV architectures, competitive autonomous-driving features, and substantial software ecosystems. The pricing pressure in China specifically (where German OEMs once had substantial market share) has been severe.

The European market is more protected — EU import tariffs on Chinese EVs (imposed in 2024 after substantial WTO debate) have moderated the immediate competitive pressure. But the structural pressure remains.

What outsiders should pay attention to#

For non-German automotive observers:

  1. The SDV transition is hard, even for well-resourced companies. German OEMs have spent tens of billions on software programs. The work has produced credible products but on slower timelines than initial projections.

  2. Vertical integration of software is the dominant pattern — Mercedes’ MB.OS approach has produced better outcomes than the more outsourced approaches.

  3. Cross-OEM partnerships are emerging — VW-Rivian, the various China partnerships, the developing US/Korean cross-partnerships. The industry is increasingly cross-pollinating.

  4. Talent flow matters — German OEMs have struggled to attract and retain top software talent. Munich and Stuttgart are growing software hubs but compete with global tech employers.

What’s coming in 2026 and 2027#

Three things to watch:

The next-generation platforms — VW SSP, BMW Neue Klasse, Mercedes’ next architecture — will produce major releases through 2026-2028.

Autonomous driving capability — L3 conditional autonomy is increasingly being launched (Mercedes’ Drive Pilot is operational in specific regions). L4 highway autonomy is the next frontier.

The cross-OEM partnerships continue to evolve.

Where pdpspectra fits#

Our automotive and embedded systems work spans Europe and adjacent markets. We work with OEMs and suppliers on software architecture, embedded systems engineering, and the broader automotive-tech infrastructure.

Related reading: the Germany Industrie 4.0 post, the Japan manufacturing AI post, and the EV charging infrastructure post.


German automotive SDV pivot is the largest single industry software transition. Talk to our team about your automotive platform.