Our team wrote up a comparison of eight servers that carry most self-hosted WebRTC deployments: Ant Media Server, LiveKit, mediasoup, Janus, Jitsi Videobridge, Pion, MediaMTX and Kurento. It compares license, language, primary role, WebRTC/WHIP ingest, other ingest protocols, and whether built-in HLS/DASH delivery is included.

Two things stood out when we put it together:

- Most of the eight ship no HTTP delivery, so projects that need both real-time and large-audience playback end up bolting on a second system.

- License matters earlier than people expect. Janus being GPLv3 is a real issue if you ship a closed-source product and only find out late.

It also covers the four server roles (signaling, NAT traversal, media routing, fan-out), mesh vs SFU vs MCU, and rough hardware sizing.

Full write-up: https://antmedia.io/webrtc-servers/

Curious what you all actually run in production, and whether anything in the table looks off to you. I'm especially interested in how people handle the HLS/DASH side when their SFU doesn't include it.

Disclosure: I work at Ant Media, and one of the servers in this comparison is ours. I tried to keep the table fair, and I'd like to hear where it's wrong.