Hey LiveKit team! Need clarification for Saudi Ara...
# agents
b
Hey LiveKit team! Need clarification for Saudi Arabia compliance - data must stay in KSA borders πŸ‡ΈπŸ‡¦ Questions: 1. Agent deployment in KSA - available? If YES β†’ how do we specify it + does WebRTC service also automatically stay in KSA? 2. If agent deployment NOT available β†’ can we still use your WebRTC service in KSA region with our self-hosted agents? If YES β†’ how do we configure/pin it? 3. If neither available in KSA β†’ means we self-host both, right? Basically: what's available in KSA region, how to configure it, and what's our minimum viable setup for compliance? Thanks! πŸ™
l
Hi, 1. We only support US and EU agent deployment for agents hosted in LiveKit cloud: https://docs.livekit.io/deploy/admin/regions/ 2. Yes, you can pin your traffic to the
me
region that covers Saudi Arabia and UAE. This is available on
scale
plan or higher. Details here: https://docs.livekit.io/telephony/features/region-pinning/#enabling-protocol-based-region-pinning
b
Thanks
Hi , Clarification on region pinning scope:
If we pin WebRTC traffic to me region (Saudi Arabia) using region pinning:
Can an agent deployed in your USA cloud still join/access those pinned WebRTC rooms?
Or does region pinning *block all connections* (including agents) from outside the pinned region?
l
It would not be able to. There are also regional restrictions for SIP, if you were planning on integrating telephony. We have a number of customers in Saudi Arabia with similar restrictions, who have successfully deployed - you might want to contact our sales team through https://livekit.io/contact-sales for more hands-on guidance, for example which models support KSA data residency - I'm not sure on that one myself.
b
Thank you