Skip to main content
ABV operates in multiple regions with complete data isolation. Your data, accounts, and infrastructure are entirely separated between regions.
RegionLocationURL
US RegionAWS us-east-1 (Northern Virginia)https://app.abv.dev
EU RegionAWS eu-west-1 (Dublin, Ireland)https://eu.app.abv.dev
If you need to use multiple regions, you’ll create separate accounts and manage them independently. There’s no automatic sync or cross-region features.

​
Connecting to a Specific Region

When integrating ABV, you’ll configure your SDK or API client to connect to your chosen region.
Set the ABV region using the ABV_HOST environment variable or the host parameter:Environment Variable:
# US Region
export ABV_HOST=https://app.abv.dev

# EU Region
export ABV_HOST=https://eu.app.abv.dev
Code Configuration:
from abv import ABV

# US Region
abv = ABV(host="https://app.abv.dev")

# EU Region
abv = ABV(host="https://eu.app.abv.dev")
Learn more in the Python SDK documentation.
Set the ABV region using the ABV_BASEURL environment variable or the baseUrl parameter:Environment Variable:
# US Region
export ABV_BASEURL=https://app.abv.dev

# EU Region
export ABV_BASEURL=https://eu.app.abv.dev
Code Configuration:
import { ABV } from 'abv';

// US Region
const abv = new ABV({ baseUrl: 'https://app.abv.dev' });

// EU Region
const abv = new ABV({ baseUrl: 'https://eu.app.abv.dev' });
Learn more in the JavaScript/TypeScript SDK documentation.
When using the ABV LLM Gateway, specify the regional endpoint in your LLM provider configuration:US Region:
https://gateway.abv.dev
EU Region:
https://gateway.eu.abv.dev
All gateway traffic stays within the chosen region—requests to OpenAI, Anthropic, etc. are proxied from the regional gateway.Learn more in the LLM Gateway documentation.

​
Migration Between Regions

Regional migration requires manual steps:

Create New Regional Account

Sign up for ABV in the target region (separate account from your current region).

Configure New Environment

Set up your organization, projects, users, and settings in the new region.

Export Data

Use ABV’s data export features to export historical traces and data from the old region.

Import Data (Optional)

If needed, work with ABV support to import historical data to the new region. This is optional—many customers start fresh.

Update SDK Configuration

Update your application code to point SDKs to the new regional endpoint.

Cutover

Deploy updated code, redirecting all new traffic to the new region.

Decommission Old Region

After verifying the new region works correctly, decommission the old regional account.
Regional migration is not automatic. Plan for downtime or dual-write periods during migration. Contact support for assistance.

​
Next Steps

Get Started

Start using ABV with our quickstart guides

SDK Configuration

Configure your SDK for regional endpoints

GDPR Compliance

Learn about our GDPR compliance for EU region

HIPAA Compliance

Explore dedicated HIPAA infrastructure