Haivision
Haivision's product signal is thin under a marketing feed: SRT Gateway and ISR player get UX work
A side-by-side editorial comparison of Element Call and Jitsi — release velocity, themes, recent moves, and the top alternatives to consider.
Element Call moves to a multi-SFU architecture, ending per-call media-server negotiation
Element Call, the Matrix-native video calling app, is iterating quickly on RC builds and just made a structural change to how calls route media. The latest RC adopts a multi-SFU approach where each participant connects to the SFU tied to their own homeserver, while recent releases also steadily improve mobile layout, error reporting, and call reliability.
Jitsi's blog is largely dormant, its only fresh post a Summer-of-Code announcement
Jitsi's feed is its project blog, and it is largely dormant, the only recent post is the Google Summer of Code 2026 project announcement, after which entries drop back to late 2025 and 2024. When it does cover product, the content is substantive (receiver audio subscriptions, AV1 as the default codec, SSRC rewriting for large calls), but those posts are months to years old.
Element Call, the Matrix-native video calling app, is iterating quickly on RC builds and just made a structural change to how calls route media. The latest RC adopts a multi-SFU approach where each participant connects to the SFU tied to their own homeserver, while recent releases also steadily improve mobile layout, error reporting, and call reliability.
The direction is federation-correct real-time media: rather than negotiating a single shared SFU per call, Element Call leans into Matrix's decentralized model by letting each homeserver own its participants' media and subscribing cross-server as needed. Around that, the team keeps polishing the mobile experience (edge-to-edge, portrait one-on-one layouts, PiP) and hardening LiveKit error handling.
Expect multi-SFU to graduate from RC to default with legacy single-SFU mode kept as a fallback, followed by continued work on cross-homeserver subscription reliability and mobile polish.
Jitsi's feed is its project blog, and it is largely dormant, the only recent post is the Google Summer of Code 2026 project announcement, after which entries drop back to late 2025 and 2024. When it does cover product, the content is substantive (receiver audio subscriptions, AV1 as the default codec, SSRC rewriting for large calls), but those posts are months to years old.
This is a stale, low-frequency feed rather than an active changelog. The historical product direction, SFU performance for large calls, modern codecs, and SIP interoperability, is sound but not currently reflected in fresh posts. The recent signal is community and organizational (GSoC), not shipping.
With only a GSoC announcement as recent activity, there is not enough in this feed to predict Jitsi's next product move; the blog appears to update infrequently.
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 Jitsi.
Haivision's product signal is thin under a marketing feed: SRT Gateway and ISR player get UX work
Vimeo's feed is almost all SEO marketing; the only product signal is a batch of Live events fixes
The tracked feed is Evercast's post-production blog, not a product changelog
Digital Samba's feed is EU-sovereignty positioning and WebRTC explainers, not releases
Webex moves its agentic-workplace features from announcement toward general availability
3CX pushes its V5.6 mobile and desktop clients to production amid renewal promos.
See all Element Call alternatives → · See all Jitsi 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 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. Element Call is currently shipping more aggressively (velocity 6.3 vs 2.5), 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 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 Jitsi alternatives in Meetings are ranked by recent ship velocity. Browse the "Jitsi alternatives" section above for the current picks, or visit /alternatives/jitsi for the full list with editorial commentary on each.