Fourwaves
Fourwaves is closing the gaps around its payments layer and its form editor at the same time.
A side-by-side editorial comparison of Asterisk and SRS — release velocity, themes, recent moves, and the top alternatives to consider.
Four parallel branches, one fix set — Asterisk's changelog is a backport ledger, not a feature list.
Asterisk maintains mainline 20, 22 and 23 branches alongside a certified track, and lands each fix set across all of them at once. The June 25 batch was a coordinated security release resolving roughly 20 advisories on every branch simultaneously. The August 7 batch opens the next cycle with release candidates carrying identical commit, author and issue counts across 23.5.0, 22.11.0 and 20.21.0.
SRS opens a 7.0 line built on a Go proxy tier, and drops features it no longer wants to carry.
SRS shipped the stable 6.0 line's first release on 12 August and, three hours later, the first development build of 7.0. The 6.0 line is now in pure maintenance — the r1 changelog is seven merges of DVR, WebRTC and edge fixes. Everything new is in 7.0-d0: RTSP playback, RTMPS, IPv6 across every protocol, HEVC in both directions between RTMP and WebRTC, and HLS fMP4 segments for HEVC and LL-HLS.
Asterisk maintains mainline 20, 22 and 23 branches alongside a certified track, and lands each fix set across all of them at once. The June 25 batch was a coordinated security release resolving roughly 20 advisories on every branch simultaneously. The August 7 batch opens the next cycle with release candidates carrying identical commit, author and issue counts across 23.5.0, 22.11.0 and 20.21.0.
The visible output is backport discipline rather than feature development. Release notes carry counts, tags and advisory IDs but no feature text, so the changelog reads as a stability and security ledger for a mature telephony core. The certified track deliberately lags mainline and picks up a smaller subset of each cycle.
The three release candidates should promote to final within the project's usual short RC window, with the certified branch taking the same fixes a cycle later. Nothing in these entries points to feature work in flight.
SRS shipped the stable 6.0 line's first release on 12 August and, three hours later, the first development build of 7.0. The 6.0 line is now in pure maintenance — the r1 changelog is seven merges of DVR, WebRTC and edge fixes. Everything new is in 7.0-d0: RTSP playback, RTMPS, IPv6 across every protocol, HEVC in both directions between RTMP and WebRTC, and HLS fMP4 segments for HEVC and LL-HLS.
The project is trading breadth of legacy surface for a narrower, better-covered core. 7.0-d0 removes the embedded GB28181 SIP server, multi-threading, Cygwin, and most configuration hot reload, while introducing a Go proxy server and origin-cluster architecture alongside the C++ media core. Protocol coverage keeps generalizing — each release makes a codec or an address family a property of the server rather than of one delivery path.
Expect the 7.0 line to run a long alpha and beta train the way 6.0 did, with the Go proxy and origin clustering carrying most of the remaining work and 6.0 continuing to receive backported fixes in parallel.
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 Asterisk or SRS.
Fourwaves is closing the gaps around its payments layer and its form editor at the same time.
Homer's storage churn pauses long enough to ship a catalog backup CLI.
mediasoup has moved off data-channel plumbing and into the media path — timing first, now layer selection.
Wowza keeps arguing its case for detection inside the streaming pipeline
Vimeo ships another batched product post: six changes to embeds and the player
Switcher Studio's feed is a livestreaming how-to blog, not a changelog
See all Asterisk alternatives → · See all SRS alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. SRS is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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. SRS is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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 Asterisk alternatives in Meetings are ranked by recent ship velocity. Browse the "Asterisk alternatives" section above for the current picks, or visit /alternatives/asterisk for the full list with editorial commentary on each.
Top SRS alternatives in Meetings are ranked by recent ship velocity. Browse the "SRS alternatives" section above for the current picks, or visit /alternatives/srs for the full list with editorial commentary on each.