Restream
Restream deepening X integration and adding Slack as a live streaming destination
Comparison · Meetings
Element Call vs HOMER
A side-by-side editorial comparison of Element Call and HOMER — release velocity, themes, recent moves, and the top alternatives to consider.
Element Call vs HOMER: at a glance
What is Element Call?
Element Call drops MatrixRTC legacy mode entirely, betting the entire call stack on the multi-SFU protocol.
Element Call is deep into a protocol transition: MatrixRTC legacy mode was removed in v0.25.0-rc.1, and .well-known transport discovery was removed in v0.24.0-rc.1. Both had been optional for months before the forced cutover. The current v0.26.x RC cycle is stabilizing the post-legacy stack with bug fixes to audio output selection, memberId handling in MatrixRTC mode, and leave timing adjustments when SFU delegation is active. The product ships exclusively as release candidates at this stage, signaling it's in final pre-release hardening.
What is HOMER?
HOMER 11.0.x fixes a critical S3/DuckDB contention bug and adds call-level fields to MCP NL search
HOMER is in active maintenance for version 11, shipping frequent patch releases that address reliability issues in its DuckDB-based analytics layer and S3 cold-tier storage. The September window shows two parallel workstreams: fixing resource contention bugs — specifically cold S3 maintenance blocking the DuckDB connection during active Node search — and expanding its MCP natural language search surface to include call-level identifiers like response_code, cid, and user_agent.
Element Call vs HOMER: editorial side-by-side
Element Call
6.3MEETINGS
Element Call drops MatrixRTC legacy mode entirely, betting the entire call stack on the multi-SFU protocol.
◆ Current state
Element Call is deep into a protocol transition: MatrixRTC legacy mode was removed in v0.25.0-rc.1, and .well-known transport discovery was removed in v0.24.0-rc.1. Both had been optional for months before the forced cutover. The current v0.26.x RC cycle is stabilizing the post-legacy stack with bug fixes to audio output selection, memberId handling in MatrixRTC mode, and leave timing adjustments when SFU delegation is active. The product ships exclusively as release candidates at this stage, signaling it's in final pre-release hardening.
◆ Where it's heading
Having removed both legacy transport paths, Element Call is fully committed to a multi-SFU architecture where each homeserver operator runs their own SFU and participants connect to whichever SFUs host the streams they need. The ongoing RC cycle and the LiveKit logging improvements in v0.26.0-rc.1 point to a push for call-quality diagnostics before a stable release. Mobile performance has been a consistent focus across v0.22–v0.26 — landscape layouts, PiP mode, voice-only call handling — pointing to mobile as a priority segment.
◆ Prediction
A stable v0.26.0 release is imminent given the RC cadence. The delegated leave timing breaking change in v0.26.0-rc.2 is unfinished infrastructure for SFU delegation — that work will likely define the next development cycle.
HOMER
5.0MEETINGS
HOMER 11.0.x fixes a critical S3/DuckDB contention bug and adds call-level fields to MCP NL search
◆ Current state
HOMER is in active maintenance for version 11, shipping frequent patch releases that address reliability issues in its DuckDB-based analytics layer and S3 cold-tier storage. The September window shows two parallel workstreams: fixing resource contention bugs — specifically cold S3 maintenance blocking the DuckDB connection during active Node search — and expanding its MCP natural language search surface to include call-level identifiers like response_code, cid, and user_agent.
◆ Where it's heading
HOMER is investing in both storage tier reliability and AI-accessible query interfaces. The MCP NL search additions suggest the project is positioning its VoIP call capture data as queryable via LLMs — a natural fit given the structured nature of SIP traffic. The ongoing S3 tiering fixes indicate the cold storage pipeline is still maturing, and the security patch (POST /exec SQL injection, in 11.0.342) reflects broadening the hardening scope as more tooling connects to the query interface.
◆ Prediction
Continued MCP query expansion is likely — response_code, cid, and user_agent are the first-tier call identifiers. Subsequent additions will probably include SDP media details, codec negotiation, and RTCP quality metrics to make the NL search genuinely useful for call quality diagnostics.
Alternatives to Element Call and HOMER
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 HOMER.
JW Player
JW Player expands ad analytics and vertical video while hardening mobile SDKs
Fourwaves
Fourwaves replaces per-event pricing with an annual submission model and lets organizers connect custom domains to event websites.
Nextcloud Talk Desktop
Nextcloud Talk Desktop 2.3.2 ships Talk v25 stable with E2EE call audio fix
BigBlueButton
BigBlueButton 4.0 enters release candidate with LiveKit fully replacing the legacy audio stack.
Nextcloud Talk
Nextcloud Talk v25 adds classified conversations and an owner role, targeting regulated enterprise deployments.
See all Element Call alternatives → · See all HOMER alternatives →
Recent activity from Element Call and HOMER
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoHOMERHOMER 11.0.353: run S3 cold maintenance on a separate DuckDB connection
- 4d agoHOMERHOMER MCP NL search now supports response_code, call ID, and user_agent fields
- 5d agoElement Callv0.26.1-rc.1
- 7d agoHOMERHOMER QoS panel now charts RTCP Receiver Reports
- 7d agoHOMERHOMER 11.0.347: MCP static auth token support and deep link auto-search fix
- 10d agoHOMERHOMER 11.0.346: preserve hot partition during incomplete S3 cold copy
- 10d agoHOMERHOMER 11.0.345: fix Azure managed-identity cleanup and release asset uploads
- 17d agoElement Callv0.26.0-rc.2
- 19d agoElement Callv0.26.0-rc.1
- 29d agoElement CallMatrixRTC legacy mode removed — all calls now run on the new protocol ⚡
- 1mo agoElement Callv0.24.0-rc.1
- 2mo agoElement Callv0.23.0-rc.1
Frequently asked questions
What is the difference between Element Call and HOMER?
They serve adjacent needs but don't currently overlap on shipped themes. Element Call 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 HOMER?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Element Call 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 HOMER?
Top HOMER alternatives in Meetings are ranked by recent ship velocity. Browse the "HOMER alternatives" section above for the current picks, or visit /alternatives/homer-voip for the full list with editorial commentary on each.