Photo source: Honda Motor Co. Image from the joint Honda-Nissan release.

Honda and Nissan will use shared software and control units from 2029

Honda and Nissan have concluded a joint development agreement for the electronic components and core software of future software-defined vehicles, known in the industry by the abbreviation SDV. The release published on 31 August shows that the jointly developed electronic architecture is scheduled to reach both brands' next-generation models starting in fiscal year 2029.

The agreement does not mean a merger, nor the immediate launch of identical Honda and Nissan models. The two companies will, however, standardise a significant part of the technology that is not visible from the cabin: several electronic control units, the on-board operating system, key middleware elements and the software that controls the vehicle.

What Honda and Nissan will develop together

In a modern car, electronic control units, usually called ECUs, manage functions such as propulsion, charging, braking, climate control, assistance systems and communication between modules. Honda and Nissan will set common specifications for several central ECUs in the electrical and electronic architecture of future SDVs.

The companies also include in the project the in-car operating system, essential parts of middleware — the software layer that links applications and hardware — and vehicle-control software. Honda specifies that this includes high-performance central computers with SoC-type processors, and zone ECUs that coordinate different areas of the car.

For the driver, these components matter because they become the basis for software updates, digital functions, assistance systems and the integration of new equipment over the car's life. The manufacturers have not announced which European models will receive the technology first, nor which functions will be shared at interface level.

The first models are planned from fiscal year 2029

The E/E architecture, the name used for the car's electrical and electronic network, is planned for both brands' future software-defined vehicles from fiscal year 2029. In practice, that means the first launches can appear between 1 April 2029 and 31 March 2030, if the plan is kept.

Honda and Nissan have not yet communicated a calendar by model, market or plant. There is also no announcement regarding prices, availability in Romania or changes for cars already on sale.

Why the agreement matters for the European car market

Sharing the software platform and electronic components can cut development costs and shorten the cycle of creating new models. That is an important stake in a market where manufacturers compete not only through engines and design, but also through how quickly they introduce digital functions and software updates.

Honda and Nissan say they aim to combine engineering resources, improve development efficiency and obtain economies of scale. For buyers, the concrete effect will depend on how each brand turns this shared base into distinct products: more stable software, faster updates or better-controlled costs. Those outcomes are not guaranteed by the announced agreement and can be assessed only after the first models launch.

The agreement continues the technical collaboration the two groups have explored in recent years, after talks about a corporate integration did not lead to a merger. The current release is limited to joint development of the core technology and shows that the firms will continue to examine other forms of collaboration as well.

Frequently asked questions

When will the first Honda and Nissan cars with the shared technology reach the market?

The official plan targets fiscal year 2029, that is the period between 1 April 2029 and 31 March 2030.

Will Honda and Nissan cars be identical?

No. The agreement refers to standardising some electronic components and the core software. The two companies have not announced shared models or identical interiors.

What is a software-defined vehicle?

It is a car in which important functions are coordinated by a centralised software architecture, able to receive updates and integrate new functions more easily.

Source