Honda and Nissan Rediscover Each Other, This Time Over Silicon Rather Than a Merger Agreement

Just fifteen months after Honda and Nissan walked away from a full merger, the two Japanese manufacturers appear to be edging back towards each other, though this time through the electronics architecture rather than the boardroom. According to local reports citing a source familiar with the matter, the companies plan to develop a shared software operating system for next-generation vehicles, built on Nissan's existing OS, and to standardise key electronic hardware including electronic control units. A formal agreement is expected within the month, following what the reports describe as encouraging progress in preliminary joint development work.

The rationale is straightforward enough. As the industry shifts towards software-defined vehicles, the cost of developing and validating the software stack, the ADAS suite, the connected services layer and the AI assistants that increasingly define a car's character has grown to rival, and in places exceed, the cost of the mechanical vehicle beneath it. For two manufacturers whose combined global scale still trails the leading Chinese groups and Tesla, and whose R&D budgets are stretched further by parallel electrification and software transitions, sharing the most expensive and least visible layer of the vehicle is one of the few levers left that does not require touching the brand.

That distinction matters more than it might first appear. A merger threatens identity, management structure and, inevitably, jobs, which is broadly why the Honda-Nissan tie-up fell apart in early 2025. Standardising an OS and a family of ECUs is a quieter proposition: customers never see it, dealers never discuss it, and each company can still claim its own styling, chassis tuning and marketing story sits on top. It is, in effect, cooperation at the layer where consumers have the least emotional investment and the most sensitivity to cost, which explains why it has proved politically easier to agree than a full corporate combination.

For automotive leaders elsewhere, the arrangement is worth watching as a template rather than a curiosity. If two competitors who could not agree on a merger can nonetheless agree to share the vehicle's software brain and its ECUs, the bar for horizontal software alliances across the industry looks lower than boardroom optics might suggest. The harder questions sit downstream: how governance of a jointly developed OS is structured when the two parties remain independent competitors in every other respect, how intellectual property and future differentiation are protected once the platform is common, and how Tier 1 suppliers are expected to design ECUs that serve two customers with potentially diverging feature roadmaps. Nissan and Honda's existing discussions on EV batteries and powertrain components suggest this OS agreement may be one strand of a broader industrial logic rather than a standalone deal.

The formal announcement expected next month should clarify scope, but the direction of travel is already instructive. Software-defined vehicles were meant to be the ground on which manufacturers differentiated themselves from rivals and from new entrants alike. Honda and Nissan's move suggests that, for cost reasons, at least some of that differentiation is being quietly outsourced to a shared foundation, with the real competition pushed further up the stack into features, services and the user experience layered on top of a common brain.