rtpengine
rtpengine backports the same DTLS and socket fixes across four maintenance branches at once.
A side-by-side editorial comparison of coturn and Element Call — release velocity, themes, recent moves, and the top alternatives to consider.
coturn ships three minor versions in six weeks, packaged as Docker images on three registries.
The tracked feed for coturn, the open-source TURN/STUN server, is Docker image releases: 4.16.0, 4.17.0, 4.17.1, 4.17.2 and 4.18.0 between late July and early September 2026. Each is published to Docker Hub, GitHub Container Registry and Quay.io, and the release notes here point to the upstream changelog without listing changes.
Element Call drops MatrixRTC legacy mode entirely, betting the entire call stack on the multi-SFU protocol.
Element Call is deep into a protocol transition: MatrixRTC legacy mode was removed in v0.25.0-rc.1, and .well-known transport discovery was removed in v0.24.0-rc.1. Both had been optional for months before the forced cutover. The current v0.26.x RC cycle is stabilizing the post-legacy stack with bug fixes to audio output selection, memberId handling in MatrixRTC mode, and leave timing adjustments when SFU delegation is active. The product ships exclusively as release candidates at this stage, signaling it's in final pre-release hardening.
The tracked feed for coturn, the open-source TURN/STUN server, is Docker image releases: 4.16.0, 4.17.0, 4.17.1, 4.17.2 and 4.18.0 between late July and early September 2026. Each is published to Docker Hub, GitHub Container Registry and Quay.io, and the release notes here point to the upstream changelog without listing changes.
The cadence picked up: three minor versions (4.16, 4.17, 4.18) landed in about six weeks, with two same-day patch images for 4.17. The project keeps container packaging in lockstep with upstream releases, which matters to operators running TURN for WebRTC in containers.
A 4.18.x patch image or a 4.19.0 release is the likely next entry, following the observed roughly two-to-four-week rhythm; the feature content is not visible from these entries.
Element Call is deep into a protocol transition: MatrixRTC legacy mode was removed in v0.25.0-rc.1, and .well-known transport discovery was removed in v0.24.0-rc.1. Both had been optional for months before the forced cutover. The current v0.26.x RC cycle is stabilizing the post-legacy stack with bug fixes to audio output selection, memberId handling in MatrixRTC mode, and leave timing adjustments when SFU delegation is active. The product ships exclusively as release candidates at this stage, signaling it's in final pre-release hardening.
Having removed both legacy transport paths, Element Call is fully committed to a multi-SFU architecture where each homeserver operator runs their own SFU and participants connect to whichever SFUs host the streams they need. The ongoing RC cycle and the LiveKit logging improvements in v0.26.0-rc.1 point to a push for call-quality diagnostics before a stable release. Mobile performance has been a consistent focus across v0.22–v0.26 — landscape layouts, PiP mode, voice-only call handling — pointing to mobile as a priority segment.
A stable v0.26.0 release is imminent given the RC cadence. The delegated leave timing breaking change in v0.26.0-rc.2 is unfinished infrastructure for SFU delegation — that work will likely define the next development cycle.
Other Meetings products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either coturn or Element Call.
rtpengine backports the same DTLS and socket fixes across four maintenance branches at once.
OpenSIPS 4.0 is in release-candidate testing, with two RCs a month apart.
Kamailio's tracked feed shows one thing: a quiet, schema-stable 5.8 maintenance release.
JW Player is rebuilding its VOD pipeline around CMAF, one workflow fix at a time
Restream's webinars get a registration page and a CSV of leads, turning broadcasts into a pipeline
BigBlueButton 4.0 rc.4 is a security-only release as the LiveKit stack hardens.
See all coturn alternatives → · See all Element Call alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — webrtc — within Meetings. Element Call is currently shipping more aggressively (velocity 6.3 vs 2.5), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Element Call is currently shipping more aggressively (velocity 6.3 vs 2.5), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Meetings products to evaluate alongside.
Top coturn alternatives in Meetings are ranked by recent ship velocity. Browse the "coturn alternatives" section above for the current picks, or visit /alternatives/coturn for the full list with editorial commentary on each.
Top Element Call alternatives in Meetings are ranked by recent ship velocity. Browse the "Element Call alternatives" section above for the current picks, or visit /alternatives/element-call for the full list with editorial commentary on each.