coturn
coturn ships three minor versions in six weeks, packaged as Docker images on three registries.
A side-by-side editorial comparison of rtpengine and Wowza — release velocity, themes, recent moves, and the top alternatives to consider.
rtpengine backports the same DTLS and socket fixes across four maintenance branches at once.
Sipwise's rtpengine media proxy is maintaining several release lines in parallel (mr13.5, mr14.1, mr26.0, mr26.1, mr26.2), and most recent entries are coordinated backports. The September 16 batch fixes hash-table updates, nested string lookups and stop_forwarding mixups across four branches, and adds DTLS negotiation corrections (setup=actpass logic, ignoring incorrect DTLS=passive, keeping TLS IDs on answer role changes) to the mr26.0 and mr26.1 lines.
Wowza is rebuilding around one idea: run computer vision inside the streaming pipeline.
Wowza's feed is a marketing blog, not a changelog — every entry is a short teaser ending in an ellipsis, with the substance behind the link. Read for direction rather than scope, it is almost entirely about the Video Intelligence Framework: object detection, scene analysis, vision-language models, synthetic video detection, and custom model support, all running on the same media server that ingests and delivers the stream. The one release-shaped item in this window remains NVIDIA's Synthetic Video Detector shipping as a VIF module; the newest post is a customer story rather than a capability.
Sipwise's rtpengine media proxy is maintaining several release lines in parallel (mr13.5, mr14.1, mr26.0, mr26.1, mr26.2), and most recent entries are coordinated backports. The September 16 batch fixes hash-table updates, nested string lookups and stop_forwarding mixups across four branches, and adds DTLS negotiation corrections (setup=actpass logic, ignoring incorrect DTLS=passive, keeping TLS IDs on answer role changes) to the mr26.0 and mr26.1 lines.
The work is focused on correctness in media negotiation, especially DTLS role handling and ICE on closed sockets, rather than new features. The newest branch, mr26.2, also brought AMR fmtp defaults, mirroring of generated RTCP sender reports to Homer, and recording cleanup hardening, which points to better interop and observability for carrier deployments.
More synchronized backport releases across the mr13.5 through mr26.2 lines are the clear pattern; feature work will most likely keep landing on mr26.2 first.
Wowza's feed is a marketing blog, not a changelog — every entry is a short teaser ending in an ellipsis, with the substance behind the link. Read for direction rather than scope, it is almost entirely about the Video Intelligence Framework: object detection, scene analysis, vision-language models, synthetic video detection, and custom model support, all running on the same media server that ingests and delivers the stream. The one release-shaped item in this window remains NVIDIA's Synthetic Video Detector shipping as a VIF module; the newest post is a customer story rather than a capability.
Wowza is repositioning from media server to inference point, and the marketing has shifted from explaining the idea to proving it. The earlier posts argued that analysis belongs inside the pipeline rather than in a second system downstream; the recent ones supply a named deployment — Oceaneering running VIF on live subsea ROV video — and press the installed base still on Streaming Engine 4.8 to upgrade. A reference account and upgrade pressure arriving together is what a vendor does when it is converting an existing base rather than chasing new ones.
With a named customer now published and upgrade pressure already applied, expect more vertical case studies in industrial and infrastructure monitoring rather than new VIF capability announcements. The teaser-only feed will not reveal VIF pricing or packaging.
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 rtpengine or Wowza.
coturn ships three minor versions in six weeks, packaged as Docker images on three registries.
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 rtpengine alternatives → · See all Wowza alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Wowza is currently shipping more aggressively (velocity 6.3 vs 5.0), 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. Wowza is currently shipping more aggressively (velocity 6.3 vs 5.0), 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 rtpengine alternatives in Meetings are ranked by recent ship velocity. Browse the "rtpengine alternatives" section above for the current picks, or visit /alternatives/rtpengine for the full list with editorial commentary on each.
Top Wowza alternatives in Meetings are ranked by recent ship velocity. Browse the "Wowza alternatives" section above for the current picks, or visit /alternatives/wowza for the full list with editorial commentary on each.