Skip to main content
This is a sovereignty variant of RKP-3 (Hybrid). The anchoring mechanics are identical - the difference is that all cloud processing and storage runs on OVH rather than Azure or AWS.

​
Sovereignty Profile

When to choose this variant: You need the throughput efficiency of the hybrid model - off-chain for bulk data, on-chain for critical events - and require that all data processing and storage occur on EU-incorporated infrastructure, while the on-chain anchoring layer (Polygon) is acceptable as a global public network.

​
How It Differs from RKP-3 Standard and RKP-3 Sovereign EU

​
Architecture

​
Which Records Go On-Chain vs. Off-Chain

RKP-3 Enhanced EU follows the same routing logic as RKP-3 Standard - the customer configures which event types are elevated to on-chain anchoring:

​
Regulatory Frameworks Addressed

​
Configuration

RKP-3 Enhanced EU is available as a workspace configuration option. Your API integration is unchanged - the routing logic (on-chain vs. off-chain) is configured the same way as RKP-3 Standard. Contact our team to configure your workspace for OVH-backed processing. → Request EU cloud configuration

​
When to Use RKP-3 Sovereign EU Instead

If you require that the on-chain anchoring layer itself be under EU jurisdiction - not just the cloud processing - use RKP-3 Sovereign EU (EBSI + OVH). → RKP-3 Sovereign EU