PQC Patents

What this means for you

Executive / Business Leader

Licensing exposure is part of vendor risk: the "Top assignee" view shows who has filed the most claims over the implementations your suppliers ship.

GRC / Risk & Compliance

A patent filing is dated evidence of prior work; "Filing activity over time" shows when each family of claims was first written down.

Developer / Engineer

Filter to "Core invention" and "PQC only" to see the constructions that carry real claims before you standardise your own envelope or hybrid format.

Security Architect

Use "Map to FIPS 203/4/5" to see which patents touch the standards you are designing against; hybrid schemes have their own filter.

Researcher / Academic

The "Corpus scope" control switches between all filings and the core-invention set; each patent opens with its claims, not just its abstract.

Certification & Validation Engineer

Use "Map to FIPS 203/4/5" to see which filings touch the algorithms a module implements; licensing is a question for the vendor, not for the lab.

IT Ops / DevOps

Patents change nothing you operate today; the licensing angle you need rides on the vendors in the migration catalogue.

Curious Explorer

A patent is a public description of an invention with a date on it — this is where the post-quantum ideas were first written down, searchable by title, assignee or number.

30 of the patents below touch ML-KEM, ML-DSA, SLH-DSA — the algorithms your own path uses — and they are held by 20 organisations.

What this does not tell you: whether any of it is enforceable against you. We record assignees and claims; we do not record licensing terms, patent-pledge commitments, or any history of assertion, and we are not in a position to say whether you owe anyone anything. Treat the list below as who to ask, and put the question to your own counsel.