Haivision vs Element Call
Side-by-side trajectory, velocity, and editorial themes.
Haivision's product signal is thin under a marketing feed: SRT Gateway and ISR player get UX work
Haivision's crawled feed is mostly thought-leadership and customer-story marketing across defense, public safety, and broadcast video. The genuine product signal is narrow: a UX overhaul of the SRT Gateway (visual workflows, mobile support, thumbnail previews) and capability content around the Play ISR Premium player (interactive mapping, annotations, collaboration). New broadcast hardware — Makito ONE, Falkon X4 — surfaces through NAB and customer recaps rather than changelog releases.
Where signal exists, Haivision is refining operator experience on existing platforms — making IP video routing and ISR analysis easier to drive visually — while its hardware momentum lives in trade-show and customer narratives. This is a marketing-led feed; product direction has to be inferred from a handful of feature-adjacent posts rather than a release stream.
Expect continued UX modernization of the SRT Gateway and ISR tooling and further broadcast-contribution hardware (Makito ONE, Falkon X4) positioning, though the blog-style feed makes precise release timing hard to call.
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.
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.
See more alternatives to Haivision →
See more alternatives to Element Call →