Overview
LiveKit is a globally distributed service and regions represent geographic locations where services run. Users of LiveKit apps connect to the closest server, or edge, to minimize latency and improve the overall realtime experience.
Using default regions and allowing LiveKit to route traffic to the closest server is typically the best approach. However, in some cases, you might need to make explicit decisions about region assignment, or restrict traffic to a specific region.
Regions topics
Learn more about managing regions for your LiveKit apps with these topics.
| Component | Description | Use cases |
|---|---|---|
| Region pinning | Restrict LiveKit Cloud network traffic to a specific region. | Isolating signaling and media to a specific region. |
| Regions, regional endpoints, and static IPs | Reach a specific region with regional endpoints, and allowlist LiveKit Cloud traffic with static IP ranges. | Connecting to specific regions and allowlisting traffic in a firewall. |
| Agent deployment | Configure and manage agent deployments across multiple regions. | Deploying agents in multiple regions, optimizing latency, and managing regional deployments. |
| Region pinning for telephony | Isolate telephony traffic to a specific region to comply with local telephony regulations. | Complying with local telephony regulations and isolating calls to specific regions. |
| Observability data residency | Choose the project data region that determines where LiveKit Cloud stores your project data. | Selecting a data region at project creation, and meeting regional storage requirements. |
| EU data residency | Configure LiveKit to keep your agent stack and its data within the European Union. | Meeting GDPR and EU data residency requirements. |