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
STUNner is a Kubernetes-native TURN server, TURN being the relay protocol that gives WebRTC clients a public endpoint to send media through. It builds on the Gateway API to terminate TURN at a single load balancer endpoint and relay media to the pod behind it, so media-server
The Janus WebRTC Server is one of the most pleasant WebRTC media servers to build on, and it’s a bonus that it is open source. It’s small, fast, and modular: a thin C core with plugins for exactly the workloads you need, a clean signaling API, and
TURN servers remain one of the most common points of confusion in WebRTC applications. While STUN and TURN servers both play critical roles in establishing WebRTC peer connections, teams new to WebRTC development often struggle to understand their differences and implementation details. Even experienced developers may overlook
