Your identity data. Your soil. Your keys.
Healthcare data doesn’t get to leave the jurisdiction, and trust doesn’t get to depend on a vendor’s goodwill. OrthID runs where you run, encrypts with keys you hold, and lets you walk away whenever you choose.
Sovereignty isn’t a setting. It’s the architecture.
Open core, your infrastructure, your keys - control that survives a contract dispute, not a checkbox in someone else’s console.
Run OrthID in your own cloud or on-prem. The core is open - inspect it, audit it, trust it because you can read it.
Pin identity data to a jurisdiction. Data stays where the law - and your patients - require it to stay.
Bring your own keys via Vault, KMS or HSM. OrthID encrypts with keys it can use but never own.
A hash-chained log makes every change provable and any tampering obvious - evidence, not just records.
Re-identification keys never leave sovereign storage. The data plane enforces the boundary; nothing exfiltrates by design.
Open formats and standard protocols. Your data and your keys leave with you, intact, on your terms.
When you hold the keys, sovereignty isn’t a promise.
BYOK means OrthID can decrypt your data only while you let it. Rotate, suspend or revoke from your own Vault, KMS or HSM - and the lights go out on access without a support ticket. Re-identification keys never leave sovereign storage at all.
Prove residency, keys and integrity at a glance.
Region, key custody and audit-chain health - visible to your security team and ready for an auditor.
Identity on your soil, under your keys.
Self-hosted, region-pinned, BYOK - and an exit that’s yours to take whenever you want it.