Teams building voice agents for European customers often meet the same question shortly before launch: the ElevenLabs integration works, but the customer's data protection officer asks where text and audio go. A search for "ElevenLabs EU endpoint" leads to a host name, api.eu.residency.elevenlabs.io, and to a page that says the feature is for Enterprise customers. What that host covers, and what it does not, decides whether it solves your problem.
This Article explains ElevenLabs' EU data residency as its documentation and Data Processing Agreement describe it on 12 November 2026, shows how to configure it, and compares it with the default API, an EU-hosted compatible endpoint and self-hosting. The step-by-step move to a compatible endpoint is in our guide on migrating from the ElevenLabs API.
The author works at KugelAudio, which offers one of the options compared here. KugelAudio facts are first-party disclosures; ElevenLabs facts come from ElevenLabs' own documentation, pricing page and DPA. No option is declared the winner.
Key takeaways
- The ElevenLabs EU endpoint is
https://api.eu.residency.elevenlabs.io(WebSockets onwss://at the same host). It belongs to an isolated environment that only Enterprise customers can get, with a separate, initially blank workspace and a different API key. - EU residency at ElevenLabs is a storage guarantee first. Processing may still happen outside the EU (affiliates, subprocessors, support, content moderation) unless you use the API with Zero Retention Mode, also an Enterprise feature, and avoid integrations that need out-of-region processing. Without residency, ElevenLabs hosts customer data in the U.S. by default.
- If you want to keep ElevenLabs SDK code but need EU hosting without an enterprise contract, an EU-hosted ElevenLabs-compatible endpoint is a base-URL swap. KugelAudio offers one at
/11labson its EU host; voice IDs and some endpoints differ. - Whatever you choose, verify it: pin the host, block the default host at the egress, and check every other hop in your voice pipeline.
Last checked 12 November 2026.
What is the ElevenLabs EU endpoint?
The ElevenLabs EU endpoint is the API address of an isolated ElevenLabs environment in the EU: https://api.eu.residency.elevenlabs.io for REST, wss://api.eu.residency.elevenlabs.io for WebSockets, and https://eu.residency.elevenlabs.io for the web app. ElevenLabs lists equivalent isolated environments for India and Singapore.
The word "isolated" matters. ElevenLabs describes these environments as completely separate workspaces. Your account there is separate from the one on elevenlabs.io and starts blank, so API calls need both the different URL and a different API key, and your existing voices and agents are not there.
Access is not self-serve. The documentation calls data residency an exclusive feature for Enterprise customers: existing Enterprise customers ask their success team to enable an isolated environment, new customers go through sales. The public API pricing page does not mention data residency at all; its Enterprise column mentions custom terms around DPAs and SLAs.
What does ElevenLabs EU data residency cover, and what not?
It covers where your data is stored, not by default where it is processed. In ElevenLabs' words, "while storage will take place in the selected location, processing may nevertheless occur outside of the selected location, including by ElevenLabs' international affiliates and subprocessors, for support purposes, and for content moderation purposes."
The Data Processing Agreement (last updated 8 April 2026) says the same in contractual language. Section 13.1 makes the residency option subject to ElevenLabs' discretion and states that customer personal data "may nevertheless be processed outside of such Data Residency location", including by subprocessors located elsewhere and by support or moderation staff accessing data from outside the residency location. The DPA also authorizes international data transfers and incorporates the EU Standard Contractual Clauses for them.
For the EU there is one documented way to restrict processing as well: "users may restrict processing to the EU by using Zero Retention Mode and the API." In that case content submitted to the service is not processed outside the EU, with an exception for optional integrations such as custom LLMs or post-call webhooks that require out-of-region processing.
Zero Retention Mode has its own conditions. It is an Enterprise feature, available to "select enterprise customers", and ElevenLabs can restrict it if it judges a use case high risk. It is not switched on by an isolated environment: you enable it per request with the query parameter enable_logging=false on covered endpoints, which include every /v1/text-to-speech/ endpoint and the TTS WebSocket. Traffic through the web UI is never covered. ElevenLabs suggests checking that it works by opening the Text to Speech history, which should contain no requests with saved audio.
The isolated environment also has functional gaps. On the fetch date, Image and Video, Flows and the Studio Agent were not available there, Speech to Text transcript editing returned an error, and available LLMs differ by region. Migration support is limited: professional voice clones can be moved by link sharing, instant voice clones need a request to ElevenLabs, and agents are best recreated through the API.
How do you configure the ElevenLabs EU endpoint?
Once ElevenLabs has enabled the environment, you sign in at eu.residency.elevenlabs.io, create an API key there and point your client at the EU environment. The official SDKs take an environment setting instead of a raw URL. In Python:
from elevenlabs import ElevenLabs, ElevenLabsEnvironment
client = ElevenLabs(
api_key="your-eu-workspace-key", # created in the isolated EU workspace
environment=ElevenLabsEnvironment.PRODUCTION_EU,
)
The TypeScript SDK uses ElevenLabsEnvironment.ProductionEu, the browser client for agents takes origin: "https://api.eu.residency.elevenlabs.io" (plus a livekitUrl on the EU host for WebRTC), and the React SDK takes serverLocation: "eu-residency". Frameworks that wrap ElevenLabs may expose a base URL instead. In a LiveKit community thread from March 2026, a developer passed https://api.eu.residency.elevenlabs.io/v1 as the ElevenLabs plugin's base_url for an EU deployment, and a reply in the thread confirmed that base_url is appropriate when you have your own endpoint.
If you need processing restricted to the EU, add enable_logging=False to each covered call, for example client.text_to_speech.convert(..., enable_logging=False). If requests fail after the switch, ElevenLabs' FAQ points to two causes: the wrong URL or a key from the other workspace.
What are the alternatives to ElevenLabs EU residency?
There are four realistic setups, and they differ in who has to sign what before you can send the first request. The table describes each provider's documented behaviour, not a legal assessment.
Two points are easy to miss. First, an EU host is a routing and hosting control, not a compliance outcome: retention, subprocessors, support access and your own records of processing still need review, whichever row you pick. Second, the speech API is one hop of several. If your speech recognition, LLM or telephony provider processes in the U.S., moving text-to-speech to the EU does not make the call EU-only.
How does an EU-hosted ElevenLabs-compatible endpoint work?
A compatible endpoint implements a subset of the ElevenLabs HTTP and WebSocket API under its own base URL, so the official ElevenLabs SDKs and tools that accept a base URL keep working. KugelAudio documents the following routes under /11labs: POST /v1/text-to-speech/{voice_id}, POST /v1/text-to-speech/{voice_id}/stream, the stream-input WebSocket for LLM token streams, GET /v1/voices and GET /v1/models.
KugelAudio's integration page shows the base URL https://api.kugelaudio.com/11labs, which is the canonical geo-routed endpoint. To pin traffic to Europe, the Regions page names the direct EU host api.eu.kugelaudio.com, says EU selection applies to REST and WebSocket endpoints, and says the ElevenLabs model mapping is the same on both hosted regions. With the ElevenLabs Python SDK the swap looks like this:
from elevenlabs import ElevenLabs
client = ElevenLabs(
api_key="your-kugelaudio-api-key", # no "eu-" prefix here
base_url="https://api.eu.kugelaudio.com/11labs",
)
audio = client.text_to_speech.convert(
voice_id="480", # KugelAudio voice ID; list them with client.voices.get_all()
text="Hello from the EU endpoint.",
model_id="kugel-3.5",
output_format="pcm_24000",
)
The same works without an SDK. The header stays xi-api-key, as in ElevenLabs' API:
curl -X POST https://api.eu.kugelaudio.com/11labs/v1/text-to-speech/480 \
-H "xi-api-key: $KUGELAUDIO_API_KEY" \
-H "Content-Type: application/json" \
-d '{"text": "Hello from the EU endpoint.", "model_id": "kugel-3.5"}' \
--output test.pcm
Three details from KugelAudio's documentation prevent the usual first-day errors. The eu- key prefix that selects the EU region in KugelAudio's own SDKs is an SDK feature: inside the ElevenLabs SDK or a raw request it is sent as part of the key and fails with 401, so set the EU host in the URL instead. ElevenLabs voice IDs do not exist on KugelAudio, and ElevenLabs model aliases such as eleven_turbo_v2 or eleven_multilingual_v2 map to kugel-3.5 on the hosted regions. And the compatible endpoint returns 24 kHz PCM unless you request MP3, so code that expects MP3 by default should set output_format explicitly.
Unlike an ElevenLabs isolated environment, the same KugelAudio API key works on the default and the EU host, so there is no second workspace. What the compatible subset does not cover (voice creation, history, user and subscription endpoints, and parameters such as stability or style) is listed in the migration guide, together with voice mapping and a cutover plan. If your agent runs on LiveKit, Pipecat, Vapi or Cognigy, KugelAudio's documentation recommends its official integration over the compatibility layer.
How do you verify that voice traffic actually stays in the EU?
Configuration is a claim; these checks turn it into evidence. Run them in staging with production settings, and again after SDK upgrades, since a new version can change how WebSocket URLs are built.
- Inventory every host your code calls. Search configuration and source for the default hosts (
api.elevenlabs.io,api.kugelaudio.com) and for WebSocket URLs, which some clients build separately from the REST base URL. Include browser widgets, agent frameworks and background jobs. - Block the default host at the egress. Allow only the EU host (
api.eu.residency.elevenlabs.ioorapi.eu.kugelaudio.com) in your firewall or proxy and run your integration tests. Anything that breaks was still using the default route. - Remove keys you no longer need. With ElevenLabs residency, the key from the elevenlabs.io workspace has no business in production; deleting it from your secrets makes a fallback to the default workspace fail loudly instead of silently.
- Check retention, not only location. At ElevenLabs, confirm
enable_logging=falseis set on every covered request and that the Text to Speech history shows no saved audio. At any provider, read what the DPA says about logs, support access and deletion. - Read the subprocessor list. ElevenLabs maintains its list at compliance.elevenlabs.io; KugelAudio publishes an EU-only subprocessor register. Check where each one processes, not where it is headquartered.
- Trace the other hops. Speech recognition, the LLM, webhooks, call recording, telephony and observability tools each see call content. ElevenLabs itself notes that custom LLMs and post-call webhooks can take processing out of region.
- Write down the result. Note the hosts, the date, the SDK versions and the test that passed, so the next audit does not start from zero.
What should you choose?
Choose the ElevenLabs EU environment if your product depends on ElevenLabs-specific features, voices or agents and you can sign an Enterprise agreement; plan for a fresh workspace, rebuilt voices and Zero Retention Mode if processing has to stay in the EU. Choose an EU-hosted compatible endpoint if you mainly need text-to-speech from code that already speaks the ElevenLabs API and want EU hosting from the first request, accepting that voices change and some endpoints are missing. Choose self-hosting if data must stay in your own data centre; our guides on on-premise voice AI infrastructure and self-hosted open-source TTS models cover what that takes.
For a broader view of providers, see ElevenLabs alternatives in Europe, and for German-speaking markets the DACH data residency and language guide. KugelAudio's plans, all of which include the EU Sovereign Cloud for EU and EEA customers without an enterprise contract, are on the pricing page (traffic is pinned to Europe with the EU endpoint api.eu.kugelaudio.com); on-premise is described on the on-premise page.
FAQ
Is there an ElevenLabs EU endpoint for non-Enterprise plans?
Not according to ElevenLabs' documentation on 12 November 2026. Data residency is described as an exclusive feature for Enterprise customers, and the public API pricing page does not mention it.
Does the ElevenLabs EU endpoint keep all processing in the EU?
Not by default. ElevenLabs guarantees storage in the EU environment, but says processing may occur elsewhere, including by subprocessors, support and moderation. Processing is restricted to the EU only with the API and Zero Retention Mode, and optional integrations such as custom LLMs or post-call webhooks can still require out-of-region processing.
Can I use my existing ElevenLabs API key with api.eu.residency.elevenlabs.io?
No. The isolated environment is a separate account with a blank workspace, so you create a new key there. A key from elevenlabs.io is the most common reason ElevenLabs gives for failing requests against the EU host.
Do my ElevenLabs voices move to the EU environment?
Not automatically. Professional voice clones can be added via link sharing, instant voice clones need a request to ElevenLabs, and agents should be recreated through the API. On an ElevenLabs-compatible endpoint from another provider, ElevenLabs voice IDs do not exist at all; you pick or clone voices there.
Is an EU endpoint enough for GDPR?
No endpoint makes a deployment GDPR compliant on its own. It controls routing and hosting. You still need a DPA, a review of subprocessors and retention, a lawful basis and, for a voice agent, the same check for every other provider in the call path.
Does the KugelAudio ElevenLabs-compatible API need an enterprise contract for EU hosting?
No. KugelAudio states that the EU Sovereign Cloud is included on every plan for customers in the EU and EEA, without an enterprise contract. To pin traffic to Europe, use the EU endpoint api.eu.kugelaudio.com; the same API key works there. On-premise deployment is the part that requires an Enterprise agreement.
Does an ElevenLabs-compatible endpoint support WebSocket streaming?
KugelAudio's compatible API supports the stream-input WebSocket for text streamed token by token from an LLM. Its documentation advises against flushing after every chunk, because each flush ends a turn; let the server start synthesis at sentence boundaries instead.
Sources
All sources accessed 12 November 2026.
- ElevenLabs, Data residency: https://elevenlabs.io/docs/overview/administration/data-residency
- ElevenLabs, Zero Retention Mode (Enterprise): https://elevenlabs.io/docs/resources/zero-retention-mode
- ElevenLabs, Data Processing Agreement (last updated 8 April 2026): https://elevenlabs.io/dpa
- ElevenLabs, API pricing: https://elevenlabs.io/pricing/api
- LiveKit community, "EU data residency with Deepgram, OpenAI & ElevenLabs": https://community.livekit.io/t/eu-data-residency-with-deepgram-openai-elevenlabs-how-to-configure-regional-endpoints/465
- KugelAudio documentation, ElevenLabs API compatibility: https://docs.kugelaudio.com/integrations/elevenlabs-proxy
- KugelAudio documentation, Regions: https://docs.kugelaudio.com/guides/regions
- KugelAudio documentation index: https://docs.kugelaudio.com/llms.txt
- KugelAudio, pricing (EU Sovereign Cloud on every plan for EU and EEA customers): https://www.kugelaudio.com/en/pricing
- KugelAudio, subprocessor register: https://www.kugelaudio.com/en/trust/subprocessors
Build with KugelAudio
Put European voice infrastructure into production.
Use the EU endpoint or discuss a customer-operated Kubernetes deployment.