Every decision stays in your jurisdiction.

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.

3Deployment regions
0Cross-region transfers
100%In-region processing
US · EU · UKResidency options
What it means

Residency for enforcement is not the same as residency for storage.

The data we handle, decisions, evaluations, and cryptographic proof, is regulatory evidence. It must be in the right jurisdiction, processed there, and auditable there.

Processing in region

The engine that evaluates your AI actions runs in your configured region. The decision is made in your jurisdiction, never transferred out and returned.

Vault anchoring in region

Every hash anchor that makes a record tamper-evident is computed and stored in your region. The proof is jurisdictionally bound.

Agent identities in region

Cryptographic agent identity records are provisioned, stored, and evaluated in your region. No cross-region identity lookups.

Auditable where it lives

Regulators review the evidence in the jurisdiction it was created, with no transatlantic transfer to explain.

Region coverage

Three regions. Full regulatory alignment in each.

Each region maps to dedicated infrastructure, dedicated compute, storage, and vault anchoring, with the frameworks that apply to that jurisdiction.

United States

Decisions, vault entries, and identities processed in US data centres. SOX, HIPAA, GLBA, and CCPA aligned. No transatlantic transfer.

European Union

EU-only compute and storage. GDPR Article 44 transfer restrictions satisfied, with EU-resident vault anchoring.

United Kingdom

UK-resident processing and storage aligned to UK GDPR, the Data Protection Act 2018, and FCA expectations.

Dedicated per region

Every region is isolated infrastructure, not a shared pool with a regional label.

Deployment & control

Choose where, and prove it.

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.

Residency tagging

Bind workspaces to a residency zone so every decision inherits the right jurisdiction automatically.

Data map

A clear map of where enforcement decisions, proof, and identities are processed and stored.

Self-hosted & on-premise

Run enforcement inside your own region or air-gapped environment with no external dependency.

Evidence you can export

Export a signed, in-region proof pack for any regulator, scoped to a period, agent, or decision.

Keep your enforcement evidence where it belongs.

Tell us your jurisdictions and we will map each class of data to the right region, with proof that stays there.