If you run WebRTC at scale, a large share of your media goes through TURN relays. Restrictive NATs, enterprise firewalls, and clients that hide their IP addresses all push sessions onto relayed candidates, and when TURN server performance drops under load, call quality drops with it. This
LiveKit can run on Kubernetes without hostNetwork, which lets self-hosted LiveKit scale like any other workload and run in clusters that don’t allow host networking. Its pods stay private behind an ordinary ClusterIP Service, and STUNner, a Kubernetes-native TURN server, provides the single public address that WebRTC
Self-hosting a voice AI pipeline gives you control that managed APIs can’t offer: you choose the models, you decide where they run relative to each other, and you keep audio data within your own infrastructure. Getting there means managing GPU workloads, model placement, and service networking yourself.
We built a self-hosted video calling system for a healthcare platform client, replacing the usual “meeting link” pattern with a real phone-call flow: clinician dials, patient’s phone rings, patient answers. Highlights: Read the full WebRTC.ventures Story of Success: Self-Hosted Jitsi for Telehealth: Ringing, Answer, and Recovery Instead
