Cloudflare's October 23 post puts a post-quantum Geo Key Manager in closed beta for its Data Localization Suite. General availability is planned for the first quarter of 2027. The post is the record.
Cloudflare's October 23 post puts a post-quantum Geo Key Manager in closed beta. General availability is planned for the first quarter of 2027.
The short version
A closed beta of a post-quantum Geo Key Manager for the Data Localization Suite. The company says general availability is planned for the first quarter of 2027, that customer keys unwrap only in the geography the customer chose, and that the construction is hybrid ML-KEM-768 and X25519. Requests that would unwrap a key out of region fail closed. The post says this does not, by itself, decide where traffic is routed. Quantum Computing Report and TSN retell the post.
Closed beta, with a quarter named
On October 23, 2026 Cloudflare posted that a post-quantum, geographically restricted key manager is in closed beta in support of its Data Localization Suite. The authors are Chetan Agrawal, Arka Nayan, and Erik Engstrom. The post says customer decryption keys should be unwrappable only by servers in the geography the customer chose. It says general availability is planned for the first quarter of 2027. It says the design uses hybrid ML-KEM-768 and X25519 because a production post-quantum attribute-based scheme was not available, and because customers do not need a large number of regions. ML-KEM-768 is identified as a NIST standard. Quantum Computing Report and TSN both date the beta to October 23 and the availability plan to that quarter. They are accounts of this post.Kimi's weight date is a different kind of promise.
A key region is not a traffic region
The post is explicit that this system controls where a wrapped private key can be unwrapped. It says other work decides where tunnels end, where traffic is inspected, and where plaintext is processed. Those are related, because traffic cannot be decrypted where the key cannot be unwrapped, and they are not the same switch. A customer who reads the beta as a complete answer to where data is processed has read past the paragraph that splits the jobs. TSN's account makes the same point as a caveat. This page keeps it: sovereignty in the post is a statement about keys.a TLS certificate binds a name.
Fail closed is the impact
Cloudflare says a server that does not have the regional key for a request rejects the request rather than unwrapping the key out of region. It gives the example of a Germany key that is not present in Spain or France. That example is the company's, and it is the impact a reader can check the design against: the failure mode is refusal, not a quiet decrypt somewhere else. This page does not describe how a server proves which region it is in, and it does not name the internal systems that move the keys. A news brief can state the failure mode without a component map.K-ISMS is a certificate program.
What the beta is not
It is not general availability. It is not a claim that every Cloudflare product already unwraps keys this way. The post says older Geo Key Manager controls still exist for CDN certificates, and that bringing this post-quantum design to that CDN path is separate work still in development. It says Data Localization Suite customers who regionalize CDN traffic can register interest in testing. A registration of interest is not enrollment. The first quarter of 2027 is a plan the post states, not a ship notice.Origin Range Requests are a different October Cloudflare post.
Harvest now, decrypt later is the threat named
The post's reason for post-quantum protection is that someone can store ciphertext today and wait for a quantum computer. Hybrid construction, ML-KEM-768 plus X25519, is the post's answer: confidentiality holds if at least one of the two components holds. That is a design goal stated by the vendor. It is not a proof this page performed, and it is not a statement that recorded traffic already on disk became safe on October 23. A beta does not reach back and re-encrypt the world's archives.
Who is in scope
Data Localization Suite customers, and specifically those the post invites to register interest if they regionalize CDN traffic. Everyone else is reading a beta announcement. Quantum Computing Report's readers and TSN's readers are reading retellings. A retelling that adds a guarantee the post does not make is not a second specification. This page did not find an independent review of the beta.
What stays off the page
The post contains a long account of how keys are provisioned. This brief does not repeat that account. Identifiers of internal systems, hardware identity checks, and the consequences of compromising a particular key are the post's engineering note, and they are not needed to say what shipped: a closed beta, a quarter for general availability, a hybrid of a NIST mechanism and X25519, and a fail-closed rule for out-of-region unwraps. Readers who need the design can read the post. Readers who need the status can stop here.the October 9 profiling post is earlier Cloudflare.
Two outside accounts
Quantum Computing Report states the closed beta, the suite, the hybrid, and the 2027 quarter. TSN adds that every security property in the announcement is Cloudflare's description of its own beta, and that a regulator will also ask about routing and inspection. Both additions match the post's own split. Neither is a lab report. Two of three sources are not Cloudflare, which is more than the Origin Range brief could say the same day. The measurements, such as they are, are still the company's, because the outside pieces do not add a number.
The limit
Closed beta. First quarter of 2027 as a plan. Hybrid ML-KEM-768 and X25519. Fail closed. Routing is a different control. The record is the October 23 post. The short answer this page will stand on is this: A closed beta of a post-quantum Geo Key Manager for the Data Localization Suite. The company says general availability is planned for the first quarter of 2027, that customer keys unwrap only in the geography the customer chose, and that the construction is hybrid ML-KEM-768 and X25519. Requests that would unwrap a key out of region fail closed. The post says this does not, by itself, decide where traffic is routed. Quantum Computing Report and TSN retell the post.
Sources
The reports this brief is filing. Futureweb did not republish them.
Questions
Is the post-quantum Geo Key Manager generally available?
No. The October 23 post says closed beta. It says general availability is planned for the first quarter of 2027. A plan is not a date on a calendar this page can circle.
Which algorithms does the post name?
Hybrid ML-KEM-768 and X25519. ML-KEM-768 is the NIST standard the post points at. This page does not describe the wrapping steps.
Does the product decide where a request is processed?
The post says key unwrapping is regional, and that routing, tunnel termination, and inspection are separate work. A key that stays in-region is not a map of every byte.
What does fail closed mean here?
Cloudflare says if the regional key the request needs is not on that server, the request is rejected rather than unwrapped somewhere else. That is the company's description of the failure mode.
Are the outside articles a second design?
No. Quantum Computing Report and TSN retell the October 23 post. TSN's caveat, that the properties are the company's own account of a beta, is a fair label. This page does not add a design the post does not contain.