Enforcement decisions, trust context, agent identities, and vault entries are all processed and stored in the region you configure. Jurisdictional boundaries are enforced at the infrastructure level, not by policy.
The data we handle, decisions, evaluations, and cryptographic proof, is regulatory evidence. It must be in the right jurisdiction, processed there, and auditable there.
The engine that evaluates your AI actions runs in your configured region. The decision is made in your jurisdiction, never transferred out and returned.
Every hash anchor that makes a record tamper-evident is computed and stored in your region. The proof is jurisdictionally bound.
Cryptographic agent identity records are provisioned, stored, and evaluated in your region. No cross-region identity lookups.
Regulators review the evidence in the jurisdiction it was created, with no transatlantic transfer to explain.
Each region maps to dedicated infrastructure, dedicated compute, storage, and vault anchoring, with the frameworks that apply to that jurisdiction.
Decisions, vault entries, and identities processed in US data centres. SOX, HIPAA, GLBA, and CCPA aligned. No transatlantic transfer.
EU-only compute and storage. GDPR Article 44 transfer restrictions satisfied, with EU-resident vault anchoring.
UK-resident processing and storage aligned to UK GDPR, the Data Protection Act 2018, and FCA expectations.
Every region is isolated infrastructure, not a shared pool with a regional label.
Tag data to a residency zone, see exactly where each class of data lives, and run the whole layer inside your own environment when you must.
Bind workspaces to a residency zone so every decision inherits the right jurisdiction automatically.
A clear map of where enforcement decisions, proof, and identities are processed and stored.
Run enforcement inside your own region or air-gapped environment with no external dependency.
Export a signed, in-region proof pack for any regulator, scoped to a period, agent, or decision.
Tell us your jurisdictions and we will map each class of data to the right region, with proof that stays there.