500K characters included every month. Add payment details to start.
EU Data Residency

Keep your translation data in Europe

Translation processing uses Google Cloud regions in EU member states, and temporary Redis caching stays in Frankfurt. Same API, same quality, same pricing.

Two endpoints, one API

Both endpoints are fully Google Translate v2 compatible, run in the EU, and share the same pricing. Choose the one that fits your compliance requirements.

Global Endpoint

api.langbly.com
Global service route

Designed for worldwide access and low latency. Use the EU endpoint when EU data residency is required.

  • GDPR-compliant
  • Lowest latency globally
  • Google Translate v2 compatible
  • Best for most use cases
EU Data Residency

EU Data Residency Endpoint

eu.langbly.com
Google Cloud EU region pool

Translation processing uses regions in EU member states. The configured default is europe-west4 in the Netherlands, and temporary Redis caching is in Frankfurt.

  • GDPR-compliant
  • All processing in the EU
  • Google Translate v2 compatible
  • Best for regulated industries

What is EU-based today

When you use the EU endpoint, every component of the translation pipeline runs within the European Union. No data leaves EU borders at any stage of the process.

Our infrastructure runs on certified platforms that meet ISO 27001 and SOC 2 standards, with all data encrypted in transit using TLS.

Translation processing
Google Cloud EU region pool
Database
EU region
Cache
Frankfurt (eu-central-1), up to 1 hour
Encryption in transit
TLS 1.2+
Infrastructure certification
ISO 27001, SOC 2

Built for GDPR compliance

Both endpoints use the same privacy and retention controls. The dedicated endpoint provides EU data residency for translation processing and temporary storage.

No content storage

We don't persist translation content in our database. Results may be cached briefly to speed up repeated requests, then discarded.

Encrypted in transit

All API traffic is encrypted with TLS. Your translation data is never transmitted in plain text between any component.

DPA available

We offer a Data Processing Agreement for enterprise customers. Contact us to set up a DPA for your organization.

Cross-border transfers

US companies translating EU customer data should consider the EU endpoint to simplify cross-border data transfer compliance.

Switch endpoints in one line

Both endpoints share the same Google Translate v2 compatible API. Switching to the EU endpoint is as simple as changing the base URL.

cURL
# Global endpoint
curl "https://api.langbly.com/v2?key=YOUR_KEY&q=Hello&target=de&source=en"
# EU data residency endpoint
curl "https://eu.langbly.com/v2?key=YOUR_KEY&q=Hello&target=de&source=en"
Python
from langbly import LangblyClient
# Use the EU endpoint
client = LangblyClient(
api_key="YOUR_KEY",
base_url="https://eu.langbly.com"
)
result = client.translate(
q="Hello world",
target="de"
)
Node.js
import { LangblyClient } from "langbly";
// Use the EU endpoint
const client = new LangblyClient({
apiKey: "YOUR_KEY",
baseUrl: "https://eu.langbly.com"
})
const result = await client.translate({)
q: "Hello world",
target: "de"
})
Regulated industries
Healthcare, finance, legal, government
US companies with EU users
Simplify cross-border compliance
Enterprise procurement
Meet internal data residency policies
Public sector
National data sovereignty requirements

Who should use the EU endpoint?

The global endpoint is GDPR-compliant and works great for most use cases. The EU endpoint is designed for organizations that prefer an EU Vertex AI region as the first processing location.

If your security team, legal department, or procurement process requires EU data residency, use the dedicated EU endpoint.

Get started with EU data residency

The same API key works on both endpoints. Choose the dedicated EU endpoint when your workload needs EU data residency.