Autonomous driving is entering a new software chapter. On November 2, 2026, TIER IV announced that it is spearheading Autoware 2.0 initiatives with the Autoware Foundation and the global open-source community, the same day the foundation released version 2.0 of its open-source autonomous driving software.
Autoware 2.0 brings end-to-end AI and hybrid driving stacks into the same system as established rule-based modules. That move gives developers a shared foundation for combining data-centric AI with conventional approaches instead of choosing one path and abandoning the other.
A Shared Architecture for AI and Rule-Based Driving
Autoware has traditionally used a modular pipeline for sensing, perception, localization, planning, and control. Its packages are organized into two layers: Autoware Core and Autoware Universe. The Autoware Foundation maintains Core as a curated set of stable, well-tested libraries, APIs, and interfaces, while Universe extends Core with additional features, experimental algorithms, and community contributions.
Autoware 2.0 builds on that architecture rather than replacing it. The new version brings rule-based and AI-based technologies into a shared architecture, giving teams a way to combine established software with newer end-to-end systems.
A new generator–selector architecture sits at the center of that approach. Multiple trajectory generators can run within the same system, and a selector chooses which output to use. Developers can therefore compose different driving technologies inside one software structure, creating hybrid systems that match a vehicle, application, or operating environment.
TIER IV described Autoware 2.0 as a significant evolution of open-source autonomous driving software, with an architecture designed to scale across different configurations of AI-based and rule-based systems. The company also highlighted a flexible indexing scheme for modular software integration and a ready-made Reference Design framework intended to support commercial adoption across vehicles, applications, and operating environments.
Shinpei Kato, founder and CEO of TIER IV, said, “Autoware 2.0 represents an important step toward the democratization of autonomous driving in the era of AI-defined vehicles.”
Kato also drew a line between open code and a complete industry platform: “Open-source software alone is not enough to transform the automotive industry. We need an ecosystem that connects AI, computing platforms, cloud infrastructure, and automotive software into practical solutions.”
Arm, AWS, and Red Hat Push the Ecosystem Forward
TIER IV’s Autoware 2.0 initiatives build on its existing collaborations with Arm, AWS, and Red Hat, linking the software release to computing platforms, cloud operations, and vehicle operating systems.
- With Arm, TIER IV is advancing computing platforms for Autoware 2.0 as a representative use case of Arm Total Design for Physical AI.
- With AWS, the company is advancing cloud-native development and operations environments for Autoware 2.0, building on its existing use of AWS cloud technologies.
- With Red Hat, TIER IV is advancing system integration of Autoware 2.0 with AutoSD, the open-source upstream project for Red Hat In-Vehicle Operating System.
These initiatives target different layers of the same challenge. AI needs computing platforms, developers need cloud-native tools and operations environments, and vehicles need software that integrates with in-vehicle operating systems. TIER IV said the combined effort will strengthen the technology ecosystem supporting Autoware 2.0 and expand opportunities for adoption and commercialization across the automotive industry.
Muhammad Zain Khawaja, president of the Autoware Foundation, said TIER IV has played a leading role in advancing Autoware. He also said TIER IV’s continued commitment to open-source development and industry collaboration is essential to the growth of the ecosystem.
Why the Timing Matters for Autonomous Driving
The push toward end-to-end autonomy arrives as AI reshapes the startup landscape around autonomous vehicles. Trucks VC, which specializes in early-stage investing, has fielded pitches from 81 new autonomous vehicle startups so far in 2026. That is two-thirds more than last year and enough to surpass the boom years of a decade ago.
Trucks VC argues that the industry is in the middle of a second, even bigger AV wave fueled by technological breakthroughs and AI. Puneeth Meruva said, “For a long time AV companies were trying to go from what was AV 1.0 to AV 2.0, which is kind of this holy grail end-to-end architecture for AVs.”
“And I think the foundation models now provide a technical architecture that makes those end-to-end systems possible,” Meruva said. Foundational models can generalize across different environments and scenarios, a capability that can make autonomous vehicles cheaper and faster to deploy.
Open-source models such as Nvidia’s Alpamayo and Qwen’s general-purpose vision-language-action models have also made it easier for startups to get off the ground. Meruva said the barrier to entry is lower than ever before, with Trucks VC seeing startups deploy within a few months and with less than $1 million raised.
That momentum is reaching beyond major autonomous vehicle companies. Trucks VC has seen a growing number of startups pitch pure-play robotaxi businesses, with many positioning themselves as direct competitors to Waymo. Meruva said, “In this world, smaller, more niche autonomy companies can compete — maybe they’re not competing with Waymo on a global scale, but maybe they’re competing in specific regions or specific types of routes.”
The wider industry is moving at the same time. Bedrock Robotics raised $600 million at a $4.1 billion valuation, while Kodiak AI will deliver 75 self-driving trucks to DTL Transport starting in 2028. Toyota will manufacture AV-ready bZ4X vehicles and integrate Waymo’s self-driving system at its factory in Japan for robotaxi services in Japan, the U.K., and other international markets.
Autoware 2.0 now gives that expanding field a flexible open-source architecture for combining AI, rules, computing, cloud infrastructure, and vehicle software. The next phase will show how far developers and commercial partners can take that shared foundation across different routes, vehicles, and operating environments.
Based on
