This is the highest-sovereignty variant of RKP-2 (Off-Chain). Unlike RKP-2 Enhanced EU, which uses OVH-hosted infrastructure, RKP-2 Sovereign EU runs entirely within the customer’s own on-premise EU environment. Like every RKP-2 variant, it writes nothing to any blockchain.
Sovereignty Profile
When to choose this variant: Your organisation cannot allow operational data to leave its own infrastructure perimeter - whether for national security, sector regulation, or contractual reasons - while still needing cryptographic integrity verification for audit and compliance purposes.
How It Differs Across the RKP-2 Variants
Architecture
Need On-Chain Evidence for Some Records?
RKP-2 Sovereign EU keeps every record off-chain. If records such as threshold breaches, alarms, regulatory measurements, or incidents need independently verifiable on-chain evidence, that is the hybrid model - see RKP-3 (Hybrid). Its fully on-premise variant, RKP-3 Sovereign EU, is on the roadmap.Regulatory Frameworks Addressed
Deployment Requirements
RKP-2 Sovereign EU is deployed as a containerised workload within the customer’s infrastructure:- Kubernetes on customer-controlled EU infrastructure - an existing cluster, or a single Linux host the installer sets up
- An MQTT broker within the customer network - only if you use the ROOTKey MQTT client connector to ingest data already published to that broker
- Customer-managed storage for off-chain records