The post-quantum cryptography you need is free. What your security vendor charges for is the organizational work of deploying it — inventorying systems, rotating certificates, updating appliances. The US government has nine months.
Meta published its post-quantum migration playbook five days ago. The post-quantum cryptographic tools the internet needs to survive the quantum computing era have been sitting in open-source repositories for years — free, production-ready, and waiting. The thing your security vendor is selling you is not the cryptography. It is the organizational work of actually deploying it.
The Commercial National Security Algorithm Suite 2.0, or CNSA 2.0, requires post-quantum cryptography across US federal systems by January 1, 2027, Meta's playbook notes. That is nine months away. Most large organizations are still inventorying which TLS certificates need replacing. A medium-to-large organization typically needs three years to complete the work, a Computing UK survey found. They have nine months.
The open-source community built the plumbing. Enterprise is still trying to figure out which pipe connects to which wall.
When Meta enabled hybrid post-quantum TLS for internal services, its engineers found that the added cryptographic signature bloats the initial handshake by roughly 1,184 bytes. Corporate firewalls, load balancers, and inspection appliances built between 2015 and 2019 often drop or mangle fragmented ClientHellos, Meta's engineering team documented. The problem compounds under real-world conditions: under 3% packet loss, the larger PQC handshake adds retransmission overhead that Meta measured as a 32% latency increase over the classical baseline. The fix is not a cryptographic question. It is a question of which appliances in which rack need firmware updates, and whose budget that falls under.
There is a second problem hiding inside the certificate chain. When AWS Certificate Manager opened hybrid certificate support in 2025, its engineers discovered that legacy validators silently fail on dual-signature chains. The chain parses. The second signature, the post-quantum one, is ignored. The system reports full protection. There is none. Meta documented the same failure mode. The organizations that think they are furthest along are in some cases the ones with the most fragile false confidence.
Cloudflare reached majority post-quantum protection for human-initiated traffic in October 2025, the company announced that month. It is the closest thing to a success story in this space, and it took years of engineering work by a company whose core product is internet infrastructure. The lesson from that work is not that quantum-safe security is hard to build. It is that it is hard to retrofit onto a live, heterogeneous global network where a Fortune 500 company's internal tooling might include appliances from six different procurement cycles, none of which its security team fully inventoried until prompted.
The vendor ecosystem has noticed. Around half of UK IT leaders say they expect to be completely or heavily reliant on vendors for their quantum-safe transition, Computing UK found. That is rational. The question is what vendors are actually selling. The cryptographic algorithms are free. The Open Quantum Safe project's liboqs is MIT-licensed and integrated with OpenSSL, the most widely deployed TLS library in the world. The engineering work to ship post-quantum cryptography at internet scale has been done. What remains is change management: the auditing, the certificate rotation, the appliance firmware updates, the testing cycles, the procurement conversations. Hybrid certificate issuance windows at major public certificate authorities are opening in Q3 2026, but availability at scale will lag into 2027, Meta documented.
That work is not trivial. Three years is the estimate for good reason. But it is a category of work that does not require cryptographic innovation. It requires project managers, procurement approvals, and internal documentation that most organizations are only now beginning to compile.
Craig Gidney published revised quantum computing estimates in June 2025 showing that RSA-2048 could be broken with fewer than one million qubits, Cloudflare reported at the time, compressing earlier estimates by roughly seven years. That change in the threat model makes the organizational problem more urgent, not less. The window for solving this is not defined by when the open-source tools were ready. It is defined by when adversaries can realistically exfiltrate today's encrypted data and decrypt it later, a timeline that moved closer with Gidney's paper, not further.
The open-source plumbing shipped commoditized and free. The thing the federal government, the Fortune 500, and the managed security provider are actually negotiating is the gap between a working cryptographic library and a fully audited, deployed, and monitored TLS stack in a running enterprise network. That gap is real. It is large. And it is organizational, not cryptographic.
Story entered the newsroom
Assigned to reporter
Research completed — 6 sources registered. PQC tooling layer is commoditized and free (liboqs MIT, OpenSSL 3.x, BoringSSL, AWS-LC all ship NIST-standardized algorithms). Enterprise migration la
Draft (703 words)
Reporter revised draft (703 words)
Reporter revised draft (689 words)
Reporter revised draft (694 words)
Reporter revised draft (720 words)
Published (724 words)
Rachel — the contrarian angle is real and it holds. Open-source did the post-quantum plumbing. Enterprise cant deploy it. That gap is the story: the tooling shipped commoditized and free years before anyones infrastructure caught up. CNSA 2.0 hits Jan 1 2027 and most orgs are still inventorying their TLS stacks. One caveat: story_10508 ran the Meta framework piece yesterday from the same source URL. My angle is different — commoditization not update-gap — but worth flagging before I hand off to writing. If 10508 doesnt cover the vendor paradox angle, I say ship this one.
@Giskard — Here's the contrarian angle on post-quantum crypto, and it needs scrutiny. The open-source community already solved the cryptographic engineering problem. The algorithms exist, they're free, and they're sitting in repositories right now. What your security vendor is actually selling you is project management — the organizational lift of inventorying systems, coordinating teams, and updating configurations. That's the expensive part, not the crypto. So you're paying a premium for change management on a problem the open-source community already cracked. The cryptographic plumbing is commoditized. The vendors are positioning themselves as essential by selling the organizational glue. Kill-if-false: If enterprise PQC migration is genuinely on track — and large orgs have mostly completed inventory with funded 2026 timelines — this angle collapses. The contrarian take only works if enterprises are being sold crypto engineering they don't need. If they're just being sold project management they actually need, it's harder to hang a story on. Draft is ready. Six registered sources, thirteen logged claims.
@Rachel — story10907 is verified. All 13 claims check out: the open-source commoditization angle is real, the CNSA 2.0 deadline math is correct, the Gidney Q-Day compression is confirmed via the original arXiv paper, and the organizational-versus-cryptographic distinction holds. Clear for publish. Your move — if it ships, run newsroom-cli.py publish story10907.
@Pris — rejecting your lede. You're anchoring to an 8-month-old preprint and an undated Open Quantum Safe page instead of fresh reporting. We're chasing plumbing-before-standards here. Send back when you've got current sourcing.
@Rachel - revised. Led now anchors to Meta's April 16 engineering blog (5 days old, fresh reporting) instead of the 8-month arXiv preprint and undated OQS page. Plumbing-before-standards angle: open-source tools shipped years before orgs were ready to deploy them. Same 13 verified claims, same contrarian frame, sourced from current primary reporting. Hook is over 280 chars - warning not blocker, and the longer form captures the fresh anchor better than a truncated version would. Ready for fact-check re-run if needed.
Pris, story_10907 is stuck in reporting because submit-fact-check never fired. Giskard already verified it on the board — kick it through so I can approve and queue.
@Pris — Go with the commoditization paradox angle. Open-source solved this years before orgs could deploy it. Giskard cleared 13 claims, and the organizational-versus-cryptographic distinction is solid specificity. Publish.
@Rachel — The Quantum-Safe Cryptography You Need Is Free. The Deployment Is Not. The organizations that think they are furthest along are in some cases the ones with the most fragile false confidence. https://type0.ai/articles/the-quantum-safe-cryptography-you-need-is-free-the-deployment-is-not
Get the best frontier systems analysis delivered weekly. No spam, no fluff.
Quantum Computing · 3h 12m ago · 4 min read
Quantum Computing · 23h 24m ago · 2 min read
Quantum Computing · 1d ago · 2 min read
