Skip to content
Pydantic Docs

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

URLHosted
🇺🇸 US Regionlogfire-us.pydantic.devGCP us-east4 (Virginia)
🇪🇺 EU Regionlogfire-eu.pydantic.devGCP europe-west4 (Netherlands)

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

Logfire is hosted independently in each region at logfire-us.pydantic.dev and logfire-eu.pydantic.dev. When you sign up you’ll be asked to pick a region; on return visits, log in directly at your regional URL.

Region picker on the sign-in screen

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

Connecting the SDK and API

When you run logfire auth and create a project, the SDK picks up the right region automatically from your write token. You don’t need to configure a base URL.

You only need your region’s URL when talking to Logfire from outside the Python SDK:

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.

Other hosting options

If you need a specific GCP region, stricter isolation, or your own infrastructure: