From f6feaa6089d4d1db93d7af8c9dde7c0eb2754365 Mon Sep 17 00:00:00 2001 From: Steve Smtih Date: Wed, 26 Aug 2026 09:25:33 -0700 Subject: [PATCH 1/5] Add EU region & data residency page --- fern/security-and-privacy/eu-region.mdx | 59 +++++++++++++++++++++++++ 1 file changed, 59 insertions(+) create mode 100644 fern/security-and-privacy/eu-region.mdx diff --git a/fern/security-and-privacy/eu-region.mdx b/fern/security-and-privacy/eu-region.mdx new file mode 100644 index 000000000..a77d74c39 --- /dev/null +++ b/fern/security-and-privacy/eu-region.mdx @@ -0,0 +1,59 @@ +--- +title: EU region & data residency +subtitle: Where the EU region stands today, and what to do if you need EU-hosted data residency +slug: security-and-privacy/eu-region +--- + +## Overview + +Vapi organizations run in one of two regions. Each region has its own dashboard, API base URL, and SIP host, and resources (assistants, tools, phone numbers, SIP trunk credentials) belong to a single organization in a single region. + +| Region | Dashboard | API base URL | SIP host | +| --- | --- | --- | --- | +| United States | `dashboard.vapi.ai` | `https://api.vapi.ai` | `sip.vapi.ai` | +| European Union | `dashboard.eu.vapi.ai` | `https://api.eu.vapi.ai` | `sip.eu.vapi.ai` | + + +Vapi's EU support and self-serve growth are frozen until 2027. Existing EU customers can continue using their accounts, but Vapi is not offering new add-ons and does not guarantee feature parity with the US region. New self-serve customers should [create an account in the US region](https://dashboard.vapi.ai/register). If you require Vapi-hosted EU data residency, [contact Sales](https://vapi.ai/sales) about selective enterprise onboarding. + + +This is why `dashboard.eu.vapi.ai` has no self-serve sign-up flow right now: EU organizations are provisioned individually for approved enterprise cases rather than created through a public registration form. + +## What to do based on your situation + +**You don't have a Vapi organization yet.** +Create your account in the US region at [dashboard.vapi.ai](https://dashboard.vapi.ai/register). This is the default and fully self-serve path. + +**You already have an EU organization.** +Keep using it as-is. You won't see new EU add-ons roll out on the same timeline as the US region, and some newer features may not be available yet in the EU region. + +**You need your data hosted or processed in the EU (GDPR, data residency, or a customer requirement).** +EU hosting is not currently self-serve. [Contact Sales](https://vapi.ai/sales) to discuss selective enterprise onboarding into the EU region, or see [On-premise deployment](#need-eu-data-residency-without-waiting-for-eu-hosting) below for an option available today. + +## Can I migrate my existing US organization to the EU region? + +Not through self-serve tools. Assistants, tools, phone numbers, SIP trunk credentials, and other resources are scoped to the organization and region they were created in, and there is currently no dashboard or API action that moves an organization, or its resources, from the US region to the EU region. + +If EU hosting is a requirement, [contact Sales](https://vapi.ai/sales) to scope enterprise onboarding into the EU region. Enterprise onboarding is evaluated case by case; it is not a guaranteed or immediate migration path, and it does not automatically carry over existing US-region resources. + +## Need EU data residency without waiting for EU hosting? + +If self-hosting rather than waiting on EU-region access fits your compliance needs, Vapi offers an on-premise deployment model where audio and text data stays within your own infrastructure and never passes through Vapi's servers. This is available today regardless of the EU-region freeze above. Contact **support@vapi.ai** to request on-premise setup documentation. + +## Using the EU region today (existing EU organizations) + +If you already have an EU organization, keep every request, credential, and SIP host in that same region: + +- Use your **EU dashboard private key** with `https://api.eu.vapi.ai`, not `https://api.vapi.ai`. +- Create SIP phone numbers with a `sipUri` on `sip.eu.vapi.ai`, matching your EU-region assistant. +- If your SIP provider or firewall requires IP allowlisting, use the EU signaling IPs from the [SIP networking and firewall configuration](/advanced/sip/sip-networking) reference. + + +Mixing regions (for example, an EU API key with a `sip.vapi.ai` SIP URI) will fail. The API base URL, private key, and SIP host must all match the same region. + + +## Related + +- [SIP introduction](/advanced/sip) — setting up SIP calls per region +- [Data flow](/security-and-privacy/data-flow) — what data is processed and stored, and where +- [GDPR compliance](/security-and-privacy/GDPR) — legal bases, data subject rights, and transborder transfers From f562ba9b06c2c0b045552944169b3296dbd2d963 Mon Sep 17 00:00:00 2001 From: Steve Smtih Date: Wed, 26 Aug 2026 09:29:37 -0700 Subject: [PATCH 2/5] Add EU region & data residency nav entry --- fern/docs.yml | 132 +++++++++++++++++++++++++++----------------------- 1 file changed, 71 insertions(+), 61 deletions(-) diff --git a/fern/docs.yml b/fern/docs.yml index 7f2136b83..44f133251 100644 --- a/fern/docs.yml +++ b/fern/docs.yml @@ -287,12 +287,20 @@ navigation: path: customization/custom-voices/playht.mdx - page: Cartesia path: customization/custom-voices/cartesia.mdx - - page: Custom transcriber + - page: Gandr + path: customization/custom-voices/gandr.mdx + - section: Custom transcriber path: customization/custom-transcriber.mdx icon: fa-light fa-microphone - - page: Custom TTS + contents: + - page: Gradium + path: customization/custom-transcriber/gradium.mdx + - section: Custom TTS path: customization/custom-tts.mdx icon: fa-light fa-volume-high + contents: + - page: Gradium + path: customization/custom-tts/gradium.mdx - section: Custom LLMs icon: fa-light fa-brain-circuit contents: @@ -362,7 +370,7 @@ navigation: path: advanced/sip/sip-telnyx.mdx - page: DIDWW path: advanced/sip/sip-didww.mdx - - page: DIDLogic + - page: didlogic path: advanced/sip/sip-didlogic.mdx - page: Zadarma path: advanced/sip/sip-zadarma.mdx @@ -636,50 +644,34 @@ navigation: collapsed: true icon: fa-light fa-link contents: - - section: Voices (Text-to-speech) - path: providers/voice/overview.mdx - icon: fa-light fa-waveform-lines + - section: Transcribers (Speech-to-text) + path: providers/transcriber/overview.mdx + icon: fa-light fa-microphone contents: - - section: Vapi Voices - path: providers/voice/vapi-voices.mdx - contents: - - page: Legacy migration - path: providers/voice/vapi-voices/legacy-migration.mdx - icon: fa-light fa-triangle-exclamation + - page: AssemblyAI + path: providers/transcriber/assembly-ai.mdx - page: Azure - path: providers/voice/azure.mdx + path: providers/transcriber/azure.mdx - page: Cartesia - path: providers/voice/cartesia.mdx + path: providers/transcriber/cartesia.mdx - page: Deepgram - path: providers/voice/deepgram.mdx + path: providers/transcriber/deepgram.mdx - page: ElevenLabs - path: providers/voice/elevenlabs.mdx - - page: Hume - path: providers/voice/hume.mdx - - page: Inworld - path: providers/voice/inworld.mdx - - page: LMNT - path: providers/voice/imnt.mdx - - page: Microsoft - path: providers/voice/microsoft.mdx - - page: MiniMax - path: providers/voice/minimax.mdx - - page: Neuphonic - path: providers/voice/neuphonic.mdx + path: providers/transcriber/elevenlabs.mdx + - page: Gladia + path: providers/transcriber/gladia.mdx + - page: Google + path: providers/transcriber/google.mdx - page: OpenAI - path: providers/voice/openai.mdx - - page: PlayHT - path: providers/voice/playht.mdx - - page: RimeAI - path: providers/voice/rimeai.mdx - - page: Sesame - path: providers/voice/sesame.mdx - - page: Smallest AI - path: providers/voice/smallest-ai.mdx - - page: WellSaid - path: providers/voice/wellsaid.mdx + path: providers/transcriber/openai.mdx + - page: Soniox + path: providers/transcriber/soniox.mdx + - page: Speechmatics + path: providers/transcriber/speechmatics.mdx + - page: Talkscriber + path: providers/transcriber/talkscriber.mdx - page: xAI - path: providers/voice/xai.mdx + path: providers/transcriber/xai.mdx - section: Large language models path: providers/model/overview.mdx @@ -720,34 +712,50 @@ navigation: - page: xAI path: providers/model/xai.mdx - - section: Transcribers (Speech-to-text) - path: providers/transcriber/overview.mdx - icon: fa-light fa-microphone + - section: Voices (Text-to-speech) + path: providers/voice/overview.mdx + icon: fa-light fa-waveform-lines contents: - - page: AssemblyAI - path: providers/transcriber/assembly-ai.mdx + - section: Vapi Voices + path: providers/voice/vapi-voices.mdx + contents: + - page: Legacy migration + path: providers/voice/vapi-voices/legacy-migration.mdx + icon: fa-light fa-triangle-exclamation - page: Azure - path: providers/transcriber/azure.mdx + path: providers/voice/azure.mdx - page: Cartesia - path: providers/transcriber/cartesia.mdx + path: providers/voice/cartesia.mdx - page: Deepgram - path: providers/transcriber/deepgram.mdx + path: providers/voice/deepgram.mdx - page: ElevenLabs - path: providers/transcriber/elevenlabs.mdx - - page: Gladia - path: providers/transcriber/gladia.mdx - - page: Google - path: providers/transcriber/google.mdx + path: providers/voice/elevenlabs.mdx + - page: Hume + path: providers/voice/hume.mdx + - page: Inworld + path: providers/voice/inworld.mdx + - page: LMNT + path: providers/voice/imnt.mdx + - page: Microsoft + path: providers/voice/microsoft.mdx + - page: MiniMax + path: providers/voice/minimax.mdx + - page: Neuphonic + path: providers/voice/neuphonic.mdx - page: OpenAI - path: providers/transcriber/openai.mdx - - page: Soniox - path: providers/transcriber/soniox.mdx - - page: Speechmatics - path: providers/transcriber/speechmatics.mdx - - page: Talkscriber - path: providers/transcriber/talkscriber.mdx + path: providers/voice/openai.mdx + - page: PlayHT + path: providers/voice/playht.mdx + - page: RimeAI + path: providers/voice/rimeai.mdx + - page: Sesame + path: providers/voice/sesame.mdx + - page: Smallest AI + path: providers/voice/smallest-ai.mdx + - page: WellSaid + path: providers/voice/wellsaid.mdx - page: xAI - path: providers/transcriber/xai.mdx + path: providers/voice/xai.mdx - section: Cloud storage icon: fa-light fa-cloud-arrow-up @@ -822,6 +830,8 @@ navigation: contents: - page: Data flow path: security-and-privacy/data-flow.mdx + - page: EU region & data residency + path: security-and-privacy/eu-region.mdx - page: API keys path: security-and-privacy/api-keys.mdx - page: Single Sign-On (SSO) From 2663d48a68e4d40b2d661f3a5143cd6e470d25f5 Mon Sep 17 00:00:00 2001 From: Stephen Smith Date: Thu, 3 Sep 2026 14:57:27 -0700 Subject: [PATCH 3/5] docs: correct EU region page and on-prem FAQ - Remove on-prem deployment section (not a supported offering) and its inline link - Correct FAQ snippet on-prem answer to "not supported" - Add required description frontmatter - Trim top warning, rename Overview heading, spell out title, Related colons Co-Authored-By: Claude Opus 4.8 --- fern/docs.yml | 2 +- fern/security-and-privacy/eu-region.mdx | 21 +++++++++------------ fern/snippets/faq-snippet.mdx | 2 +- 3 files changed, 11 insertions(+), 14 deletions(-) diff --git a/fern/docs.yml b/fern/docs.yml index 44f133251..5f19e083a 100644 --- a/fern/docs.yml +++ b/fern/docs.yml @@ -830,7 +830,7 @@ navigation: contents: - page: Data flow path: security-and-privacy/data-flow.mdx - - page: EU region & data residency + - page: EU region and data residency path: security-and-privacy/eu-region.mdx - page: API keys path: security-and-privacy/api-keys.mdx diff --git a/fern/security-and-privacy/eu-region.mdx b/fern/security-and-privacy/eu-region.mdx index a77d74c39..6b375d097 100644 --- a/fern/security-and-privacy/eu-region.mdx +++ b/fern/security-and-privacy/eu-region.mdx @@ -1,10 +1,11 @@ --- -title: EU region & data residency -subtitle: Where the EU region stands today, and what to do if you need EU-hosted data residency +title: EU region and data residency +subtitle: Where the EU region stands today, and what to do if you need EU-hosted data residency. +description: Vapi's EU region and data residency: how regions are scoped, why EU self-serve signup is closed, and how existing EU organizations keep requests in-region. slug: security-and-privacy/eu-region --- -## Overview +## US and EU regions Vapi organizations run in one of two regions. Each region has its own dashboard, API base URL, and SIP host, and resources (assistants, tools, phone numbers, SIP trunk credentials) belong to a single organization in a single region. @@ -14,7 +15,7 @@ Vapi organizations run in one of two regions. Each region has its own dashboard, | European Union | `dashboard.eu.vapi.ai` | `https://api.eu.vapi.ai` | `sip.eu.vapi.ai` | -Vapi's EU support and self-serve growth are frozen until 2027. Existing EU customers can continue using their accounts, but Vapi is not offering new add-ons and does not guarantee feature parity with the US region. New self-serve customers should [create an account in the US region](https://dashboard.vapi.ai/register). If you require Vapi-hosted EU data residency, [contact Sales](https://vapi.ai/sales) about selective enterprise onboarding. +Vapi's EU support and self-serve growth are frozen until 2027. New self-serve customers should [create an account in the US region](https://dashboard.vapi.ai/register); if you require Vapi-hosted EU data residency, [contact Sales](https://vapi.ai/sales) about selective enterprise onboarding. This is why `dashboard.eu.vapi.ai` has no self-serve sign-up flow right now: EU organizations are provisioned individually for approved enterprise cases rather than created through a public registration form. @@ -28,7 +29,7 @@ Create your account in the US region at [dashboard.vapi.ai](https://dashboard.va Keep using it as-is. You won't see new EU add-ons roll out on the same timeline as the US region, and some newer features may not be available yet in the EU region. **You need your data hosted or processed in the EU (GDPR, data residency, or a customer requirement).** -EU hosting is not currently self-serve. [Contact Sales](https://vapi.ai/sales) to discuss selective enterprise onboarding into the EU region, or see [On-premise deployment](#need-eu-data-residency-without-waiting-for-eu-hosting) below for an option available today. +EU hosting is not currently self-serve. [Contact Sales](https://vapi.ai/sales) to discuss selective enterprise onboarding into the EU region. ## Can I migrate my existing US organization to the EU region? @@ -36,10 +37,6 @@ Not through self-serve tools. Assistants, tools, phone numbers, SIP trunk creden If EU hosting is a requirement, [contact Sales](https://vapi.ai/sales) to scope enterprise onboarding into the EU region. Enterprise onboarding is evaluated case by case; it is not a guaranteed or immediate migration path, and it does not automatically carry over existing US-region resources. -## Need EU data residency without waiting for EU hosting? - -If self-hosting rather than waiting on EU-region access fits your compliance needs, Vapi offers an on-premise deployment model where audio and text data stays within your own infrastructure and never passes through Vapi's servers. This is available today regardless of the EU-region freeze above. Contact **support@vapi.ai** to request on-premise setup documentation. - ## Using the EU region today (existing EU organizations) If you already have an EU organization, keep every request, credential, and SIP host in that same region: @@ -54,6 +51,6 @@ Mixing regions (for example, an EU API key with a `sip.vapi.ai` SIP URI) will fa ## Related -- [SIP introduction](/advanced/sip) — setting up SIP calls per region -- [Data flow](/security-and-privacy/data-flow) — what data is processed and stored, and where -- [GDPR compliance](/security-and-privacy/GDPR) — legal bases, data subject rights, and transborder transfers +- [SIP introduction](/advanced/sip): setting up SIP calls per region +- [Data flow](/security-and-privacy/data-flow): what data is processed and stored, and where +- [GDPR compliance](/security-and-privacy/GDPR): legal bases, data subject rights, and transborder transfers diff --git a/fern/snippets/faq-snippet.mdx b/fern/snippets/faq-snippet.mdx index 6c28b30fc..0d9b71308 100644 --- a/fern/snippets/faq-snippet.mdx +++ b/fern/snippets/faq-snippet.mdx @@ -98,7 +98,7 @@ Yes, Vapi is a API-first platform. This means can bake it in your product withou -Yes, we support on-premise deployments for large Enterprises. +No, Vapi does not support on-premise deployments. From ecf4502e0544bc11f0f9de2a7d6c6da6693e0751 Mon Sep 17 00:00:00 2001 From: Stephen Smith Date: Thu, 3 Sep 2026 15:11:58 -0700 Subject: [PATCH 4/5] fix: quote EU region description frontmatter (colon broke YAML) Co-Authored-By: Claude Opus 4.8 --- fern/security-and-privacy/eu-region.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fern/security-and-privacy/eu-region.mdx b/fern/security-and-privacy/eu-region.mdx index 6b375d097..03b90ae35 100644 --- a/fern/security-and-privacy/eu-region.mdx +++ b/fern/security-and-privacy/eu-region.mdx @@ -1,7 +1,7 @@ --- title: EU region and data residency subtitle: Where the EU region stands today, and what to do if you need EU-hosted data residency. -description: Vapi's EU region and data residency: how regions are scoped, why EU self-serve signup is closed, and how existing EU organizations keep requests in-region. +description: "Vapi's EU region and data residency: how regions are scoped, why EU self-serve signup is closed, and how existing EU organizations keep requests in-region." slug: security-and-privacy/eu-region --- From 0964cd81233b607cd00c68d0c0dcf1f49dfdb0f4 Mon Sep 17 00:00:00 2001 From: Stephen Smith Date: Fri, 4 Sep 2026 12:24:36 -0700 Subject: [PATCH 5/5] Added IP address for EU --- fern/security-and-privacy/eu-region.mdx | 65 ++++++++++--------------- 1 file changed, 27 insertions(+), 38 deletions(-) diff --git a/fern/security-and-privacy/eu-region.mdx b/fern/security-and-privacy/eu-region.mdx index 03b90ae35..5cd3d840d 100644 --- a/fern/security-and-privacy/eu-region.mdx +++ b/fern/security-and-privacy/eu-region.mdx @@ -1,56 +1,45 @@ --- title: EU region and data residency -subtitle: Where the EU region stands today, and what to do if you need EU-hosted data residency. -description: "Vapi's EU region and data residency: how regions are scoped, why EU self-serve signup is closed, and how existing EU organizations keep requests in-region." +subtitle: Build and run your voice agents in Vapi's EU region. +description: "Build in Vapi's EU region: the EU dashboard, API, and SIP endpoints, the outbound IP addresses to allowlist, and keeping your organization in-region." slug: security-and-privacy/eu-region --- -## US and EU regions +Vapi's EU region lets you build and run voice agents hosted in the European Union. If your organization is in the EU region, use the EU endpoints below for everything: the dashboard, API calls, and SIP. -Vapi organizations run in one of two regions. Each region has its own dashboard, API base URL, and SIP host, and resources (assistants, tools, phone numbers, SIP trunk credentials) belong to a single organization in a single region. +## EU region endpoints -| Region | Dashboard | API base URL | SIP host | -| --- | --- | --- | --- | -| United States | `dashboard.vapi.ai` | `https://api.vapi.ai` | `sip.vapi.ai` | -| European Union | `dashboard.eu.vapi.ai` | `https://api.eu.vapi.ai` | `sip.eu.vapi.ai` | +Each Vapi organization belongs to a single region, and every resource (assistants, tools, phone numbers, SIP trunk credentials) lives with it. Use the endpoints that match your organization's region. - -Vapi's EU support and self-serve growth are frozen until 2027. New self-serve customers should [create an account in the US region](https://dashboard.vapi.ai/register); if you require Vapi-hosted EU data residency, [contact Sales](https://vapi.ai/sales) about selective enterprise onboarding. - +| | United States | European Union | +| --- | --- | --- | +| Dashboard | `dashboard.vapi.ai` | `dashboard.eu.vapi.ai` | +| API base URL | `https://api.vapi.ai` | `https://api.eu.vapi.ai` | +| SIP host | `sip.vapi.ai` | `sip.eu.vapi.ai` | -This is why `dashboard.eu.vapi.ai` has no self-serve sign-up flow right now: EU organizations are provisioned individually for approved enterprise cases rather than created through a public registration form. +## Build in the EU region -## What to do based on your situation +If your organization is in the EU region, keep every request and resource on the EU endpoints: -**You don't have a Vapi organization yet.** -Create your account in the US region at [dashboard.vapi.ai](https://dashboard.vapi.ai/register). This is the default and fully self-serve path. +- Make API calls to `https://api.eu.vapi.ai` using a key from your EU dashboard. +- Create SIP phone numbers and trunks with a `sipUri` on `sip.eu.vapi.ai`. +- For SIP firewall allowlisting, use the EU addresses in the [SIP networking reference](/advanced/sip/sip-networking). -**You already have an EU organization.** -Keep using it as-is. You won't see new EU add-ons roll out on the same timeline as the US region, and some newer features may not be available yet in the EU region. +Each region is a separate, isolated environment, so keep your API key, endpoints, and SIP host all in the same region. -**You need your data hosted or processed in the EU (GDPR, data residency, or a customer requirement).** -EU hosting is not currently self-serve. [Contact Sales](https://vapi.ai/sales) to discuss selective enterprise onboarding into the EU region. +## EU outbound IP addresses -## Can I migrate my existing US organization to the EU region? +Vapi's outbound HTTP requests from the EU region (webhooks, tool calls, and other requests to your server) originate from a fixed set of EU addresses. Allowlist these if your server restricts inbound traffic by IP: -Not through self-serve tools. Assistants, tools, phone numbers, SIP trunk credentials, and other resources are scoped to the organization and region they were created in, and there is currently no dashboard or API action that moves an organization, or its resources, from the US region to the EU region. - -If EU hosting is a requirement, [contact Sales](https://vapi.ai/sales) to scope enterprise onboarding into the EU region. Enterprise onboarding is evaluated case by case; it is not a guaranteed or immediate migration path, and it does not automatically carry over existing US-region resources. - -## Using the EU region today (existing EU organizations) - -If you already have an EU organization, keep every request, credential, and SIP host in that same region: - -- Use your **EU dashboard private key** with `https://api.eu.vapi.ai`, not `https://api.vapi.ai`. -- Create SIP phone numbers with a `sipUri` on `sip.eu.vapi.ai`, matching your EU-region assistant. -- If your SIP provider or firewall requires IP allowlisting, use the EU signaling IPs from the [SIP networking and firewall configuration](/advanced/sip/sip-networking) reference. - - -Mixing regions (for example, an EU API key with a `sip.vapi.ai` SIP URI) will fail. The API base URL, private key, and SIP host must all match the same region. - +- `3.74.75.238/32` +- `3.77.231.137/32` +- `3.120.216.209/32` +- `3.127.10.26/32` +- `63.182.246.187/32` +- `63.184.196.2/32` ## Related -- [SIP introduction](/advanced/sip): setting up SIP calls per region -- [Data flow](/security-and-privacy/data-flow): what data is processed and stored, and where -- [GDPR compliance](/security-and-privacy/GDPR): legal bases, data subject rights, and transborder transfers +- [SIP networking and firewall configuration](/advanced/sip/sip-networking): EU SIP hosts and allowlist addresses +- [Data flow](/security-and-privacy/data-flow): what data Vapi processes and stores, and where +- [GDPR compliance](/security-and-privacy/GDPR): legal bases, data subject rights, and data transfers