Cloudflare announced on September 29, 2026 that it intends to become a public Certificate Authority issuing quantum-safe TLS certificates. You will not be able to get one until the first quarter of 2027. Both of those things are in the same press cycle, and the gap between them is the actual story.
I review tools for a living, which mostly means reading announcements and then waiting to find out whether the thing described in the announcement exists. This one is unusually honest about the waiting part. Cloudflare says production issuance of Merkle Tree Certificates starts in Q1 2027. That is a date, not a vibe, and it is far enough out that nobody has to pretend otherwise.
What was actually announced
Stripped of the framing, here is what we know from the company and the coverage:
- Cloudflare plans to become a public Certificate Authority, issuing both traditional and post-quantum certificates.
- The post-quantum format is Merkle Tree Certificates (MTCs).
- Production MTC issuance is scheduled for Q1 2027.
- The CA will run on an open-source platform.
- Cloudflare is acquiring a trusted certificate root from GlobalSign to smooth the transition.
That last item is the part I would underline if I were underlining things. Becoming a CA is not primarily a cryptography problem. It is a trust-distribution problem. Your browser trusts a specific set of roots, and getting a new root into those trust stores takes years of audits and review. Buying an existing trusted root from GlobalSign skips the line. It is a procurement decision doing the work that engineering cannot do on its own.
Why a new certificate format at all
Post-quantum signatures are big. That is the practical problem nobody mentions when they talk about quantum computers breaking encryption. The math holds up; the bandwidth does not. Swap today’s signatures for post-quantum ones inside the existing certificate format and every TLS handshake on the web gets heavier.
Merkle Tree Certificates are an attempt to get around that by restructuring how proof of trust is delivered rather than just substituting a bigger signature into the old envelope. Cloudflare is positioning MTCs as the faster path to quantum-safe TLS. I have not benchmarked them, nobody outside the people building this has, and I am not going to quote numbers What I can say is that the design goal is sensible and the problem it targets is real.
What this means for anyone building with AI tools
This is where I usually get asked whether something matters for the stack readers here actually run. Mostly agent frameworks, API gateways, orchestration layers, scraping pipelines, and the long tail of services those things call out to.
Short answer: not yet, and then suddenly quite a lot.
Agent stacks make an enormous number of outbound TLS connections. Every tool call, every model API request, every webhook. The certificate path is invisible until it is not. When certificate formats change, the things that break are the things that parse certificates in their own way — older HTTP clients, pinned certificate configurations, custom trust bundles baked into container images, and any library that made assumptions about certificate size or structure. If your agent runtime ships a vendored CA bundle from 2023, that is a future problem with a known due date.
Nothing to do about it today. Worth knowing the date exists.
The honest read
What I like: the open-source platform commitment, a specific ship date instead of a vague horizon, and dual issuance of traditional and post-quantum certificates so nobody is forced into a flag-day migration. Supporting both formats is the unglamorous choice and the correct one.
What I am reserving judgment on: everything about how this behaves in production, because production is sixteen-ish months away. We do not know pricing. We do not know issuance limits or the validation process. We do not know which clients, browsers, and language runtimes will handle MTCs by the time issuance begins, and that compatibility question determines whether any of this is usable or just available. A certificate format only works when both ends agree, and the far end of the internet is slow.
There is also a concentration question that nobody wants to be the one to ask. Cloudflare already sits in front of a large share of web traffic. Adding certificate issuance to that is efficient and also puts more of the trust chain in one place. Not an objection, just a tradeoff that should be said out loud rather than discovered later.
Announcing a certificate authority is easy. Running one that browsers trust, auditors approve of, and developers do not curse at is the hard part. Cloudflare has bought itself a trusted root and given itself a deadline. That is a more serious starting position than most quantum-readiness announcements, which tend to be slide decks about threats that arrive on no particular schedule.
Check back in Q1 2027. I will be the one with the benchmarks.
đź•’ Published: