← Back to home
Comparison · Meetings

Element Call vs Red5

A side-by-side editorial comparison of Element Call and Red5 — release velocity, themes, recent moves, and the top alternatives to consider.

Element Call vs Red5: at a glance

FeatureElement CallRed5
SectorMeetingsMeetings
Velocity score6.32.5
Sparks · 30d00
Top themesmatrix, webrtc, federation, multi-sfumedia-server, rtmp, av1, streaming-performance
Last editorial update3d ago1h ago
WebsiteVisit →Visit →

What is Element Call?

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.

Read the full Element Call trajectory →

What is Red5?

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.

Read the full Red5 trajectory →

Element Call vs Red5: editorial side-by-side

E
Element Call
MEETINGS
6.3

Matrix's calling app stopped negotiating which server hosts a call and let federation do it

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

R
Red5
MEETINGS
2.5

Red5 ships constantly and explains almost none of it.

◆ Current state

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 it's heading

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.

◆ Prediction

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.

Alternatives to Element Call and Red5

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.

See all Element Call alternatives → · See all Red5 alternatives →

Recent activity from Element Call and Red5

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 4d agoElement CallLandscape mobile calls get a proper one-on-one layout
  2. 18d agoElement CallGradient background by default and old design-system colors removed
  3. 24d agoRed5Red5 2.0.16.46 ships with no published changes
  4. 1mo agoElement CallMulti-SFU becomes the default for calls
  5. 1mo agoElement Callmatrix_rtc_mode config option and typed homeserver errors
  6. 1mo agoRed5Red5 2.0.40 ships with no published changes
  7. 1mo agoRed5Red5 2.0.39 adds AV1 support
  8. 2mo agoElement CallDevice switcher labels and older WebView polyfill
  9. 2mo agoRed5Red5 2.0.38 fixes RTMP thread oversubscription
  10. 2mo agoRed5Red5 2.0.37 ships with no published changes
  11. 2mo agoRed5Red5 2.0.36 cuts CPU waste in RTMP ingest
  12. 2mo agoElement CallFast call switcher and portrait one-on-one layout

Frequently asked questions

What is the difference between Element Call and Red5?

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.

Is Element Call better than Red5?

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.

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 Red5?

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.