TIER IV Joins Open Invention Network 2.0 to Shield Open-Source Autonomous Driving From Patent Risk

Open-Source Self-Driving Gets a Patent Shield

TIER IV, the Tokyo company behind Autoware, the most widely used open-source software stack for autonomous driving, said on Friday, August 21 that it has joined Open Invention Network 2.0, a patent non-aggression framework designed to protect open-source software from patent litigation. The announcement is short, contains no product and no money, and is one of the more consequential pieces of autonomy news this week, because it addresses the risk that has quietly limited how far carmakers and suppliers are willing to build on open code.

What Was Announced

Open Invention Network, usually shortened to OIN, is a global patent community in which participants grant one another royalty-free cross-licences to patents that read on what OIN defines as the "Linux System," a list of open-source packages that began with the Linux kernel and has grown over two decades to cover much of the open-source infrastructure stack. Thousands of companies and organisations participate. In January 2026 OIN launched OIN 2.0, which TIER IV describes as expanding the scope of the Linux System and broadening the technologies the non-aggression framework covers.

TIER IV says it will use its participation to reduce patent risk for the partners building on Autoware, which it names as automakers, suppliers, and semiconductor makers, and to pursue what it calls a patent strategy that balances open-source use with protection of its own intellectual property. The company will take part in OIN's framework for patent non-aggression and what it describes as enhanced governance under OIN 2.0.

Where Autoware Actually Runs

Autoware's reach is easy to underestimate because it rarely appears under its own name. The stack has been used in low-speed shuttles, campus and last-mile delivery vehicles, research fleets at universities on several continents, and in the development platforms of automotive suppliers evaluating open alternatives to proprietary stacks. TIER IV's commercial model wraps the open code in services: reference vehicles, integration, a cloud platform for data and simulation, and operational support for fleets, which is how a company can sustain itself on software it gives away. The Autoware Foundation, established to govern the project independently of any single company, counts automakers, suppliers, semiconductor firms, and universities among its members.

That membership is the audience for Friday's announcement. A foundation member deciding whether to ship a production system on Autoware has to answer its own legal department's question about patent exposure, and until now the answer has been a bilateral one, negotiated deal by deal. OIN participation gives the ecosystem a collective answer for the first time.

Why Patents Matter More in Autonomy Than in Most Software

Autoware has been in development since its first release in 2015, built on Linux and ROS, the Robot Operating System, and is now stewarded by the Autoware Foundation while TIER IV remains its lead developer and commercial backbone, supplying software, vehicle procurement, and operational support around it. That lineage is exactly why patents are a live issue. Autonomous driving sits at the intersection of automotive, where patent portfolios are enormous and aggressively maintained, and software, where open-source norms assume code is free to reuse.

A supplier that builds a perception module on Autoware is exposed in two directions. It may infringe patents held by a competitor who also uses the open stack, and it may be pressured by a patent holder who has no interest in open source at all. The first risk is what OIN's cross-licence addresses: participants agree not to assert their patents against one another's use of the covered packages. For a company deciding whether to standardise on Autoware rather than license a proprietary stack, removing that risk from a large community of co-users is a concrete change in the decision.

The second risk, assertion by non-participants, is not solved by OIN and TIER IV does not claim it is. OIN's model works by recruiting enough of the industry that the remaining assertion risk becomes tolerable, and by maintaining defensive patent holdings that can be deployed against entities outside the community. How much of the automotive patent world ends up inside OIN 2.0 will determine how much protection Autoware users actually receive.

The Linux Precedent

The reason this is worth more than a paragraph is what OIN did for Linux. When the network was founded in 2005 by a group of large technology companies, enterprise adoption of Linux was slowed by uncertainty over patents. By building a community in which the largest users of Linux pledged not to sue one another over it, OIN made the platform safe enough for banks, telecoms, and governments to standardise on, and Linux went on to become the default operating system of servers, phones, and embedded devices.

TIER IV is making an explicit bet that Autoware can follow the same path in vehicles: an open foundation that automakers and suppliers trust enough to build products on, with the patent question handled at the community level rather than negotiated bilaterally in every contract. The company's own framing is that advancing autonomy with partners worldwide requires an ecosystem built on open source, and that such an ecosystem cannot exist while patent risk makes open code something legal departments tolerate rather than choose.

The Japanese Context

Japan's position in autonomous driving is distinctive. The country has a dense automotive industry, an ageing population that makes driverless mobility a policy priority rather than a curiosity, and a regulatory framework that has allowed Level 4 services in designated areas since 2023. Yet commercial Level 4 deployment has moved more slowly than in China or the United States, partly because Japanese automakers and suppliers have been cautious about committing to stacks they do not control.

An open foundation headquartered in Tokyo, governed by a foundation with Japanese industrial members, and now protected by a patent framework is an answer to that caution. It offers the domestic industry a path to autonomy that does not run through a foreign platform vendor, and TIER IV has been explicit that its recent work has focused on assembling automakers, suppliers, and semiconductor makers around Autoware as a shared foundation. The OIN move removes one of the remaining reasons for those partners to hold back.

What Suppliers Should Do Now

For a supplier or automaker already building on Autoware, the practical step is to ask OIN which packages in the 2.0 definition of the Linux System overlap with the components it ships, and to map its own patent portfolio against that list before deciding whether to join. Participation is a two-way pledge: a member gains freedom from assertion by other members on covered code, and gives up the right to assert its own covered patents against them. For companies whose competitive edge lies in perception models or planning algorithms outside the covered set, the trade is usually favourable; for companies whose patents sit squarely on the Linux System, it requires a board-level decision. Either way, the decision is now available to make, which it was not before Friday.

What It Does Not Do

Three caveats a reader should hold against the headline.

First, OIN membership is about the Linux System as OIN defines it. Autonomy-specific patents that fall outside that definition, on perception algorithms, planning methods, or sensor fusion, are not automatically covered by the cross-licence, and OIN 2.0's expanded scope has not been published in detail in the announcement. How much of Autoware's functional surface the definition captures is the question that determines the real value.

Second, TIER IV's statement that it will balance open-source use with protection of its own intellectual property is a reminder that the company holds patents too. Joining OIN does not mean giving them up; it means agreeing not to assert them against other participants' use of covered code. Partners should read the distinction carefully.

Third, the announcement contains no named partners, no deployment figures, and no commercial terms. It is infrastructure news, not a contract, and its value will be measured by who else joins.

The Market Context

Autonomous-driving software is consolidating around a small number of stacks. Proprietary platforms from Nvidia, Mobileye, and the large Chinese players compete with open foundations, and Autoware is the only open stack with a foundation, a commercial steward, and a decade of deployments behind it, ranging from shuttles and delivery vehicles to research fleets. Japan's automotive industry, which has been slower than China's to field Level 4 vehicles commercially, has a particular stake in an open stack it can influence; TIER IV has spent recent years assembling automakers, suppliers, and chip companies around Autoware as what it calls an open technology foundation spanning software, AI, and automotive computing.

A patent non-aggression framework is the kind of unglamorous plumbing that decides whether such a coalition holds. It reduces the cost of saying yes to the open option, and it gives procurement and legal teams a reason they can write down.

What to Watch

The two signals that will show whether this matters are simple. Which automakers and tier-one suppliers join OIN 2.0 alongside TIER IV, and whether the Autoware Foundation's members begin citing OIN coverage in their own product decisions. If the answer to both is a growing list, open-source autonomy will have acquired the same legal floor that let Linux leave the lab. If the list stays short, the announcement will remain what it is today: one company doing the right thing early, and waiting for the industry to follow.

Image: TIER IV.

Disclaimer: This article is for general information purposes only and does not constitute investment, legal, or procurement advice. Readers should verify details with primary sources before making business decisions.