Overview#
EU Data Sovereignty Options let an organisation run the platform's supporting services on European providers and keep its users' sign-in inside the EU, so that sensitive operational data does not depend on a single non-European cloud. Each option is a deployment setting chosen by the customer and the operator, and the existing providers remain available for organisations that prefer them.
The options cover the parts of a deployment where data usually leaves an organisation's control: AI language models, outbound email, object storage for files and evidence, and the sign-in service that issues passkeys and sessions. For each one the platform supports a European choice that can be selected through configuration rather than code changes.
For buyers, this answers the sovereignty and transfer questions raised in public sector procurement, GDPR transfer assessments and national security reviews. For operators, it means a move to a European provider is a configuration change with a clear fallback, and the EU sign-in service enforces its own trust boundary so EU sessions are never issued by another region's host.
Last Reviewed: 2026-10-28 Last Updated: 2026-10-28
Key Features#
- EU-Hosted AI Model Option: A European language model provider is available in the model catalogue alongside the existing providers. It supports streaming responses, an allowlist of approved models, per-tenant token tracking and failover, and the smart router can select it for complex tasks. Organisations can prefer it for workloads that must stay with an EU provider.
- EU Email Transport: Platform and sign-in emails can be sent through an EU mail service over SMTP with STARTTLS. The previous transport stays available as a customer option. The sender address matches the authenticated mail account, HTML messages include a plain-text version, and recipient addresses are masked in logs. Sending email remains switched off until an operator enables it.
- Portable Object Storage: File and evidence storage works with any S3-compatible object store. The storage region and addressing style are settings, so a sovereign store that needs path-style addressing works through configuration alone, consistent with how database backups are already stored.
- Single EU Passkey Relying Party: Passkeys for the EU service are registered once against one EU relying party and work across the related EU sign-in origins, including the Android platform sign-in flow.
- EU Ingress Trust Boundary: The EU sign-in service listens on dedicated EU entry points and grants EU trust only to connections that genuinely arrived there from a trusted proxy. Requests for the EU host on any other entry point are refused, the EU entry points never serve another region's traffic, and a misconfigured boundary stops the service at start-up instead of running in a weakened state.
- Configuration with Fallback: Each option is selected per deployment. Where an EU provider is not configured the platform keeps using the existing provider, so a migration can be staged service by service.
Use Cases#
Public Sector Procurement in the EU#
A national agency requires that AI processing, email and stored evidence stay with European providers. The deployment selects the EU model provider, the EU mail transport and an EU object store, and the agency's transfer impact assessment can rely on documented configuration.
Staged Migration Off a Single Cloud#
An operator moves file storage to a European S3-compatible provider first, verifies it, and then moves email, without code changes and with the previous providers still available.
Region-Bound Sign-In#
Users of the EU service register a passkey once and sign in only through EU entry points, so their sessions and keys are issued and checked within the EU boundary.
Audiences#
- Public sector and critical infrastructure buyers with sovereignty requirements.
- Data protection officers preparing GDPR transfer and impact assessments.
- Platform operators planning provider changes.
Integration#
The options plug into the platform's AI orchestration and model routing, the notification and email services, evidence and file storage, and the passwordless sign-in service. They work alongside the platform's existing security controls and key management.
Open Standards#
- SMTP with STARTTLS (RFC 3207): email is delivered over an encrypted SMTP session.
- Amazon S3-compatible API: object storage uses the widely supported S3 interface, so any compatible provider can be used.
- W3C WebAuthn Level 3 and related origins: passkeys are bound to one EU relying party and shared across declared related origins.
- GDPR (Regulation (EU) 2016/679): the options support data residency and transfer obligations.