Data Regions¶
Logfire is hosted in two separate geographic regions to provide you with options for data residency, compliance with local regulations, and optimal performance.
Available Regions¶
| Hosted | URL | |
|---|---|---|
| 🇺🇸 US Region | GCP us-east4 | logfire-us.pydantic.dev |
| 🇪🇺 EU Region | GCP europe-west4 | logfire-eu.pydantic.dev |
Region Separation¶
Regions are strictly separated with no data sharing between them:
- No data is transferred between regions
- No cookies are shared between regions
- Authentication tokens are region-specific
- User accounts are separate for each region
Choosing a Region¶
When you sign up for Logfire, you'll be prompted to choose a region. After selecting your region, you'll be automatically redirected from the global domain (logfire.pydantic.dev) to your region-specific domain (either logfire-us.pydantic.dev or logfire-eu.pydantic.dev).
Consider the following factors when selecting a region:
- Geographic proximity: Choose a region closer to your location or your users for optimal performance
- Data residency requirements: Select the region that aligns with your regulatory compliance needs
- GDPR compliance: Companies requiring GDPR compliance are advised to use the EU region
Multiple Regions¶
You can have accounts in both regions if needed for different projects or teams. Each account is managed separately, with its own authentication and data.
Region Migration¶
Migration between regions is not currently available but we hope to make it possible in the future.
How does this Impact Pricing?¶
Pricing is the same between the US and EU instances.
Region URLs¶
Always ensure you're using the correct region-specific URL:
The global domain (logfire.pydantic.dev) is used primarily for the initial signup process where you'll select your region.