HOMER
HOMER patches a SQL injection in /exec and stabilizes Azure and DuckDB storage in 11.0.x
Comparison · Meetings
Element Call vs SRS
A side-by-side editorial comparison of Element Call and SRS — release velocity, themes, recent moves, and the top alternatives to consider.
Element Call vs SRS: at a glance
What is Element Call?
Element Call is removing its legacy architecture — the federated multi-SFU model is now the only option.
Element Call has spent the last two months removing compatibility scaffolding: MatrixRTC legacy mode (v0.25.0) and .well-known transport discovery (v0.24.0) are both gone. Every participant now connects to their homeserver's SFU with no fallback to the old negotiated single-SFU model. React Compiler is enabled for rendering performance, and media quality settings got a dedicated UI in v0.24.0. The RC release cadence is high while stable releases remain patch-focused.
What is SRS?
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.
Element Call vs SRS: editorial side-by-side
Element Call
6.3MEETINGS
Element Call is removing its legacy architecture — the federated multi-SFU model is now the only option.
◆ Current state
Element Call has spent the last two months removing compatibility scaffolding: MatrixRTC legacy mode (v0.25.0) and .well-known transport discovery (v0.24.0) are both gone. Every participant now connects to their homeserver's SFU with no fallback to the old negotiated single-SFU model. React Compiler is enabled for rendering performance, and media quality settings got a dedicated UI in v0.24.0. The RC release cadence is high while stable releases remain patch-focused.
◆ Where it's heading
The architecture is settled: federated multi-SFU, homeserver-anchored, no legacy bridges. The breaking changes are pruning maintenance surface rather than adding capability. The next period is likely refinement — call quality controls, edge-case stability, and mobile experience polish — within the established architecture. Element Call's trajectory is now governed by the Matrix ecosystem roadmap more than its own feature backlog.
◆ Prediction
Stable releases catching up to the RC channel, with polish on the media quality controls from v0.24.0 and mobile layout improvements. Homeserver-level call routing policies are a plausible next capability now that the SFU model is uniform across all deployments.
SRS
6.3MEETINGS
SRS opens a 7.0 line built on a Go proxy tier, and drops features it no longer wants to carry.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to Element Call and SRS
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 Element Call or SRS.
Fourwaves
Fourwaves adds custom domain support for event websites, removing the hosted-subdomain constraint for conference organizers
BigBlueButton
BigBlueButton 4.0 enters release candidate with LiveKit fully replacing the legacy audio stack.
JW Player
JW Player automates CMAF rendition ladders and sharpens ad attribution by player and placement
Nextcloud Talk Desktop
Nextcloud Talk Desktop is approaching Talk v25 stable while its July managed-config feature unlocks enterprise mass deployment for the first time.
Nextcloud Talk
Nextcloud Talk v25 adds classified conversations and an owner role, targeting regulated enterprise deployments.
See all Element Call alternatives → · See all SRS alternatives →
Recent activity from Element Call and SRS
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 7d agoElement Callv0.26.0-rc.2
- 9d agoElement Callv0.26.0-rc.1
- 19d agoElement CallElement Call v0.25.0 removes MatrixRTC legacy mode, requiring full multi-SFU migration ⚡
- 1mo agoSRSSRS 7.0-d0: Go proxy tier, RTSP playback, IPv6 across protocols ⚡
- 1mo agoSRS6.0-r1: DVR, WebRTC and edge fixes on the stable line
- 1mo agoElement CallElement Call v0.24.0: React Compiler enabled, media quality UI, legacy transport removed
- 1mo agoElement Callv0.23.0-rc.1
- 2mo agoElement CallElement Call v0.22.0: Mobile call UI overhaul with gradient backgrounds as default
- 9mo agoSRSSRS 6.0 goes stable with H.265 across RTMP, HLS, TS and SRT ⚡
- 10mo agoSRS6.0-b3: use-after-free and HLS cleanup fixes
- 11mo agoSRS6.0-b2: configurable SRT stream IDs and a WHIP transcoding fix
- 1y agoSRS6.0-b1: RTC crash fixes, Windows binary dropped
Frequently asked questions
What is the difference between Element Call and SRS?
They serve adjacent needs but don't currently overlap on shipped themes. Element Call and SRS are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Element Call better than SRS?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Element Call and SRS are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Meetings products to evaluate alongside.
What are the best alternatives to Element Call?
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.
What are the best alternatives to SRS?
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.