Nissan and Honda Will Share the Computers Behind Their 2029 Vehicles
Nissan and Honda will jointly develop core vehicle computers, an in-car operating system, middleware, and control software for next-generation vehicles arriving from fiscal 2029.
Nissan and Honda are taking their software partnership from research to actual hardware.
The two Japanese automakers have signed a joint development agreement covering the central computers and foundational software for their next generation of software-defined vehicles. The shared electrical and electronic architecture is planned for vehicles from both companies beginning in fiscal 2029.
This is not a vague promise to cooperate on apps or infotainment. According to the joint announcement published by Honda, the companies intend to establish common specifications for multiple core electronic control units, an in-vehicle operating system, key middleware, and vehicle-control software.
In plain English, Nissan and Honda want to share more of the digital plumbing underneath future vehicles while keeping the finished products distinct.
What Nissan and Honda Are Developing Together
Modern vehicles can contain dozens of electronic control units, each responsible for a particular group of functions. Software-defined vehicles consolidate more of that work into a smaller number of powerful computers connected through a centralized electrical architecture.
Nissan and Honda say their agreement covers two important types of hardware:
- High-performance main computers, built around system-on-chip processors and responsible for major vehicle functions
- Zone controllers, which oversee electronics in different physical areas of the vehicle
The companies will also work on the operating system that runs across those computers, the middleware that lets different layers of software communicate, and key vehicle-control code.
That scope matters. A shared infotainment skin would be easy to dismiss. Common core computers and control software reach much deeper into how a vehicle is engineered, updated, and supported over its life.
Neither automaker named a model, battery platform, supplier, or launch market. The announcement also does not say that every Nissan and Honda product from fiscal 2029 will use the common architecture. The careful wording is that the technology is planned for application in both companies’ next-generation software-defined vehicles from that point onward.
Why Automakers Are Sharing the Expensive Part
Software has become one of the auto industry’s most expensive competitive fronts. Automakers need enough computing power for advanced driver-assistance systems, digital cockpits, powertrain management, connected services, cybersecurity, and over-the-air updates. They also need to maintain that software for years after a vehicle is sold.
Doing all of that twice makes little sense when two companies face many of the same technical requirements.
Nissan and Honda say standardization should improve development speed, reduce costs, and create economies of scale. It could also reduce duplicated engineering work, leaving each company more room to differentiate the parts buyers actually see and feel: design, chassis tuning, cabin layout, powertrain character, and brand-specific features.
The partnership has been moving in this direction for two years. In August 2024, the automakers announced joint research into a next-generation software-defined vehicle platform, alongside broader work on electrification and components. Monday’s agreement turns that research topic into a defined joint-development program.
This Is Not a Nissan-Honda Merger
The distinction is important after the companies’ previous merger discussions attracted so much attention. This agreement does not combine the automakers, create a shared consumer brand, or confirm jointly developed vehicle models.
Instead, it resembles the kind of deep technical alliance that is becoming more common as software costs rise. The underlying architecture can be shared even if a future Nissan and a future Honda look, drive, and behave differently.
That separation will be the real test. Common foundations are useful only if customers still get products with clear identities. Nobody needs a Nissan and a Honda that differ only in badges and screen graphics.
There is also execution risk. A common specification can reduce duplication, but two large organizations still have to agree on priorities, development tools, suppliers, update schedules, and responsibility when software fails. The fiscal-2029 timing gives them room to solve those problems, while also showing how long major vehicle-software decisions take to reach production.
Why It Matters for EVs
The announcement applies to software-defined vehicles generally, not exclusively to battery EVs. Still, Nissan and Honda explicitly describe software as central to both vehicle intelligence and electrification.
That connection is straightforward. In an EV, software manages battery temperature, power delivery, regenerative braking, charging, range estimation, route planning, and often the entire cabin interface. Better integration between the vehicle’s main computers and those systems can improve efficiency and make meaningful updates possible after the vehicle leaves the factory.
Honda has been introducing ASIMO OS as the software foundation for its newest software-defined vehicles, while Nissan has been reorganizing future product development around shared platforms and software. Monday’s release does not explain how those existing efforts will fit into the common 2029 architecture, so it would be premature to assume one company’s system simply becomes the other’s.
What is clear is the strategic direction. Nissan and Honda have decided the least visible part of the car may be the part where cooperation delivers the most value. If they execute well, buyers should get more capable, better-supported vehicles without the brands surrendering what makes their products different.