Skip to main content

​
Overview

Data sovereignty means that data is subject to the laws of the country in which it is processed and stored - and that no foreign government, court, or authority can compel access without the knowledge and consent of the data owner under EU law. For organisations subject to NIS2, GDPR, national critical infrastructure regulations, or sector-specific requirements (healthcare, defence, financial services), this is not a preference - it is a requirement. ROOTKey supports sovereignty at three levels - the standard EU-region cloud, a dedicated deployment on EU-incorporated cloud, and a fully on-premise installation where no component leaves your infrastructure.

​
Infrastructure Stack

The choice of infrastructure determines the sovereignty level of the deployment:

​
Sovereignty Levels

Standard

Azure or AWS (EU regions) + PolygonData remains in EU geographically but is subject to US jurisdiction via the CLOUD Act. Suitable for most commercial deployments where EU data residency (not strict sovereignty) is the requirement.

Enhanced EU

Dedicated OVH deployment + PolygonCloud infrastructure is EU-incorporated (OVH, no US parent). Blockchain anchoring, where the protocol uses it, stays on Polygon (global network). Available on request.

Sovereign EU

On-premiseEvery component runs inside your own infrastructure. The off-chain protocol (RKP-2) is in development; on-chain variants with a private chain deployed in your perimeter are on the roadmap.

​
Protocol Sovereignty Matrix

For RKP-2 there is no blockchain, so sovereignty is determined entirely by where the platform runs. For RKP-1 and RKP-3, the public Polygon network is outside any single jurisdiction - full EU sovereignty on those protocols requires a private chain inside your perimeter, which is on the roadmap.

​
What Changes With Each Level

​
Enhanced EU: OVH instead of Azure / AWS

OVH is a French cloud provider with no US parent company. A dedicated ROOTKey deployment on OVH Managed Kubernetes means that off-chain data storage, API processing, and platform operations are outside the jurisdiction of US law enforcement and the CLOUD Act. ROOTKey does not run on OVH by default - the deployment is provisioned on request.

​
Sovereign EU: your own infrastructure

The on-premise installation places the complete ROOTKey Data Plane inside your perimeter. In egress-only mode the only outbound link is to the ROOTKey Control Plane, for licensing and telemetry - never files, users, or metadata. In air-gapped mode there is no link at all.

​
Regulatory Frameworks That Require or Benefit From Sovereignty

​
Requesting an EU Deployment

Both the dedicated OVH deployment and the on-premise installation are available on request for organisations with demonstrated sovereignty requirements. Scoping involves:
  1. Choosing the level - dedicated OVH deployment or on-premise
  2. Sizing and network design (for on-premise: egress-only or air-gapped)
  3. API endpoints scoped to the dedicated deployment
  4. SLA and data processing agreements under EU law
Contact our team to discuss your requirements and initiate a sovereignty assessment.

Request a data sovereignty consultation

We’ll assess your regulatory environment and design a ROOTKey deployment configuration that meets your sovereignty requirements.

View compliance coverage

Full mapping of ROOTKey capabilities to EU regulatory frameworks that drive sovereignty requirements.