Hi, I know from previous posts that there are few requests on whether we could change the location of servers to other region and the answer was no. Any plan for this to change? For compliance & regulatory purposes, most of clients outside of US would need their data be hosted locally. Any plan for Vapi to allow this? If not, any reason as to why? @Gilang

For compliance and data residency, you can configure custom bucket storage (e.g., AWS S3, GCP, Azure) in your required region and use your own LLM, transcriber, and voice servers hosted locally. However, Vapi's orchestration layer (real-time conversation logic) must still run on Vapi's US/EU infrastructure, and there are currently no announced plans to allow full relocation of this component. Example:

yaml
storage:
  provider: aws-s3
  region: eu-west-1
  bucket: your-eu-bucket

This setup ensures your call data is stored locally, but some ephemeral processing remains on Vapi's infrastructure. For more details, see the [Vapi data flow documentation](https://docs.vapi.ai/security-and-privacy/data-flow). Source: - [Vapi Data Flow & Regional Compliance](https://docs.vapi.ai/security-and-privacy/data-flow)

Hi, Current state: Vapi’s core orchestration layer (which handles things like endpointing, interruption detection, and background noise filtering) currently runs on US/EU infrastructure only. This is part of Vapi’s core platform and can’t be changed today. An important note: audio processed by the orchestration layer is ephemeral - it isn’t stored. Only final artifacts like transcripts and logs are retained (unless specific compliance modes apply). Data residency options available today: For compliance and regulatory needs, Vapi supports a Bring Your Own Infrastructure approach so most data can stay in your required region: - LLM: Use a custom LLM server or providers with regional endpoints (e.g., Azure OpenAI supports many global regions). - Transcription: Use a custom transcriber or providers with EU/US data residency options. - TTS: Use a custom TTS server in your region. - Storage: Store recordings, transcripts, and logs in your own regional storage (AWS S3, GCP, Azure Blob, Cloudflare R2, etc.). With this setup, only ephemeral orchestration signals pass through Vapi’s infrastructure; persistent data can remain fully regional. Docs for reference: - Data flow: https://docs.vapi.ai/security-and-privacy/data-flow - Custom LLM: https://docs.vapi.ai/customization/custom-llm/using-your-server - Custom transcriber: https://docs.vapi.ai/customization/custom-transcriber - Regional LLMs (Azure): https://docs.vapi.ai/providers/model/azure-openai - Custom storage: https://docs.vapi.ai/providers/cloud/s3