EU data residency

Langbly offers two endpoints, both hosted in the EU. The dedicated EU endpoint guarantees that all data processing and storage — including translation processing — stays within the European Union.

Endpoints

	Global (recommended)	EU-only
Base URL	`https://api.langbly.com`	`https://eu.langbly.com`
Server location	Netherlands	Finland
Translation processing	May route outside EU	EU-only infrastructure
Best for	Lowest latency worldwide	Strict EU data residency
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. It runs in the Netherlands and provides the lowest latency for users worldwide. Both the API server and database are in the EU.

Use eu.langbly.com (EU-only) when you need guaranteed EU data residency for all processing and storage. This endpoint runs in Finland using EU-only infrastructure. All computation, storage, and translation processing stays within the EU. Note that this endpoint may have slightly higher latency for users outside Northern Europe.

Both endpoints are GDPR-compliant. Langbly does not store translation content beyond short-lived caching, and our infrastructure (database, cache) is hosted in the EU.

The key difference: the global endpoint may process translation requests outside the EU. If your data protection policy or DPA requires that no data leaves the EU — even temporarily during processing — use the EU endpoint.

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-only (strict data residency)
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.

What stays in the EU (eu.langbly.com)

API server — Finland
Translation processing — EU-based infrastructure
Database — EU region
Cache — EU region

All data processing and storage happens within the EU. Data in transit is encrypted via TLS and routed over certified network infrastructure (ISO 27001, SOC 2).

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.

Endpoints​

Which endpoint should I use?​

GDPR​

How to use​

What stays in the EU (eu.langbly.com)​

SDK configuration​

Python​

Node.js​

Compliance​