Data residency

By default, every Monroe customer's data — Fargate task, EFS state, RDS row, KMS keys, audit log — lives in AWS us-east-1.

For customers with regulatory or contractual requirements:

EU-West (Enterprise)

Available regions:

• eu-west-1 (Ireland)
• eu-central-1 (Frankfurt)

When you provision an EU workspace, the Fargate task, EFS volume, RDS row, KMS keys, and audit log all live in your chosen region. LLM calls flow through OpenRouter, which routes to providers in the same region where possible (Anthropic EU, Bedrock EU, Vertex EU).

GDPR-friendly defaults:

• Data subject deletion request → workspace-wide purge in 30 days
• Right to portability → audit log + skills export in JSON
• DPA + SCC available on request

AP-Southeast (Enterprise)

Available regions:

• ap-southeast-1 (Singapore)
• ap-southeast-2 (Sydney)

Same pattern as EU. LLM provider availability varies by region — we'll confirm what's accessible from your chosen region before contract.

Cross-region data flow

Monroe never moves customer data out of the chosen region. The only cross-region calls are:

• Stripe payment processing (US/EU, Stripe-side)
• Clerk identity (US, Clerk-side)
• OpenRouter LLM routing (region-matched where possible; we'll document exceptions per contract)

If strict no-cross-region is required, Enterprise contracts include "no-egress" mode where every component is region-locked and LLM provider availability is limited to in-region only.

Self-hosted (special arrangement)

A small number of regulated customers (banks, defense contractors) require Monroe to run entirely on their own infrastructure. Self-hosting the runtime in your VPC is technically possible. Email enterprise@getmonroe.com to discuss.

Next: audit log.