RKP-3 Sovereign EU - Hybrid, 100% EU (Roadmap) - ROOTKey

Roadmap - not available yet. RKP-3 Sovereign EU depends on deploying a private blockchain inside the customer’s infrastructure, which the on-premise installer does not do today. RKP-3 itself, including RKP-3 Enhanced EU, is in development, as is RKP-2 Sovereign EU (on-premise, no blockchain).

This is the planned highest-sovereignty variant of RKP-3 (Hybrid). The routing stays the same - bulk data off-chain, critical events on-chain - but on-chain records land on a private chain operated inside the customer’s perimeter instead of the public Polygon network.

Planned Sovereignty Profile

Component	Provider	Jurisdiction	Notes
Blockchain (on-chain path)	Private chain, customer-operated	Customer EU facility	Deployed alongside the platform by the on-premise installer
API processing	Customer on-premise	Customer EU facility	ROOTKey on-premise installation
Off-chain storage	Customer on-premise	Customer EU facility	Data never leaves the organisation’s infrastructure
Sovereignty level	Full EU	100% customer infrastructure	No component outside the customer’s control

The Complete Sovereignty Matrix - All Protocol Variants

Protocol	Blockchain	Infrastructure	Sovereignty	Availability
RKP-1 Standard	Polygon	ROOTKey cloud (Azure / AWS)	None	Standard
RKP-1 Enhanced EU	Polygon	Dedicated OVH deployment	Partial (EU cloud)	On request
RKP-1 Sovereign EU	Private chain	On-premise	Full EU	Roadmap
RKP-2 Standard	-	ROOTKey cloud (Azure / AWS)	None	In development
RKP-2 Enhanced EU	-	Dedicated OVH deployment	Full EU (cloud)	In development
RKP-2 Sovereign EU	-	On-premise	Full EU - air-gap	In development
RKP-3 Standard	Polygon	ROOTKey cloud (Azure / AWS)	None	In development
RKP-3 Enhanced EU	Polygon	Dedicated OVH deployment	Partial (EU cloud)	In development
RKP-3 Sovereign EU	Private chain	On-premise	Full EU	Roadmap

A private chain moves the trust boundary: verification is no longer possible from a public block explorer by any third party, only by parties given access to the chain. This is the trade-off for keeping every component under the customer’s jurisdiction.

Interested?

If your organisation needs hybrid anchoring with no component outside your perimeter, tell us about your requirements - they shape the roadmap. → Discuss RKP-3 Sovereign EU