Data residency (Enterprise)

Enterprise contracts unlock data-residency controls beyond the default Argentina-primary footprint:

Region pinning

Choose a single region to host all customer data:

• AR (San Juan) — solar-native, lowest cost.
• EU (Frankfurt) — GDPR-native.
• US (Virginia) — for latency to North American users.

Pinning disables cross-region DR; we recommend coupling with an explicit DR plan (snapshots-only or warm standby in the same region).

Dedicated cluster

For regulated workloads, we deploy a single-tenant cluster:

• Isolated Postgres for identity + inference logs
• Isolated LiteLLM gateway with the customer’s choice of providers
• Customer’s own KMS root keys (BYOK)
• Customer-supplied VPN or PrivateLink for ingress

Operated by Xcity, billed at a different rate than shared infra. Talk to us via enterprise@xcity.one.

Customer-hosted

For air-gapped or fully-sovereign environments, the Xcity gateway can be deployed inside the customer’s cloud (AWS / Azure / GCP). The customer pays for compute; Xcity provides the software, updates, and support. Identity and billing still flow through xcity.one unless the customer opts for fully-offline mode.

Reach out

Email enterprise@xcity.one. Typical evaluation cycle is 4–8 weeks; we’ll walk you through a deployment plan, run a proof-of-concept against your data, and produce a custom DPA.

Last updated: May 15, 2026