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 - with optional EBSI anchoring for audit-grade proofs.
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
Selective EBSI Anchoring
RKP-2 Sovereign EU processes high-frequency data entirely on-premise. For records that require the highest level of audit defensibility - regulatory measurements, safety events, incident records, threshold breaches - the on-premise ROOTKey deployment can selectively elevate those records to EBSI:
This pattern preserves throughput and cost efficiency for bulk telemetry while ensuring that the records most likely to face regulatory scrutiny have the highest possible evidentiary standing.
Regulatory Frameworks Addressed
Deployment Requirements
RKP-2 Sovereign EU is deployed as a containerised workload within the customer’s infrastructure:- Docker or Kubernetes environment on customer-controlled EU infrastructure
- MQTT broker accessible within the customer network
- Optional outbound HTTPS connection to EBSI for selective anchoring (no inbound required)
- Customer-managed storage for off-chain records