Skip to main content
SLNG runs in 14 regions around the world. Every region runs the complete stack: Model gateway, Execution layer, and Agent Builder. Each region has its own endpoint, reachable at its own base URL, and requests are not routed between regions. For every region and its base URL, see the regions map.

​
Why regions matter?

​
Latency.

Voice is real time and turn-taking has a hard budget. A round trip to a distant region adds hundreds of milliseconds to every turn, which is the difference between a natural conversation and a bad user experience. Running in the caller’s region is the single largest latency lever available, ahead of any model or pipeline optimization.

​
Data residency.

Voice is considered PII (Personally Identifiable information) under several compliance frameworks and regions, and a growing number of jurisdictions require it to stay inside their borders. You can learn more about our compliance here.

​
The whole stack, not just part of it.

Most platforms run models or media transport close to your users but execute the agent somewhere else. That means the component holding the actual conversation, and the context it accumulates, sits outside the region. SLNG runs the gateway, the models, the Context Router and the agent workers in the same cluster, so a region selection covers the entire request path.