Software Defined Vehicles

Zonal architecture

VW and Rivian advance zonal SDV architecture

2 min
The Volkswagen ID.Every1 will launch in 2027 as the first volume model using the new architecture.

Volkswagen and Rivian report major progress on their new zonal SDV architecture. First reference vehicles are ready for winter testing in 2026, with the ID.Every1 set to launch in 2027 as the first model using the platform.

The joint venture “Rivian and Volkswagen Group Technologies” has been developing a zonal software-defined vehicle architecture since November 2024. Its goal is to create a modular electronics platform that consolidates vehicle functions in software rather than relying on numerous distributed control units.

High-performance central computers form the core of the architecture. They control individual vehicle zones, replace many traditional ECUs and support functions such as automated driving, infotainment and connected services. The architecture is designed as a long-term base across Volkswagen Group brands while also supporting Rivian’s future model generations.

Key takeaways

· Volkswagen and Rivian are developing a modular zonal electronics and software platform for future software-defined vehicles.

· High-performance central computers reduce system complexity and unify software across brands.

· Winter testing of reference vehicles begins in early 2026.

· The Volkswagen ID.Every1 will launch in 2027 as the first volume model using the new architecture.

· Volkswagen plans to roll out the system across its SSP platform for up to 30 million vehicles.

· Rivian will adopt the architecture for R2, R3 and R3X and upgrade selected existing vehicles.

· Total Volkswagen investment in Rivian and the joint venture will reach up to 5.8 billion USD by 2027.

What role the zonal vehicle architecture will play

The zonal structure groups functions by physical zones within the vehicle. Instead of isolated domain controllers, zonal gateways connect to central compute units. This reduces cabling, lowers system complexity and simplifies integration.

For manufacturers, the approach enables scalable software deployment, faster development cycles and clearer separation between hardware and software. For customers, it means ongoing software updates and feature expansions over the vehicle’s lifetime.

Audi highlights the joint architecture as an important step for the entire Volkswagen Group. Early test vehicles are already operating, with development cycles now being aligned to the new software-first approach.

When tests start and which models are involved

Winter tests are scheduled for the first quarter of 2026. They will validate the architecture’s performance under extreme climatic conditions. Reference vehicles from Volkswagen, Scout and Audi are being prepared. Hardware and software specifications for these vehicles were completed in spring 2025. The Volkswagen ID.Every1 is a central focus; it will enter series production in 2027 as the first entry-level EV using the architecture.

How Volkswagen plans to integrate the architecture

Volkswagen will deploy the technology on the group’s Scalable Systems Platform (SSP). SSP is intended to serve as the base for up to 30 million vehicles. A unified software structure across brands will reduce duplicated development, improve scalability and support long-term cost reductions.

Rivian will integrate the SDV architecture into its upcoming R2, R3 and R3X models. It also plans to upgrade selected existing models where technically feasible. Both companies benefit: Volkswagen gains a proven zonal foundation and Rivian shares development investment with a global OEM.

FAQ

What is a zonal vehicle architecture?

A structure in which vehicle functions are grouped by physical zones and connected to powerful central computers, reducing complexity and enabling efficient software updates.

When do tests begin?

Winter tests start in the first quarter of 2026 using reference vehicles across several brands.

Which Volkswagen model will use the new architecture first?

The ID.Every1, entering series production in 2027.

Which Rivian models adopt the architecture?

Rivian’s R2, R3 and R3X will use it, with potential upgrades for existing models.

How much is Volkswagen investing?

Up to 5.8 billion USD by 2027.

How the joint venture is structured and organised

Founded in November 2024, the joint venture is owned 50/50 by Volkswagen and Rivian. Its mission is to deliver a modular zonal electronics platform and a central software stack for future software-defined vehicles. Audi and Porsche will be the first brands to introduce the architecture from 2027. Volkswagen models will follow later in the decade, including a new electric Golf expected around 2029.

Volkswagen will invest up to 5.8 billion USD in Rivian and the cooperation by 2027. This includes a 1 billion USD convertible bond, 1.3 billion USD for IP licences and joint venture shares, and up to 3.5 billion USD in milestone-linked funding. More than 1,500 employees work across several international development sites. Locations include Palo Alto, Irvine, Canada, Sweden, Serbia and a recently established hub in Berlin designed to support collaboration with European brands.

The organisational structure emphasises close alignment between software engineering, system architecture and product planning.

Technical basis of the cooperation

The partnership builds on Rivian’s zonal hardware and integrated software platform. A demonstrator vehicle, built in only twelve weeks, confirmed technical compatibility with Volkswagen components and platforms. This validation established a joint roadmap for group-wide integration.

What the SDV architecture means for Audi, Porsche and Volkswagen

Audi and Porsche will introduce the architecture in 2027, serving as early reference cases before wider Volkswagen Group deployment. Volkswagen’s SSP-based strategy will gradually adopt the architecture across further model series, with the ID.Every1 and a future electric Golf positioned as key volume models. The unified SDV platform aims to create consistent digital experiences, shorten development cycles and separate hardware and software evolution more clearly.