Honda and Nissan are putting more of their automotive future in software, and both have now turned to the same Silicon Valley specialist for help. Applied Intuition announced separate agreements with the Japanese automakers on October 6, bringing its Vehicle OS technology and development tools deeper into their next-generation vehicles. The arrangements do not mean Hondas and Nissans are about to run identical software, nor do they amount to handing control of either company’s vehicles to an outside technology supplier. Both automakers say their own engineers remain central to development. What the deals reveal is how urgently traditional manufacturers are trying to shorten software-development cycles, simplify increasingly complicated vehicle electronics and build cars that can continue gaining capabilities after leaving the factory.
Honda and Nissan Chose the Same Partner on the Same Day
Applied Intuition announced its expanded work with Honda and Nissan on October 6, putting the Sunnyvale, California-based company in an unusually influential position with two of Japan’s largest automakers. Honda will use Applied Intuition’s Vehicle OS and development tools as it works on a centralized, upgradeable software-defined vehicle platform. Nissan is using the same company’s technology to support its next-generation scalable software platform and what it calls AI-defined vehicles.
The arrangements are related by technology but are not described as one combined outsourcing contract. Honda’s announcement emphasizes accelerating its own internal development while retaining control over its vehicle architecture and software direction. Nissan similarly describes Applied Intuition engineers working alongside its internal engineering teams. That distinction matters. Applied Intuition is supplying software infrastructure, tools and engineering expertise, while Honda and Nissan remain responsible for what ultimately defines their respective vehicles. The result is closer to two automakers hiring the same highly specialized technology partner than two companies adopting one identical off-the-shelf operating system.
Applied Intuition Has Become a Major Automotive Software Player
Applied Intuition is relatively young compared with the companies now relying on its technology. Founded in 2017, the Silicon Valley company initially built simulation and development tools for autonomous-driving systems before expanding into broader vehicle software, AI, defense and other industries. By June 2025, a $600-million financing round and tender offer had valued the private company at $15 billion, more than double its previous $6-billion valuation. Reuters reported that its automotive customers already included major manufacturers such as Toyota and Volkswagen.
Its rise reflects an important shift inside the automotive industry. A company does not need to manufacture engines, transmissions or complete vehicles to become strategically important to automakers. Applied Intuition instead sells the software infrastructure used to build, simulate, test and deploy increasingly complex vehicle functions. Its Vehicle OS is intended to provide a common foundation across areas that traditionally required separate development environments. Honda and Nissan are therefore not turning to an unknown startup for a speculative experiment. Both have already worked with the company for years, and the latest agreements significantly deepen those relationships.
Honda’s Relationship With Applied Intuition Actually Goes Back to 2019
The Honda partnership did not begin with this week’s announcement. Applied Intuition says Honda became its first Japanese automaker customer in 2019. The latest agreement takes that earlier relationship much further by moving Applied Intuition’s technology into the foundation of Honda’s next-generation software-defined vehicle development. Engineering teams in Japan and Silicon Valley are expected to work together on a platform designed to be centralized, upgradeable and suitable for vehicles produced on a global scale.
One particularly important detail is that Honda wants the software architecture to work across different powertrains. Applied Intuition says its technology will support Honda development involving hybrids as well as other powertrain types, rather than being restricted to battery-electric vehicles. That has become increasingly relevant as automakers adjust EV timelines and continue investing heavily in hybrids. A software platform that can be reused across different vehicles could reduce the need to rebuild major portions of the electronic architecture for every model. For Honda, the objective is therefore broader than creating a better infotainment system. It is about changing the process used to develop the entire vehicle.
Nissan Is Expanding a Partnership That Started With Simulation
Nissan’s relationship with Applied Intuition began in 2020, when the automaker adopted the company’s simulation technology. The collaboration has since expanded from development tools into software that can run much closer to the vehicle itself. Under the latest arrangement, Applied Intuition will use Vehicle OS and AI-powered development tools to support Nissan’s scalable, open next-generation software platform. Its teams in Japan and Silicon Valley will work with Nissan engineers to shorten development timelines and reduce the complexity created by different hardware and software systems.
The progression from simulation to in-vehicle software is significant. Simulation allows engineers to test scenarios without waiting for a physical prototype, but Nissan now wants a development system that connects requirements, coding, testing, debugging and deployment. Applied Intuition demonstrated that approach with Nissan at AWS Summit Japan using a LEAF-based test vehicle. Audience members selected changes to the car’s welcome sequence and engineers implemented, validated and deployed them during the demonstration. Applied Intuition said a process that could conventionally take months was compressed into minutes. It was a controlled demonstration rather than proof that every production update can happen that quickly, but it illustrated the development philosophy Nissan is pursuing.
“Software-Defined Vehicle” Means Much More Than a Bigger Touchscreen
The term software-defined vehicle can sound like industry jargon, but the underlying idea has practical consequences. Nissan defines an SDV as a vehicle architecture in which software can control, update and extend a broad range of functions. Instead of designing most capabilities permanently around individual pieces of hardware, automakers increasingly want software that can operate across centralized computers and be changed after the vehicle is built. Over-the-air updates are one visible result, but they represent only part of the transformation.
The architecture underneath the dashboard is equally important. Traditional vehicles can contain numerous electronic control units responsible for different systems, often developed by different suppliers. Newer SDV designs increasingly consolidate computing and create standardized ways for software applications to communicate with hardware. Applied Intuition describes its Vehicle OS as a platform spanning domains such as controls, perception and other vehicle systems while supporting virtualized development and testing. For consumers, the company’s name may never appear prominently inside the cabin. Its influence could instead be felt through how quickly new functions arrive, how consistently systems communicate and how much a vehicle can change after purchase.
Honda Already Has Its Own ASIMO OS—and That Has Not Simply Disappeared
Honda’s decision to use Applied Intuition raises an obvious question because the automaker has spent years promoting its own vehicle operating system. Honda introduced ASIMO OS as the core software platform for its software-defined vehicle strategy, borrowing the name from its famous humanoid robot. Honda has said the system is intended to coordinate areas including driver assistance, infotainment and vehicle dynamics while enabling functions to improve through over-the-air software updates.
Nothing in the new Applied Intuition announcement says Honda is abandoning that work. In fact, Honda executive Mahito Shikama explicitly says the partnership is intended to accelerate internal development while allowing Honda to maintain control over its architecture and software direction. Honda has separately been developing centralized electronic architecture and high-performance computing hardware, including work with Renesas on a system-on-chip targeting up to 2,000 TOPS of AI performance for future vehicles. Exactly how Applied Intuition’s Vehicle OS will be layered with Honda’s existing ASIMO OS technologies has not been fully detailed publicly. The safest interpretation is that Applied Intuition is becoming a major enabling partner inside a platform Honda still intends to shape itself.
Nissan Is Building Its Own Scalable Open Software Platform Too
Nissan is taking a similarly proprietary approach. Its Nissan Scalable Open Software Platform consists of three major elements: an in-vehicle operating system, a cloud-based data foundation and a software-development environment. Nissan says the architecture allows applications to work across model lines while reducing dependence on differences in underlying hardware. A central ECU can coordinate vehicle functions, while the cloud side collects data that can be used to improve AI and software capabilities.
That platform is also the foundation for Nissan’s broader “AI-defined vehicle” strategy. The company describes AI-Drive as technology intended to interpret road conditions and make driving decisions, while AI-Partner is designed around the occupants, using connected services and information to personalize the experience. Nissan has said it would begin introducing its SDV platform during fiscal 2026 and evolve it in stages. Applied Intuition’s involvement therefore arrives while Nissan already has a defined architecture under development. The October announcement says Applied will support that platform and Nissan’s internal engineers, rather than replace the Nissan Scalable Open Software Platform with a generic system shared unchanged with other manufacturers.
Honda and Nissan Are Already Jointly Developing Core Software
The timing becomes more interesting because Honda and Nissan separately announced a significant joint-development agreement just over a month earlier. On August 31, the automakers said they would standardize multiple electronic control units for future software-defined vehicles, together with an in-vehicle operating system, important middleware and vehicle-control software. The resulting electrical and electronic architecture is planned for next-generation vehicles from fiscal 2029 onward. The companies said sharing foundational technologies should reduce development costs, improve R&D efficiency and create economies of scale.
That cooperation survived the collapse of Honda and Nissan’s proposed business integration in 2025. They chose not to merge, but continued a strategic partnership focused on electrification and vehicle intelligence. The fact that both are now working extensively with Applied Intuition therefore deserves attention. However, no public announcement says Applied Intuition has been selected as the single supplier for the Honda-Nissan joint SDV project. The companies may ultimately share important specifications while retaining different applications, interfaces and brand characteristics. Applied Intuition’s separate contracts should not be presented as evidence that every element of their future software will be identical.
The Bigger Prize Is Cutting Years of Automotive Development Friction
Traditional vehicle development can be painfully slow compared with consumer technology. A relatively small software change can travel through requirements, supplier coordination, coding, integration, testing and physical validation before reaching a customer. Applied Intuition’s pitch is that more of those stages can be brought into one development environment and tested virtually before engineers ever need a completed vehicle. Nissan’s LEAF demonstration offered an intentionally dramatic example, turning a workflow described as potentially taking months into a change deployed within minutes.
Honda is pursuing the same basic advantage from another direction. Its existing SDV program already uses virtual electronic control units so engineers can develop and test software without waiting for final physical hardware. Honda has described scenarios in which software can be validated simultaneously across hundreds or even 1,000 virtual vehicles. Those approaches matter because modern cars are expected to support more driver-assistance functions, personalization and connected features while still meeting demanding reliability standards. Speed is useful only if validation keeps pace. The real competitive advantage is not simply writing code faster, but shortening the complete route from development to dependable production software.
The Same Software Partner Does Not Mean Hondas and Nissans Will Feel the Same
For buyers, the most important question is whether common software foundations eventually make cars better rather than merely cheaper to develop. Honda emphasizes personalization, integrated vehicle dynamics and continuous upgrades. Nissan is pushing its AI-defined vehicle idea, with software intended to understand both driving conditions and occupants. Those experiences could remain substantially different even if some foundational technology, development tools or electronic architecture becomes standardized behind the scenes.
The unanswered questions are just as important as the announcements. Neither new partnership spells out detailed financial terms, a complete production-model rollout or exactly how every existing proprietary operating-system component will interact with Applied Intuition’s Vehicle OS. The Honda-Nissan joint platform planned for fiscal 2029 adds another technical layer whose relationship with the two Applied Intuition arrangements has not been fully disclosed. What is clear is the direction of travel. Honda and Nissan increasingly view software-development speed as a core competitive issue, and both believe outside expertise can help without surrendering control. In the next generation of cars, some of the most consequential suppliers may be companies whose components cannot be seen when the hood is opened.
