Why 2026 could mark a turning point for software-defined vehicles

Software-defined vehicles are a strategic turning point for the automotive industry. Yet 2026 could be the year when it becomes clear which manufacturers are able to translate ambitious SDV concepts into robust, scalable systems — and which struggle with organisational and technical legacy structures.

In the LinkedIn post “Top SDV trends for 2026: Insights from Eclipse SDV Ambassadors”, Filipe Prezado, Eclipse SDV Working Group Ambassador, and Martin Schleicher, Eclipse SDV Ambassador, outline what they see as the next phase of SDV development: less vision, more delivery. We spoke to Martin Schleicher to better understand what this shift means in practical terms

Hybrid architectures instead of a radical reset

One of the key SDV trends for 2026 is the move towards zonal architectures. However, Schleicher does not expect a disruptive break with existing systems. Instead, hybrid zonal–central architectures are likely to dominate, combining central compute units with gradually introduced zonal concepts.

The main reason, he argues, lies in economic reality. “OEMs are increasingly focused on costs, both development costs and unit costs,” Schleicher explains. Fully new architectures are only viable if they deliver clear economic benefits. In practice, most manufacturers will pursue an evolutionary migration of existing electrical and electronic architectures — optimised, adapted and extended with zonal elements, but not rebuilt from scratch.

This reflects a pattern already visible in many SDV programmes in 2025. Transformation must remain compatible with platform cycles, variant logic and industrial scale. Architecture decisions are therefore driven not only by technology, but also by business constraints.

Artificial intelligence delivers its biggest impact in engineering

Artificial intelligence is another widely cited SDV trend. However, Schleicher sees its most immediate leverage not in new in-vehicle features, but much earlier in the development organisation.

“From my perspective, the biggest gains are in software development and validation,” he says. Productivity improvements through AI — for example in test automation, code analysis or fault resolution — can become visible within weeks or months. AI-based vehicle functions, by contrast, often show their impact only after series production, sometimes three years later or more.

As a result, AI becomes less of a feature generator and more of a productivity engine for the SDV factory. OEMs aiming to gain speed in 2026 need to industrialise AI first in their toolchains and development processes.

How SDV maturity can be measured in 2026

The central question remains: how can SDV maturity be assessed beyond roadmaps and marketing claims? For Schleicher, the answer is operational and measurable.

SDV works, he argues, “when an OEM is able to deliver new or fixed software regularly, in short cycles — monthly or quarterly — to a large vehicle fleet.” Fast feature rollouts are just as important as the ability to address defects and security issues quickly.

Another indicator of maturity is regional flexibility. OEMs must be capable of offering “regionally differentiated software on the same vehicle architecture”, as customer expectations vary significantly between markets such as the US, Europe and Asia. In this sense, SDV becomes measurable through release cycles, fleet impact and response speed — not through architecture slides.

What to expect at the Automotive Computing Conference 2026

On 24 and 25 March 2026, the Automotive Computing Conference returns to Detroit. Industry experts from OEMs, suppliers and technology partners will discuss how SDVs, AI, virtualisation and new computing architectures are reshaping the automotive industry.

Benjamin Müller

SDVs and business models: cautious realism

SDV is not an end in itself for OEMs. The debate around monetisation and new revenue models has accompanied the concept for years, often focusing on feature-on-demand or subscription-based offerings. Schleicher takes a far more cautious view.

He identifies three core economic benefits of SDV. First, scale effects: the same software can be deployed across a large number of vehicles and platforms, including vehicles already in the field, whether for new functions, bug fixes or security updates. Second, speed: rapid update capability is particularly critical in the context of cybersecurity. Third, SDV enables functions that were not defined at the time of vehicle development, making software a tool for long-term customer retention.

When it comes to direct end-customer monetisation, however, Schleicher remains sceptical. “I am very cautious about software-based business models where end customers purchase significant additional software during the vehicle’s lifetime,” he says. Functional SDV architectures and reliable execution must come first before realistic demand for such models can be assessed.

2026 as a reality check for SDV

The trends for 2026 point to a clear shift from vision to execution. Hybrid architectures prevail for cost reasons, artificial intelligence delivers its fastest impact in engineering, and SDV maturity is measured by release capability and fleet-wide impact. Business benefits are more likely to come from scalability and customer retention than from short-term subscription revenues.

In this environment, international competition is accelerating. Schleicher describes it as a faster, more dynamic game that requires a new digital culture — not just new technology. As a result, 2026 is likely to be less about the most ambitious SDV strategies and more about identifying which OEMs are truly able to deliver software at scale.