Honda and Nissan will collaborate and utilize shared software in their vehicles starting in 2029.

      Eighteen months after their proposed merger collapsed over control issues, Honda and Nissan have decided to collaborate on the software used in their vehicles.

      The two companies signed a joint development agreement on Monday that pertains to electronic control units, an in-vehicle operating system, middleware, and vehicle control software, with the first models expected to be ready by fiscal 2029. This agreement is more focused than a merger and, from an engineering perspective, is more integrated. Standardizing core ECUs necessitates consensus on the computers that manage the brakes, steering, battery, and cabin, as well as the connections among them.

      Both companies presented their choice as driven by the need for speed and cost efficiency. The stated reasons were shorter development cycles and better investment returns, following what they described as thorough analyses of potential collaborations in the software sector. No details regarding costs or savings were provided, no suppliers were mentioned, nor were any executives quoted, and the specific ECUs to be standardized were not disclosed.

      Fiscal 2029 is crucial to consider. This timeline indicates that architecture work must be finalized well in advance of the first vehicle's arrival in showrooms, highlighting the long-term nature of such decisions and the limited scope for changes later on.

      The components being standardized are those that consumers do not see but deeply notice. Issues like a faltering operating system, failed over-the-air updates, or incompatible control units can severely impact the perception of a car's modernity.

      The challenge both companies are tackling is significant and extends beyond Japan. Modern vehicles depend on tens of millions of lines of code across various controllers, with manufacturers facing high costs associated with solo development that were not an issue for engines.

      The solution lies in scale. Arm has suggested that the industry requires unified foundations rather than numerous custom stacks, which is exactly what the two automakers achieving operating system collaboration represents.

      Competitive pressure is emerging from a specific source. BYD has developed its own 4nm driving chip and is incorporating LiDAR into a $10,000 vehicle, a level of vertical integration that neither Japanese firm can independently achieve.

      Chinese brands have been rapidly gaining market share in Europe, largely due to the software experience they offer in vehicles. Consumers comparing a Chinese EV to a Japanese counterpart in 2029 will likely evaluate their operating systems as much as their drivetrains.

      What makes this agreement particularly significant is the context from which it arises. Merger discussions fell apart in February 2025 when Honda suggested making Nissan a wholly owned subsidiary, a proposal Nissan rejected, leading both companies to back away.

      Collaborating on an operating system without shared ownership poses a greater challenge. Future disagreements over features, release timelines, or security updates will need to be resolved between two independent entities with differing product cycles and issues.

      There’s a well-known precedent in the industry. Shared platforms have been successful for decades, involving fixed specifications for metal and tooling, while software decisions continue long after the vehicle is launched.

      Nissan faces more pressing concerns, having spent the time since the merger’s failure restructuring. Honda, being the larger and more stable partner, reflects the imbalance that contributed to the merger's downfall and remains unchanged.

      Both companies have expressed their intention to continue seeking collaboration in other areas, mentioning shared goals like carbon neutrality and reducing traffic fatalities. These are ambitions rather than formal agreements, and this distinction is important in their announcement.

      What is currently in place is a signed document, a clearly defined technical scope, and a timeline leading to 2029. Whether this collaboration endures will depend more on the two organizations rather than strictly on the software itself.