Fourwaves
Fourwaves is closing the gaps around its payments layer and its form editor at the same time.
Comparison · Meetings
Element Call vs mediasoup
A side-by-side editorial comparison of Element Call and mediasoup — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:webrtcsfu
Element Call vs mediasoup: at a glance
What is Element Call?
Element Call now routes every participant through their own homeserver's SFU.
Element Call publishes release candidates rather than finals, and is at v0.24.0-rc.1. The structural change in this window landed in v0.21.0-rc.1, which made multi-SFU the default: each participant connects to the media server associated with their own homeserver, and subscribes read-only to streams on others. Since then the work has been media quality controls, mobile layout for voice and group calls, and a breaking removal of .well-known transport discovery.
What is mediasoup?
mediasoup has moved off data-channel plumbing and into the media path — timing first, now layer selection.
The Rust line spent most of this window on single-PR point releases, nearly all of them subchannel plumbing for DataConsumers over pipe transports plus the occasional crash fix. That pattern broke with 0.26.0, a seven-PR reworking of how RTCP Sender Reports are generated, moving them off RTP packet arrival time and onto an estimate of when media was captured. 0.27.0 continues in the media path with a breaking change limiting simulcast and SVC to the preferred temporal layer. The 0.24.0 release earlier in the window also carried real security work — constant-time MAC comparison plus fixes for an OOB write and an SCTP integer overflow.
Element Call vs mediasoup: editorial side-by-side
Element Call
5.0MEETINGS
Element Call now routes every participant through their own homeserver's SFU.
◆ Current state
Element Call publishes release candidates rather than finals, and is at v0.24.0-rc.1. The structural change in this window landed in v0.21.0-rc.1, which made multi-SFU the default: each participant connects to the media server associated with their own homeserver, and subscribes read-only to streams on others. Since then the work has been media quality controls, mobile layout for voice and group calls, and a breaking removal of .well-known transport discovery.
◆ Where it's heading
The arc is toward removing negotiation and configuration from the connection path. Multi-SFU removed the argument over which server hosts a call; dropping .well-known transport discovery and the default server config removes guesses that were usually wrong. Alongside that, a steady mobile and widget-embedding thread continues, with React Compiler and spotlight re-render work aimed at the performance cost of running in someone else's app.
◆ Prediction
With multi-SFU now the default and legacy single-SFU still reachable through developer settings, the likely next step is retiring that legacy path rather than adding another connection mode.
mediasoup
6.3MEETINGS
mediasoup has moved off data-channel plumbing and into the media path — timing first, now layer selection.
◆ Current state
The Rust line spent most of this window on single-PR point releases, nearly all of them subchannel plumbing for DataConsumers over pipe transports plus the occasional crash fix. That pattern broke with 0.26.0, a seven-PR reworking of how RTCP Sender Reports are generated, moving them off RTP packet arrival time and onto an estimate of when media was captured. 0.27.0 continues in the media path with a breaking change limiting simulcast and SVC to the preferred temporal layer. The 0.24.0 release earlier in the window also carried real security work — constant-time MAC comparison plus fixes for an OOB write and an SCTP integer overflow.
◆ Where it's heading
The subchannel thread that dominated July has gone quiet and the media path has taken over. First timing correctness — RemoteClockOffsetEstimator and RemoteCaptureTimeEstimator gave the worker a notion of remote capture instants it did not previously have — and now layer selection, with 0.27.0 constraining which temporal layer simulcast and SVC will actually deliver. Both are behavior changes in what an SFU sends downstream rather than additions to its API surface, and 0.27.0 is labelled breaking, so integrators are being asked to absorb them.
◆ Prediction
With two consecutive releases changing media-path behavior, the near-term releases are likely to be corrections shaking out the new timing and layer-selection paths across simulcast and pipe transports. The capture-time estimators remain unused beyond Sender Reports, which leaves them the obvious foundation for further synchronization work.
Alternatives to Element Call and mediasoup
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 mediasoup.
HOMER
Homer's storage churn pauses long enough to ship a catalog backup CLI.
Wowza
Wowza keeps arguing its case for detection inside the streaming pipeline
Vimeo
Vimeo ships another batched product post: six changes to embeds and the player
Switcher Studio
Switcher Studio's feed is a livestreaming how-to blog, not a changelog
Mux
Every manual control Mux ships now arrives with a Robots workflow that does it for you
See all Element Call alternatives → · See all mediasoup alternatives →
Recent activity from Element Call and mediasoup
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 21h agomediasoupmediasoup caps simulcast and SVC temporal layers at the preferred one
- 1d agomediasoupmediasoup rebuilds RTCP Sender Reports around media capture time ⚡
- 7d agoElement CallMedia quality settings UI; .well-known transport discovery removed
- 8d agomediasoupmediasoup verifies DataConsumer subchannels before cloning
- 13d agomediasoupmediasoup stops checking ignoredSubchannel on piped DataConsumers
- 15d agomediasoupmediasoup adds ignored_subchannel to DirectDataProducer.send
- 19d agomediasoupmediasoup makes DataProducerOptions::new_pipe_transport public
- 21d agoElement CallLandscape mobile call layout fixes
- 1mo agoElement CallDefault gradient background and reworked mobile call design
- 1mo agoElement CallMulti-SFU becomes the default call topology ⚡
- 2mo agoElement Callmatrix_rtc_mode config option and typed connection errors
- 2mo agoElement CallBug fixes, older WebView polyfill and dependency bumps
Frequently asked questions
What is the difference between Element Call and mediasoup?
Both compete on the same themes — webrtc, sfu — within Meetings. mediasoup 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.
Is Element Call better than mediasoup?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. mediasoup 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.
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 mediasoup?
Top mediasoup alternatives in Meetings are ranked by recent ship velocity. Browse the "mediasoup alternatives" section above for the current picks, or visit /alternatives/mediasoup for the full list with editorial commentary on each.