diff --git a/fern/docs.yml b/fern/docs.yml
index 162641a96..ef815129a 100644
--- a/fern/docs.yml
+++ b/fern/docs.yml
@@ -868,6 +868,8 @@ navigation:
             contents:
               - page: Data flow
                 path: security-and-privacy/data-flow.mdx
+              - page: EU region and data residency
+                path: security-and-privacy/eu-region.mdx
               - page: API keys
                 path: security-and-privacy/api-keys.mdx
               - page: Single Sign-On (SSO)
diff --git a/fern/security-and-privacy/eu-region.mdx b/fern/security-and-privacy/eu-region.mdx
new file mode 100644
index 000000000..5cd3d840d
--- /dev/null
+++ b/fern/security-and-privacy/eu-region.mdx
@@ -0,0 +1,45 @@
+---
+title: EU region and data residency
+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
+---
+
+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.
+
+## EU region endpoints
+
+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.
+
+| | 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` |
+
+## Build in the EU region
+
+If your organization is in the EU region, keep every request and resource on the EU endpoints:
+
+- 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).
+
+Each region is a separate, isolated environment, so keep your API key, endpoints, and SIP host all in the same region.
+
+## EU outbound IP addresses
+
+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:
+
+- `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 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
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
   </Accordion>
   <Accordion title="Do you support on-premise deployments?" icon="building" iconType="solid" defaultOpen={false}>
 
-Yes, we support on-premise deployments for large Enterprises.
+No, Vapi does not support on-premise deployments.
 
   </Accordion>
   <Accordion title="Do you support multi-tenancy?" icon="building" iconType="solid" defaultOpen={false}>