Cloudflare has announced the closed beta launch of a post-quantum geographically restricted key manager, a major enhancement designed to support its Data Localization Suite (DLS). The new system, known as PQ GeoKey Manager, serves as a cornerstone of the company’s data sovereignty solutions. It is engineered to guarantee that a customer’s decryption keys remain exclusively accessible within their designated geographic boundaries.
The mechanism achieves this by wrapping individual customer decryption keys in such a way that they can only be unwrapped and utilized by Cloudflare servers physically located within an approved region. While general availability for the product is slated for the first quarter of 2027, today’s rollout marks a critical milestone in Cloudflare’s ongoing mission to help clients achieve their data sovereignty objectives. Simultaneously, the launch advances the company’s broader roadmap to migrate all of its products and services to post-quantum cryptography.
The urgency behind this transition stems from the unique threat landscape facing modern organizations. Governments, financial institutions, healthcare providers, and defense organizations routinely process highly sensitive data that can retain its confidentiality requirements for years or even decades after creation. Encryption is widely mandated to protect this information from unauthorized access. However, when classical public-key encryption is deployed, malicious actors do not necessarily need an operational quantum computer today to compromise security. Instead, adversaries can intercept and store encrypted ciphertext, retaining it until future quantum computers become powerful enough to break the underlying public-key cryptography. This strategy, commonly referred to in the cybersecurity industry as "harvest now, decrypt later," poses an enduring risk to long-term data privacy.
For organizations bound by strict geographic requirements, resisting this looming threat represents only half of the challenge. At Cloudflare’s global scale, maintaining high availability necessitates replicating customer data across a vast network of servers spanning the globe. Yet, many data sovereignty regulations stipulate that specific categories of data must be processed exclusively within defined geographical regions. To comply, cloud providers must ensure that data remains end-to-end encrypted so that only servers operating within the legally mandated region possess access to the plaintext.
The Evolution of GeoKey Manager
Cloudflare originally pioneered the concept of geo-restricted transport layer security keys back in 2017 with the initial release of GeoKey Manager. That foundational tool granted customers direct control over the specific locations where their private TLS keys could be unwrapped across Cloudflare’s anycast network, providing stronger technical guarantees regarding where requests were decrypted. For example, a customer could choose to restrict private key unwrapping exclusively to data centers in India, ensuring that TLS signing for their requests occurred strictly within that regional network rather than across the global infrastructure.
The system underwent a significant evolution in 2022 with the introduction of ciphertext policy attribute-based encryption, commonly known as ABE. Rather than tethering encrypted keys to a static, predefined set of data centers, ABE allowed engineers to express geographic requirements using flexible attributes such as specific countries or regional blocks, including parameters like "region equals European Union" or "region equals Canada plus United States plus Mexico." This innovation meant newly authorized servers could receive matching decryption capabilities dynamically without requiring every individual customer key to be rewrapped.
However, that flexibility also presented new challenges and opportunities as the industry prepared for the post-quantum transition. Because no production-ready post-quantum attribute-based encryption schemes are currently available, and because typical enterprise customers rarely require complex, overlapping multi-region policies, Cloudflare opted for a streamlined architectural design that is easier to maintain, audit, and operate securely.
The newly introduced system relies on a hybrid protection scheme combining ML-KEM-768 and X25519 algorithms across two distinct tiers of keys. ML-KEM-768 is a cryptographic standard established by the National Institute of Standards and Technology, opening the door for highly sensitive organizations to adopt the technology with confidence. Under this architecture, a regional root key acts as a symmetric secret tied strictly to a single geographic region, while application-specific key pairs are derived from that root for individual services such as Cloudflare Gateway or Cloudflare Tunnel. This design effectively shields private-key material against harvest-now, decrypt-later attacks while rigorously preserving regional key-use boundaries.
Global Ciphertext, Regional Key Unwrapping
In its latest iteration, the key manager acts as the foundational architecture for Cloudflare’s comprehensive data sovereignty offerings. While separate network workflows determine where traffic tunnels terminate, where traffic is inspected, how requests are routed, and where plaintext processing occurs, every single one of these components ultimately depends on the region where a customer’s private key can be unwrapped. Because TLS traffic can only be decrypted wherever the corresponding private key is actively available, controlling the key’s location dictates the boundaries of data processing.
During the initialization phase, the edge key service running on each Cloudflare edge server verifies that it has successfully loaded every regional root key mandated by its specific operational configuration. If a configured key is missing, corrupted, or malformed, the edge service halts and refuses to start. Furthermore, once operational, individual requests fail closed—meaning Cloudflare actively rejects the request rather than risking an unauthorized out-of-region key unwrap—if the accompanying metadata identifies a regional root key that is not locally available in memory. For instance, if a request originating for Germany somehow attempted to trigger decryption in Spain or France, the operation would immediately fail because neither Spanish nor French edge nodes possess the regional root key assigned to Germany. This architectural enforcement guarantees that a regional root key never leaves its designated jurisdiction under any circumstances.
Cloudflare must balance high-performance delivery with uncompromising security for regionalized data at scale. The updated GeoKey Manager achieves this by logically segmenting the global network using post-quantum cryptography to enforce strict geographic boundaries on private key unwrapping. Customers simply select their desired region, and Cloudflare manages the underlying operational complexity required to ensure private keys are unwrapped exclusively within those geographic confines.

Operational Architecture and Key Hierarchy
The core function of the system is to control where wrapped private keys can be unwrapped and utilized on the data plane. It deliberately does not dictate where network requests are forwarded, where tunnels terminate, or where traffic inspection occurs, leaving those routing functions to companion regional services.
To achieve this, the architecture separates globally distributed wrapped private keys from the regional root keys required to decrypt them. Quicksilver, Cloudflare’s global configuration distribution system, efficiently pushes wrapped private keys and their associated metadata across the entire network. However, Quicksilver never distributes regional root keys. Instead, regional root keys follow a separate, highly controlled provisioning path, utilizing an on-premises Vault infrastructure managed directly by Cloudflare to store and deliver secrets only to edge servers explicitly authorized for each region.
Every wrapped customer private key carries explicit metadata identifying its service context, regional boundary, and epoch. The service context denotes the specific Cloudflare product utilizing the key, such as Access, Gateway, Tunnel, or the Cloudflare One client. The regional boundary defines the approved set of data centers where the key may be unwrapped, such as facilities located exclusively within Germany or across the European Union. The epoch identifies the generation of the regional root key to which the key belongs, allowing for seamless key rotation over time.
Before any edge server is permitted to receive a regional root key, the provisioning service evaluates multiple inputs to verify its legitimacy. The internal fleet management system, known as Zinc, continuously updates membership records for every edge server, accommodating network growth and server decommissioning in real time. As data centers undergo maintenance or capacity adjustments, these geographic definitions propagate swiftly across the network via Quicksilver.
Additionally, Zinc associates a registered hardware identity with every physical server and location, supporting compliance standards such as FIPS 140-3. Trusted Platform Module-backed identities, server inventory data, and regional configurations collectively determine which region an edge server belongs to and which regional root keys it is authorized to access.
When an edge server contacts the provisioning service and presents its verified hardware identity, it receives a secure token permitting it to retrieve only the authorized regional root keys for its specific physical location. Authorized servers then load these regional root keys directly into the Linux kernel keyring rather than persisting them on disk. Because this memory is strictly volatile, any machine restart purges the keys, requiring the server to re-authenticate and provision them anew. This design trade-off introduces minor operational complexity in exchange for eliminating persistent key material that could otherwise serve as an attack vector for adversaries.
Cryptographic Design and Key Management
At the cryptographic core of the system, regional root keys are implemented as 256-bit symmetric secrets. GeoKey Manager derives application-specific keys from each regional root key using Hybrid Public Key Encryption as defined in RFC 9180. The key-encapsulation mechanism combines ML-KEM-768 with X25519, while HKDF-SHA-256 handles key derivation and AES-256-GCM provides authenticated encryption. By merging post-quantum and classical cryptographic components, the architecture ensures that data confidentiality remains intact as long as at least one of the underlying cryptographic layers remains secure.
The validated design also accommodates two distinct methods of key rotation: soft rotation and hard rotation. A soft rotation creates a new epoch for a regional root key while retaining controlled access to a limited number of previous generations. This allows newly wrapped private keys to utilize the latest epoch while older wrapped keys remain temporarily valid during transition periods, preserving service uptime for customers. Conversely, a hard rotation immediately rewraps affected customer keys under a replacement epoch, instantly revoking access to the previous epoch.
Operating this global infrastructure requires continuous coordination. As physical servers enter or leave service, fleet inventory updates regional memberships multiple times each day, automatically granting or revoking access to regional root keys without requiring any manual intervention from customers.
Future Roadmap and Next Steps
The introduction of the post-quantum GeoKey Manager establishes the technical foundation for upcoming enhancements to Cloudflare’s Regional Services offering under the Cloudflare One umbrella, with further product announcements expected in the coming months. While older versions of GeoKey Manager already provide geographic controls for CDN certificates, developers are actively working on a separate integration to bring the new post-quantum architecture to those traditional CDN capabilities as well.
Current Data Localization Suite customers who are actively regionalizing their CDN traffic and wish to participate in testing the new features ahead of general availability can register their intent through Cloudflare’s outreach channels. The successful delivery of the project represents a collaborative effort spanning the Data Localization Suite, Cloudflare One, and Cloudflare Research engineering teams.