Nissan Motor and Honda will jointly develop high-performance main ECUs and zone ECUs for use in next-generation software-defined vehicles (SDVs). The scope includes the in-vehicle OS and middleware, as well as core parts of the vehicle control software. The two companies announced the signing of the agreement on August 31, 2026, with a goal of applying a shared electrical and electronic (E&E) architecture to vehicles from fiscal 2029 onward. The basic research the companies began in 2024 has now moved into a phase aimed at bringing shared hardware and software into mass production.
While the announcement cites reduced development costs and faster speed, both companies have already built separate in-vehicle operating systems and development environments. To actually cut duplication through standardization, they must first decide something more fundamental than which company's technology to keep: where the boundary lies between the shared layer and each brand's proprietary layer, and who will oversee updates and certification.
From Joint Research to a Mass-Production Premise: Two Years of Groundwork
The two companies' SDV collaboration began on August 1, 2024, as joint research into "fundamental core technologies" for a next-generation platform. At the time, the plan was to complete basic research within roughly a year and then consider moving to mass-production development if the results warranted it. Standardizing ECUs and in-vehicle OS specifications had not yet been decided.
The two companies subsequently explored a full business integration but ended those talks in February 2025. However, the strategic partnership in intelligence and electrification established in August 2024 remained in place. Even after the plan to unify capital and management fell through, the joint SDV research was not severed.
| Timing | Stage announced by the two companies | Distance to mass production |
|---|---|---|
| August 2024 | Began joint research on fundamental core technologies | Would consider mass-production development if results warranted |
| February 2025 | Ended business integration talks | Strategic partnership continues |
| August 2026 | Signed joint development agreement for ECUs and software | Moving to build common specifications |
| FY2029 onward | Goal of applying to next-generation SDVs from both companies | Target models and regions not yet disclosed |
The basic research that began in August 2024 progressed into a joint development agreement in August 2026 aimed at mass-production application. That said, the fiscal 2029 timeframe is not a confirmed launch date. Mass production lies beyond finalizing specifications, validating them with prototype vehicles, and passing certification in each market.
Standardization Spans From ECUs to Vehicle Control Software
The scope this time covers the high-performance main ECU carrying the SoC and the zone ECUs that oversee each area of the vehicle. A configuration that concentrates computing in the high-performance main ECU, with each zone's ECU handling its surrounding area, makes it easier to port software across vehicle models than a design that stacks dedicated ECUs for each function. However, since the joint announcement does not disclose the number or layout of ECUs, the specific zone configuration cannot be confirmed.
The shared scope also extends to the in-vehicle OS, middleware, and core parts of the vehicle control software running on those ECUs. The in-vehicle OS manages computing resources and application execution, while the middleware provides common functions so that higher-level features don't depend directly on individual semiconductors or communication protocols. Once these are aligned, developers at both companies can use the same interfaces and test environments, making it easier to build out model-specific features.
On the other hand, the agreement states that even the "core parts" of vehicle control software will be standardized. Compared to unifying screens or voice services, this reaches into layers closer to vehicle motion and safety. While the scope for cutting development work expands, design decisions about which layer should differentiate driving feel and advanced driver assistance become harder. Neither the standardization rate nor which functions will remain proprietary has been disclosed.
ASIMO OS and Nissan's Proprietary Platform: An Unresolved Integration Question
In January 2025, Honda outlined a policy of placing its proprietary "ASIMO OS" at the core of its SDVs. For 2026 models, the plan was to consolidate ECUs into three domains—autonomous driving/driver assistance, basic vehicle control, and in-cabin information and entertainment—with further consolidation into a single high-performance ECU in the following generation. Honda has also built a development environment using virtual ECUs and virtual vehicles, allowing development and testing to proceed before physical hardware is complete.
The "Nissan Scalable Open Software Platform" that Nissan described in June 2026 likewise consists of a vehicle OS, a cloud-based data platform, and a development SDK. The vehicle OS absorbs hardware differences through a Vehicle API, using Linux, a real-time OS, and AUTOSAR depending on the purpose. Nissan, too, intends to consolidate vehicle control into a central ECU and validate it with virtual ECUs before physical vehicles are built.
| Comparison layer | Platform disclosed by Honda | Platform disclosed by Nissan | 2026 joint announcement |
|---|---|---|---|
| In-vehicle OS | ASIMO OS | Nissan Scalable Open OS | Building common specifications |
| E&E architecture | Moving from 3 domains to a central architecture | Consolidating control into a central ECU | Co-developing a high-performance main ECU and zone ECUs |
| Development environment | Virtual ECU / virtual vehicle | Data platform, SDK, virtual ECU | Shared scope of cloud and SDK not specified |
Both companies have their own in-vehicle OS and development platforms, but neither has disclosed how these will connect to the joint specification. Whether ASIMO OS is expanded, Nissan's platform is absorbed, or an entirely new shared layer is built with both existing OSes sitting on top will significantly affect transition costs and development organization. If the fiscal 2029 shared platform is to be built while continuing to support updates for existing vehicles, running the old and new systems in parallel for maintenance purposes is difficult to avoid.
The Bigger the Scale Benefit, the Harder the Update Responsibility Split
The advantage of joint development lies in reducing duplicate work and being able to spread ECU and semiconductor procurement, virtual validation, and over-the-air update systems across a much larger volume of vehicles. Fixes to shared components can be rolled out across multiple models more easily. On the other hand, defects or vulnerabilities in shared components could simultaneously affect vehicles from both companies. The faster changes are pushed out, the more precisely both companies must track who approves a modification and which vehicle configurations it can be distributed to.
Updating in-vehicle software involves more constraints than distributing smartphone updates. UN Regulation No. 155 covers manufacturers' cybersecurity management, while No. 156 covers software update management. These require recording target vehicles and software versions, confirming the compatibility, integrity, and authenticity of updates, and ensuring recovery and safe execution in case an update fails. Even once a shared OS exists, the safety responsibilities borne by each company and each vehicle model do not disappear.
Overseas, organizational models for running joint platforms have already been tested. The joint venture between Volkswagen and Rivian has built a development organization of more than 1,500 people to create a zone-based electronic architecture and software, with Volkswagen planning to use it in mass-production vehicles from 2027. Under Eclipse S-CORE, automakers and suppliers jointly develop a safety-critical core for high-performance ECUs as open source, allowing each company to direct its own workforce toward proprietary features built on top of it. Nissan and Honda have not yet indicated whether they will form a dedicated organization, how intellectual property will be allocated, or where the boundary lies for outside companies to participate.
Three Milestones to Watch Before Fiscal 2029
The first milestone is the name of the joint specification and its governance structure. If the lineage of the in-vehicle OS, the suppliers of SoCs and ECUs, and the change-approval process are disclosed, it will become easier to tell whether the two companies are simply combining existing technologies or building and operating a shared platform for the long term. Even without disclosed investment or savings figures, the existence of a dedicated organization and the scope of procurement can serve as indicators of how serious the effort is.
The second is prototyping and virtual validation. If software implementing the joint specification can run on virtual ECUs and connect to the different sensors and drivetrains of Honda and Nissan vehicles, the boundary between the shared layer and model-specific layers can be verified in implementation. Conversely, if model-by-model branching keeps increasing, the speed and cost advantages of standardization will erode.
The third is disclosure of target models and certification. This announcement covers SDVs but does not specify EV-only, and it discloses neither region and vehicle class nor projected volumes and launch order. Turning the fiscal 2029 goal into actual mass production will require defining target vehicles and entering the certification process, including cybersecurity and update management. Whether the shared platform can lower development burdens for both companies while still preserving product differentiation can only be concretely judged once that vehicle plan is announced.