Honda and Nissan will share the software in their cars from 2029

Eighteen months after their merger fell apart over who would control whom, Honda and Nissan have agreed to share the software inside their cars.

The two signed a joint development agreement on Monday covering electronic control units, an in-vehicle operating system, middleware and vehicle control software, with the first cars arriving from fiscal 2029.

The agreement is narrower than a merger and, in engineering terms, more intimate. Standardising core ECUs means agreeing on the computers that run the brakes, the steering, the battery and the cabin, and on the interfaces between them.

Both companies framed the decision as a matter of pace and cost. Faster development cycles and more efficient investment were the stated reasons, after what they described as extensive studies of where collaboration in the software domain might work.

Neither disclosed what it will cost or save. No supplier was named, no executive was quoted by name, and the specific ECUs to be standardised were not identified.

Fiscal 2029 is the part worth sitting with. That is roughly three years from now for architecture work that has to be locked long before the first vehicle reaches a showroom, which tells you how far ahead this kind of decision is made and how little room there is to change it afterwards.

The pieces being standardised are the ones customers never see and never forgive. An operating system that stutters, an over-the-air update that fails, a control unit that disagrees with another: these are the faults that define whether a car feels modern.

The problem they are addressing is real and not specific to Japan. A modern car runs on tens of millions of lines of code across dozens of controllers, and every manufacturer is discovering that writing all of it alone is expensive in a way that engines never were.

Scale is the only available answer. Arm has been arguing that the industry needs common foundations rather than dozens of bespoke stacks, which is precisely what two carmakers sharing an operating system amounts to.

The competitive pressure is coming from a specific direction. BYD has built its own 4nm driving chip and is fitting LiDAR to a $10,000 car, which is a level of vertical integration neither Japanese company can match alone.

Chinese brands have been taking share in Europe at a record rate, and the software experience inside the vehicle is a large part of why. Buyers comparing a Chinese EV with a Japanese one in 2029 will be comparing operating systems as much as drivetrains.

What makes this agreement notable is the history behind it. Merger talks collapsed in February 2025 after Honda proposed making Nissan a wholly owned subsidiary, an arrangement Nissan would not accept, and the two walked away.

Sharing an operating system without sharing ownership is a considerably harder thing to sustain. Every future disagreement about a feature, a release schedule or a security patch now has to be resolved between two independent boards with different product cycles and different problems.

There is a precedent both will know well. Shared platforms have worked in this industry for decades, but they involved metal and tooling with fixed specifications, whereas software has to keep being decided long after the vehicle ships.

Nissan has the more urgent problems of the two, having spent the period since the merger collapse restructuring. Honda is the larger and steadier partner, which is the imbalance that sank the merger and has not gone anywhere.

The pair have said they will keep exploring collaboration elsewhere, naming carbon neutrality and the elimination of traffic fatalities as areas of shared interest. Those are aspirations rather than agreements, and the distinction is doing work in the announcement.

What exists today is a signed document, a defined technical scope, and a date in 2029. Whether it holds together until then is a question about two organisations rather than about software.