Thanks — I understand you want your AI voice agent developed in India but hosted in Dubai. Here’s how to do that with LiveKit Cloud. 1. Region pinning (what to use) • Use LiveKit Cloud’s region pinning to set the geographic region for your project so your agent’s audio and session data run in the pinned region. 1. How to set it • Open your project in the LiveKit Cloud dashboard and go to Project Settings → Region Pinning. • Select the region closest to Dubai from the available options (if a Dubai/UAE region isn’t listed, choose the nearest Middle East region offered). • Save the setting; the project’s deployments will then use that pinned region. 1. Deploying after pinning • Deploy your agent as usual (for example:

lk agent deploy

). Ensure your deployment/config (e.g.,

livekit.toml

) doesn’t override the dashboard pinning. 1. Important notes • Observability data and logs are stored in the United States regardless of pinned region. • Inference/LLM/STT/TTS providers must also support the chosen region if you need inference to remain in-region. If a provider doesn’t operate in that region, inference traffic may route elsewhere. Quick question to confirm: do you see a Middle East / Dubai-close region in your Project Settings now, or should I walk you through checking that and the dashboard screens? Sources: Data Processing Addendum | LiveKit | LiveKit | LiveKit Pricing | Examples | livekit/livekit_composite | DeepWiki | Deploying to production | LiveKit Docs