EU data residency
Langbly offers a global endpoint and a dedicated EU data residency endpoint. eu.langbly.com routes translation processing through Google Cloud regions in EU member states. The temporary Redis cache and account database are also in the EU.
Endpoints​
| Global (recommended) | EU data residency | |
|---|---|---|
| Base URL | https://api.langbly.com | https://eu.langbly.com |
| API edge | Global Cloudflare network | Global Cloudflare network |
| Translation processing | Global service route | Google Cloud EU region pool |
| Primary configured region | us-central1 | europe-west4 |
| Temporary Redis cache | Frankfurt (eu-central-1), up to 1 hour | Frankfurt (eu-central-1), up to 1 hour |
| Best for | Lowest latency worldwide | EU data residency and GDPR-sensitive workloads |
| API format | Google Translate v2 | Google Translate v2 |
Both endpoints are identical in functionality and pricing.
Which endpoint should I use?​
Use api.langbly.com (global) for most use cases and worldwide access.
Use eu.langbly.com (EU data residency) when translation processing and temporary storage must stay in the European Union. Translation requests use a pool of Google Cloud regions in EU member states. europe-west4 in the Netherlands is the configured default, not the only EU region. The temporary Redis cache is in Frankfurt.
GDPR​
Both endpoints use the same authentication, billing and limited-retention policy. Source text is not written to application databases or logs. Eligible translated responses may be cached for up to one hour; idempotent responses and document results may be retained for up to 24 hours.
The key difference is the processing geography. The global endpoint is designed for worldwide access. The EU endpoint keeps translation processing and temporary storage in the EU.
This applies regardless of where your users are located. GDPR protects data of EU residents, so US-based companies translating EU customer data should consider the EU endpoint as well.
How to use​
Replace the base URL in your API calls:
# Global (default — lowest latency)
curl -sS 'https://api.langbly.com/language/translate/v2' \
-H 'Content-Type: application/json' \
-H 'X-API-Key: YOUR_API_KEY' \
-d '{"q": "Hello", "target": "de"}'
# EU data residency endpoint
curl -sS 'https://eu.langbly.com/language/translate/v2' \
-H 'Content-Type: application/json' \
-H 'X-API-Key: YOUR_API_KEY' \
-d '{"q": "Hello", "target": "de"}'
Your API key works on both endpoints. No configuration changes needed.
EU data residency infrastructure​
- Request ingress — Cloudflare's global edge network
- Translation model processing — Google Cloud EU region pool
- Database — EU region
- Temporary Redis cache — Frankfurt, Germany (
eu-central-1), with a one-hour TTL for eligible translated responses - Idempotent responses and document results — up to 24 hours
The EU endpoint is the correct choice for EU data residency. Data in transit is encrypted with TLS.
SDK configuration​
Python​
from langbly import LangblyClient
client = LangblyClient(
api_key="YOUR_API_KEY",
base_url="https://eu.langbly.com"
)
Node.js​
import { LangblyClient } from 'langbly';
const client = new LangblyClient({
apiKey: 'YOUR_API_KEY',
baseUrl: 'https://eu.langbly.com',
});
Compliance​
If you have specific compliance questions or need a Data Processing Agreement (DPA), contact support@langbly.com.