Honda and Nissan Turn to Applied Intuition as Software-Defined Vehicle Race Accelerates

Two of Japan’s largest automakers have independently agreed on software. Honda and Nissan have each struck separate deals with US-based Applied Intuition covering its Vehicle OS and a suite of AI-assisted development tools, according to the latest roundup of software-defined vehicle developments.

The arrangement points to a growing pattern in the industry: rather than building every layer of vehicle software in-house, automakers are leaning on specialist suppliers to shorten development cycles and keep pace with faster-moving rivals. Applied Intuition’s toolset is designed to help manufacturers simulate, validate and deploy software at scale, areas where traditional OEM processes have often lagged.

Regulators are moving in parallel. NHTSA is reviewing its vehicle cybersecurity best practices, amid warnings that machine learning is driving down the cost of finding software vulnerabilities. The concern is a familiar one in the SDV era: as vehicles become more connected and more code-dependent, the attack surface expands, and tools that once belonged only to well-funded security researchers are becoming cheaper and more widely accessible.

On the standards front, the Linux Foundation has published a common software bill of materials (SBOM) framework aimed at automakers and suppliers. An SBOM is essentially an ingredient list for software, and a shared framework could make it easier to trace components across complex supply chains and respond quickly when a flaw is discovered.

Commercial vehicles are part of the shift too. LG Electronics will supply an integrated cockpit system for the New Trafic E-Tech Electric, which Renault Group describes as its first series-production van built on SDV architecture. The move underlines that software-defined thinking is spreading beyond passenger cars into the vans and light commercial vehicles that keep fleets moving.

Taken together, the developments suggest an industry reorganising itself around software as a core competency, with partnerships, regulation and open standards all converging on the same question: who writes the code, and who is accountable when it fails?