Regional Data Residency
Relai operates in two fully isolated regions: EU and US. Your prompts and completions never leave your chosen region, and are never exposed to frontier AI labs.
Available Regions
| Region | Endpoint | Infrastructure |
|---|---|---|
| EU | eu.api.llmrelai.com | AWS Frankfurt + Azure West Europe |
| US | us.api.llmrelai.com | AWS Virginia + Azure East US |
Private Cloud Infrastructure
All inference runs on Amazon Bedrock and Azure OpenAI — enterprise private cloud deployments where frontier AI labs cannot access your data:
- Zero training on your data — Anthropic, OpenAI, and other frontier labs never see your prompts or use them for training
- No logging by model providers — Your conversations are not stored or analyzed by AI companies
- Contractual guarantees — DPAs with AWS and Microsoft, not with frontier labs who may change policies
- Enterprise compliance — SOC2, HIPAA, and ISO 27001 certifications from cloud providers
How It Works
When you make an API request to an EU endpoint:
- Your request arrives at our EU gateway (Frankfurt)
- We route to EU-hosted Bedrock or Azure OpenAI deployments
- The response returns directly to you
- No data crosses to the US region or to AI lab servers
┌─────────────┐ ┌─────────────┐ ┌─────────────────────┐
│ Your App │────▶│ EU Gateway │────▶│ Bedrock / Azure EU │
│ (EU) │◀────│ (Frankfurt)│◀────│ (Private Cloud) │
└─────────────┘ └─────────────┘ └─────────────────────┘
❌ Never touches Anthropic/OpenAI serversAPI Key Regions
Each API key is bound to a region when created:
rk-eu-...— EU region keyrk-us-...— US region key
Using a key on the wrong region's endpoint returns an error:
{
"error": {
"message": "API key is for region EU, but request was made to US",
"type": "region_mismatch",
"code": 403
}
}GDPR Compliance
For EU customers processing personal data:
- Data Processing Agreement (DPA): Available on request, covering AWS and Azure sub-processors
- Sub-processors: Only AWS and Microsoft — no frontier AI labs in the data processing chain
- Data Retention: Prompts and completions are never stored (zero-retention policy)
- Article 28 compliance: Full controller-processor documentation available
Multi-Region Setup
For global applications, create separate API keys per region:
const euClient = new OpenAI({
apiKey: process.env.RELAI_EU_KEY,
baseURL: "https://eu.api.llmrelai.com/v1",
});
const usClient = new OpenAI({
apiKey: process.env.RELAI_US_KEY,
baseURL: "https://us.api.llmrelai.com/v1",
});
// Route based on user location
const client = userRegion === "EU" ? euClient : usClient;Dashboard Region
Your dashboard account is region-specific:
- EU users:
app.llmrelai.com(default) - US users:
us.app.llmrelai.com(coming soon)
Each region has isolated:
- User accounts
- Organizations
- API keys
- Billing
- Usage data