Encryption has a shelf life.
On September 29, 2026, Cloudflare announced its intent to become a public Certificate Authority, and said it will issue post-quantum Merkle Tree Certificates alongside traditional ones. Production MTC issuance is scheduled for the first quarter of 2027. Ars Technica called it one of the first authorities to issue certificates built on cryptography widely believed to hold up against quantum attacks.
That’s the whole announcement. No demo video, no waitlist, no “sign up for early access.” Just a company saying it plans to run trust infrastructure differently starting fifteen months out.
I review AI tools for a living, which means I spend most of my week watching companies ship things that are 30% product and 70% positioning. So I want to be clear about why I’m writing about TLS certificates on a site about agents: this is the kind of announcement that looks boring and matters more than most of what lands in my inbox.
Why an agent reviewer cares about certificates
Every AI agent you use is, underneath the personality, a machine that makes a lot of outbound HTTPS requests. It fetches pages. It hits APIs. It authenticates to tool servers. It does this thousands of times in a session without a human ever looking at a padlock icon.
Certificates are what makes any of that trustworthy. When an agent connects to an endpoint, the certificate is the only thing telling it that the server on the other side is the server it meant to reach. Humans can eyeball a URL and feel suspicious. An agent cannot. It takes the handshake at face value and moves on.
So the trust layer under agents is not a detail. It is the part that decides whether an autonomous system talking to the open internet is doing something sane or something exploitable. If that layer has a known expiration date, every agent architecture built on top of it inherits the problem.
What Cloudflare actually committed to
Two things worth separating.
- Cloudflare intends to become a public CA, which puts it in the business of issuing the certificates websites use to encrypt traffic and prove identity.
- That CA will support both traditional encryption and post-quantum Merkle Tree Certificates, with MTC issuance starting early 2027.
The dual-support part is the honest bit. Nobody is flipping a switch and migrating the web overnight. Certificates have to work with browsers, clients, load balancers, embedded devices, and a long tail of software that has not been updated since the last time anyone thought about it. Running both tracks in parallel is the only approach that does not break things, and it’s a sign the plan was designed by people who have to answer support tickets.
The part I’m skeptical about
Announcing intent in 2026 for a 2027 ship date is a long runway. I’ve watched enough roadmaps slip to know that a quarter named this far out is a direction, not a promise. I’d treat Q1 2027 as the optimistic end of a range.
There’s also the concentration question. Cloudflare already sits in front of an enormous slice of web traffic. Adding certificate issuance to that footprint means more of the internet’s trust decisions routing through one company. That’s not an accusation, it’s a structural observation. Fewer independent trust anchors is a tradeoff, and it’s the kind of tradeoff that reads as efficiency right up until the day it reads as single point of failure.
And I’d like to see the interoperability story before I call this solved. A certificate format only works if the clients on the other end understand it. An MTC that modern browsers accept and your agent’s five-year-old HTTP library chokes on is a compatibility bug waiting to show up in production.
Still, credit where it’s due
Most of the AI industry is optimizing for things you can screenshot. Quantum-safe certificate issuance is the opposite of that. There is no viral moment in it. The best possible outcome is that nothing visible happens and the web keeps working for another decade.
That’s infrastructure work, and the AI space has a chronic shortage of it. We have an abundance of agent frameworks and a shortage of people making sure the pipes those agents run through will still be sound when the threat model changes. Cloudflare is doing the unglamorous version, early, in public, with a date attached. That deserves more attention than it will get.
My take: treat this as a signal rather than a product. If you’re building agents that will still be running in 2027, the question to start asking your vendors now is what their post-quantum plan looks like. Cloudflare just gave you a benchmark to hold them against. Most of them will not have an answer, and that answer tells you something.
🕒 Published: