Data Regions & Availability

Langfuse Cloud is designed for high availability and offers multiple data regions to meet your needs.

Our database and application run on AWS infrastructure, partly managed by Clickhouse.

Langfuse Cloud Regions

All data, user accounts, and infrastructure are completely separated between the regions. You can have accounts in each regions.

Since all data and accounts are fully separated between regions, switching regions requires creating a new account and migrating your data. See the data migration cookbook for scripts to transfer traces, prompts, and datasets between projects.

Connecting to a Region

To connect to a specific data region using the Langfuse SDKs, you need to set the base URL environment variable or pass it during initialization:

• Python: Set LANGFUSE_BASE_URL environment variable or use the base_url parameter.
• JS/TS: Set LANGFUSE_BASEURL environment variable or use the baseUrl parameter.

Example base URLs:

• US: https://us.cloud.langfuse.com
• EU: https://cloud.langfuse.com
• HIPAA: https://hipaa.cloud.langfuse.com

Refer to the SDK documentation for detailed configuration instructions.

Choosing a Region

When selecting a data region, consider the following factors:

• Compliance and data privacy requirements: Choose the region that aligns with your organization's data residency needs (e.g., GDPR often favors the EU region).
• Latency for Prompt Management: If using Langfuse Prompt Management, select the region closer to your application servers for lower latency when fetching prompts. This is hardly noticeable as the prompts are cached by the Langfuse SDK.
• Latency for UI access: Choose the region closer to your team's location for a faster experience when using the Langfuse web interface.

Less critical factor:

• Tracing ingestion latency: Trace data is sent asynchronously in batches, making ingestion latency less of a direct concern for application performance.

Business Continuity & Availability

Cross-Region Backup

To allow recovery from the permanent loss of an AWS region, a subset of data at rest is replicated to a secondary AWS region in the same legal jurisdiction. This is a disaster-recovery control and does not provide active-active failover; on a full regional outage, Langfuse would rebuild the application stack in the secondary region and restore from the replicated backups. The expected rebuild time is up to one business day.

Postgres contains organization, project, user, API key, prompt, dataset, annotation, and score configuration data. Replicating it cross-region allows projects, credentials, and prompt management to be restored without customer intervention following a regional outage.

ClickHouse stores historical traces, observations, and scores. ClickHouse Cloud does not currently offer managed cross-region backup, and Langfuse does not maintain an out-of-region copy. On the permanent loss of the primary AWS region, historical tracing data is not recoverable from Langfuse, and a restored environment would begin ingesting fresh data. Active tracing ingestion resumes once the replacement environment is live.

S3 media buckets store uploaded media items referenced from traces. They are not replicated cross-region. On the permanent loss of the primary AWS region, uploaded media items are not recoverable, even where the referencing trace survives.

All secondary regions are within the same legal jurisdiction as their primary region (EU ↔ EU, US ↔ US, Japan ↔ Japan), so cross-region replication does not change the data-residency or cross-border-transfer posture declared in the DPA and HIPAA BAA.

Self-hosted Instances

Alternatively, you can self-host Langfuse for full control over your data and infrastructure. For installation and configuration, see: Self-hosting guide

Contact

For questions about data regions or availability, contact security@langfuse.com.

---

---