Request for Recommended LiveKit Deployment Architecture (Private Networking)

Self Hosting
1

Hi LiveKit Team,

We are planning a production deployment of LiveKit with SIP integration and would like guidance on the recommended private network architecture.

Our goal is to keep all internal communication on private networking wherever possible, including:

  • LiveKit Server

  • LiveKit SIP Server

  • Redis

  • Agent Workers (STT/TTS/LLM orchestration)

  • TURN/Coturn

  • SIP SBC (OpenSIPS)

Current deployment target is AWS.

We would like to understand the recommended architecture for:

  1. Private communication between LiveKit and LiveKit SIP

  2. Private communication between LiveKit and Agent Workers

  3. Redis placement and networking best practices

  4. Multi-node LiveKit deployment across availability zones

  5. TURN server placement (public vs private)

  6. SIP server connectivity (whether LiveKit SIP should communicate with SBC over private IPs)

  7. Recommended load balancer strategy (ALB/NLB)

  8. High Availability design for 50–100 concurrent voice/video sessions

  9. Any networking or NAT considerations that should be avoided

Our current understanding is that only media ingress/egress and TURN should require public exposure, while all backend services should remain on private subnets.

Could you please share the recommended production architecture and any reference deployments for AWS?

Thank you.

1 Like
2

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.