Intermedia
Intermedia's public feed is all buyer-education content — no shipped product in sight.
A side-by-side editorial comparison of Element Call and Red5 — release velocity, themes, recent moves, and the top alternatives to consider.
Matrix's calling app stopped negotiating which server hosts a call and let federation do it
Element Call spent June switching its default to a multi-SFU model: every participant connects to the media server attached to their own homeserver, and streams from other homeservers are pulled in subscribe-only. That removes the negotiation step that used to decide which single SFU a whole call would run on. July since then has been surface work — a default gradient background, retiring the last colors from the old design system, and mobile layout fixes for landscape one-on-one and grid modes.
Red5 ships constantly and explains almost none of it.
Red5 is a Java media server built around RTMP ingest and delivery. Releases come every few days — nine tags between early May and early July — but most publish nothing beyond an auto-generated link to the commit range. Two version schemes run side by side, with v2.0.16.46 appearing in July while the v2.0.3x series was still incrementing through June, so the tag number alone does not tell you which line a build belongs to.
Element Call spent June switching its default to a multi-SFU model: every participant connects to the media server attached to their own homeserver, and streams from other homeservers are pulled in subscribe-only. That removes the negotiation step that used to decide which single SFU a whole call would run on. July since then has been surface work — a default gradient background, retiring the last colors from the old design system, and mobile layout fixes for landscape one-on-one and grid modes.
The multi-SFU switch is the project finishing what federated calling implies: no participant's call quality should depend on which homeserver happened to win a negotiation. It was compatible for six months before becoming the default, and legacy single-SFU mode is still reachable in developer settings, which is how infrastructure changes get made in an ecosystem of independent operators. With that settled, attention has visibly moved to mobile presentation and design-system consolidation.
Expect the legacy single-SFU path to be retired once operators have migrated, and the mobile layout work to continue through the 0.23 line. Note that every entry here is a release candidate, so these tags mark what is being tested rather than what operators are running.
Red5 is a Java media server built around RTMP ingest and delivery. Releases come every few days — nine tags between early May and early July — but most publish nothing beyond an auto-generated link to the commit range. Two version schemes run side by side, with v2.0.16.46 appearing in July while the v2.0.3x series was still incrementing through June, so the tag number alone does not tell you which line a build belongs to.
Where changelogs do exist, the work is concentrated in the RTMP hot path: cutting CPU waste and allocation churn on ingest, then addressing thread oversubscription three releases later. The one capability addition visible in this window is AV1 support. Everything else that is described is dependency maintenance — Spring, Bouncy Castle — and build plumbing like on-demand Docker image pushes. The pattern is a small maintainer group optimising a mature server rather than repositioning it.
Expect the RTMP performance thread to continue and AV1 handling to be refined in follow-up releases. The undocumented releases make anything beyond that guesswork — the changelogs would need to carry content before a direction could be read from them.
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 Red5.
Intermedia's public feed is all buyer-education content — no shipped product in sight.
Ten posts, zero releases — this feed is Bizzabo's marketing engine, not its changelog.
EventMobi's feed has narrowed to one topic: registration, taught rather than shipped.
Muvi answers the infrastructure objection, publishing six OTT posts in a single morning.
A WebRTC SFU spending July on pipe-transport plumbing and a security sweep.
A mature SIP stack turns its attention to concurrency correctness and AI voice endpoints
See all Element Call alternatives → · See all Red5 alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. 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 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.
Top Red5 alternatives in Meetings are ranked by recent ship velocity. Browse the "Red5 alternatives" section above for the current picks, or visit /alternatives/red5 for the full list with editorial commentary on each.