This page is intended for customers with EU data-processing requirements. EU region access is granted on request. Please reach out to your Tavus contact before relying on it in production.
Overview
By default, conversations created viaPOST /v2/conversations are processed in the US region. When you set region to "eu", Tavus routes every layer of the CVI stack to its EU counterpart, including speech-to-text (STT), text-to-speech (TTS) and all other inference.
This is EU data processing, not data residency. Tavus does not offer data-residency regions, and persisted data remains stored in the US. To satisfy EU requirements, pair region: "eu" with Zero Data Retention (ZDR). With ZDR enabled, Tavus does not retain customer content, so no conversation data is stored outside the EU.
TTS layer
Withregion: "eu", Tavus routes TTS to the EU servers of the PAL’s TTS provider. You don’t need any extra configuration.
You can optionally supply your own TTS API key for Cartesia or ElevenLabs in the PAL’s tts layer. If you do, we recommend setting up that key to route to the provider’s EU servers:
- Cartesia: EU deployments are a Cartesia Enterprise feature. Ask Cartesia to enable regional access for your organization.
- ElevenLabs: Use an EU-hosted ElevenLabs API key. These keys end with the
_residency_eusuffix, and Tavus routes them to ElevenLabs’s EU endpoint.
external_voice_id in the PAL’s tts layer must belong to your EU account.
Create an EU-region Conversation
Step 1: Configure your PAL's TTS layer
When creating (or updating) the PAL you’ll use for the conversation, configure the
tts layer:- Tavus automatic routing
- Custom TTS API key
Leave out
api_key to use Tavus’s TTS key. Tavus routes TTS to the provider’s EU servers automatically:Step 2: Create the conversation with region="eu"
Pass
"region": "eu" in the request body when creating the conversation:cURL
Replace
<api_key> with your actual API key. You can generate one in the PAL Maker. If region is omitted, the conversation defaults to "us".
