Jitsi Meet Desktop
A maintenance-mode Electron wrapper that reworked its window model and now gates remote control on consent.
A side-by-side editorial comparison of HOMER and Evercast — release velocity, themes, recent moves, and the top alternatives to consider.
A tight patch train is still paying off HOMER's move to a DuckLake storage engine.
HOMER 11 is shipping point releases every few days, and nearly all of them touch the DuckLake-backed storage layer it now runs on: partition hygiene, snapshot expiry, tiered-volume reclaim, corrupt metadata detection. The capture and correlation side is getting real work too, most notably transitive B2B call-leg resolution. This is a project stabilizing a storage migration in public rather than adding surface.
Evercast sells on credits, not releases — the feed is case studies, not shipped product.
Evercast's public feed is a marketing blog rather than a changelog: film and TV case studies (Avatar: The Way of Water, Ozark), editor interviews, conference talks, and remote-work think pieces. The only product artifact visible anywhere in the input is the 3.0 desktop app announcement, and it sits outside the recent window. The technical pitch stays consistent across the posts — WebRTC pushed toward studio-grade audio and video for live remote review sessions.
HOMER 11 is shipping point releases every few days, and nearly all of them touch the DuckLake-backed storage layer it now runs on: partition hygiene, snapshot expiry, tiered-volume reclaim, corrupt metadata detection. The capture and correlation side is getting real work too, most notably transitive B2B call-leg resolution. This is a project stabilizing a storage migration in public rather than adding surface.
The pattern across these releases is a backend that works but hasn't yet been made operationally boring. Storage bugs keep arriving from the field — future-dated partitions from bad RTPengine timestamps, obsolete files never physically deleted, corrupt table ids — which is what a young lakehouse layer under real VoIP capture volume looks like. Correlation and the coordinator API are where the actual feature work is landing, aimed at operators running multi-B2BUA chains and GitOps-managed deployments.
Expect the patch cadence to continue on storage correctness and retention until field reports thin out; the aliases CRUD API documented in 11.0.301 suggests config-as-code deployment is the next area to get real attention.
Evercast's public feed is a marketing blog rather than a changelog: film and TV case studies (Avatar: The Way of Water, Ozark), editor interviews, conference talks, and remote-work think pieces. The only product artifact visible anywhere in the input is the 3.0 desktop app announcement, and it sits outside the recent window. The technical pitch stays consistent across the posts — WebRTC pushed toward studio-grade audio and video for live remote review sessions.
The content mix points at go-to-market motion rather than product motion: proof-by-credit (named productions, named editors) plus standards-body visibility at IEEE RTC, where the CEO framed WebRTC data-channel streaming for game development, remote direction, and virtual sets. Game development reads as a second target beyond film post. Nothing published in this window indicates what is being built next.
With no release notes in this feed, the next product move isn't predictable from this source — what's unclear is whether anything has shipped since 3.0 at all. Expect more case studies and conference appearances until Evercast publishes an actual changelog.
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 HOMER or Evercast.
A maintenance-mode Electron wrapper that reworked its window model and now gates remote control on consent.
3CX is rebuilding the PBX around MCP and a dedicated AI server, then letting admins self-serve the rest.
Daily one-line releases, currently pointed at multi-event payment administration.
PeerJS keeps publishing release candidates that restate the same two fixes.
This feed is an archive of old Slack desktop releases, not current product news.
Discord is turning the chat client into a storefront and Nitro into a rewards program.
See all HOMER alternatives → · See all Evercast alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. HOMER and Evercast are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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. HOMER and Evercast are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Meetings products to evaluate alongside.
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.
Top Evercast alternatives in Meetings are ranked by recent ship velocity. Browse the "Evercast alternatives" section above for the current picks, or visit /alternatives/evercast for the full list with editorial commentary on each.