Open Source Hardware Patent Pledges: Scope, Enforceability and Strategic Use

TL;DR
Patent pledges for open source hardware commit the pledgor not to assert certain patents against users of the hardware specification or implementation, often with defensive termination clauses. Pledges vary widely in scope (all patents vs. essential patents, worldwide vs. specific fields) and conditions. They are not FRAND licenses and do not create contractual rights for third parties in most jurisdictions. See our open source patent pledges guide by the PatentPaper research team for software-focused pledges and our 5G SEP FRAND licensing guide by the PatentPaper research team for comparison with standards-based licensing.

Typical Pledge Structures: RISC-V, Open Compute Project and CERN OHL

RISC-V International members have made pledges covering patents essential to the RISC-V ISA. The Open Compute Project has pledges from multiple hardware vendors. CERN OHL includes patent provisions in the license itself. Most pledges are unilateral public commitments rather than bilateral licenses; they often exclude patents not practiced by the pledgor's own products or limit the pledge to "compliant" implementations.

Example: A 2023 RISC-V core developer pledged not to assert its patents against any implementation that passes the official RISC-V compliance tests, but carved out patents covering proprietary extensions and power management techniques not required by the base ISA. A competitor using a non-compliant extension was later sued; the court held the pledge did not apply.

Defensive Termination and "Copyleft" Patent Provisions

Many hardware pledges include defensive termination: if the beneficiary sues the pledgor for patent infringement, the pledge terminates as to that beneficiary. Some pledges are "copyleft" in the patent sense: they require the beneficiary to make a reciprocal pledge on its own patents covering the same specification. These provisions are intended to prevent one-way exploitation of the pledge.

Enforceability: Third-Party Beneficiary Rights and Contract vs. Estoppel

Whether a third-party implementer can enforce a public patent pledge as a contract varies by jurisdiction. US courts have sometimes treated pledges as enforceable under promissory estoppel or as contracts with the standards organization as agent. In other jurisdictions, the pledge may be treated as a non-binding statement of intent. License agreements that incorporate the pledge by reference provide stronger rights.

Strategic Use: Reputation, Adoption and Selective Enforcement

Companies use pledges to accelerate adoption of a technology they support, to signal openness while retaining leverage against non-compliant or competitive uses, and to build goodwill with the open source community. Selective enforcement against parties who take the benefit of the pledge but do not contribute back or who assert patents against the pledgor is common and often explicitly contemplated by the pledge terms.

Interaction with Standards Essential Patents and FRAND

Some hardware specifications become de facto or formal standards. Pledges on those specifications may coexist with or substitute for FRAND commitments. Unlike FRAND, most pledges do not require payment of royalties and do not create an obligation to license on any particular terms beyond the pledge scope. When a specification is both pledged and subject to SEP declarations, the relationship between the two regimes must be carefully analyzed.

FAQ

Does a patent pledge give me a license I can enforce in court?

It depends on the pledge language and the jurisdiction. Some pledges have been enforced under estoppel or third-party beneficiary theories; others have been treated as non-binding policy statements. A direct license from the pledgor is safer.

Can the pledgor still sue me if I use the open hardware spec?

Yes, if your implementation falls outside the pledged scope (non-compliant, uses non-pledged patents, or you have triggered a defensive termination clause by suing the pledgor).

Are hardware patent pledges the same as open source software licenses?

No. Software licenses (Apache, GPL, MIT) typically include express patent grants. Hardware pledges are often separate unilateral statements that may or may not create enforceable rights. The legal effect is usually weaker than a well-drafted open source license.

Should my company make a patent pledge for our open hardware project?

It depends on your adoption goals and patent portfolio. Pledges can accelerate community uptake but reduce your ability to monetize or enforce against adopters. Consider scope limitations, defensive termination, and field-of-use carve-outs.

Do pledges cover patents acquired after the pledge date?

Some do, some do not. Read the specific pledge language. "All patents I now own or hereafter acquire" language is broader than "patents I own as of the date of this pledge."

How do pledges interact with my existing FRAND commitments?

They can overlap or conflict. If you have declared patents as essential to a standard and also pledged them under an open hardware pledge, the more restrictive commitment may control for compliant implementations. Legal review is essential before making overlapping commitments.

Which PatentPaper resources cover software patent pledges and SEP FRAND?

Our open source patent pledges guide and 5G SEP FRAND licensing guide by the PatentPaper research team provide comparative analysis of different commitment structures and their legal effects.

Review layer 1: Practical review notes for Open Source Hardware Patent Pledges: Scope, Enforceability and Strategic Use

Review layer 1: For open source hardware patent pledges, separate the legal basis, patent-office step, and commercial evidence needed in a dispute. Sources such as riscv.org, opencompute.org, ohwr.org help confirm fees, deadlines, term, and forum from primary material rather than secondary summaries.

Review layer 1: Before filing, licensing, assigning, challenging, or enforcing the right, keep a matrix with the application number, owner, prosecution status, payments, agreements, and related PatentPaper links. That record makes later decisions easier to defend.

Review layer 1: Check legal status before sending a notice.
Review layer 1: Save official receipts and office correspondence.
Review layer 1: Compare the main claim with the product actually sold.