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 3CX and HOMER — release velocity, themes, recent moves, and the top alternatives to consider.
3CX is rebuilding the PBX around MCP and a dedicated AI server, then letting admins self-serve the rest.
The V20 line is where the product is changing: Update 10 in alpha brings MCP support, a dedicated AI Server for deploying AI infrastructure, and more administrative control, while Update 9 already ships email delivery of AI agent call details, summaries, and transcripts. Around that core, the surfaces are being tidied — the Windows Softphone V5.7 migrates extensions and accounts to the desktop app in one click, and the customer portal now lets subscribers downgrade a self-managed edition or remove hosting without going through support. Routine IP phone firmware updates and a summer support-hours notice fill out the rest of the feed.
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.
The V20 line is where the product is changing: Update 10 in alpha brings MCP support, a dedicated AI Server for deploying AI infrastructure, and more administrative control, while Update 9 already ships email delivery of AI agent call details, summaries, and transcripts. Around that core, the surfaces are being tidied — the Windows Softphone V5.7 migrates extensions and accounts to the desktop app in one click, and the customer portal now lets subscribers downgrade a self-managed edition or remove hosting without going through support. Routine IP phone firmware updates and a summer support-hours notice fill out the rest of the feed.
3CX is treating AI as infrastructure a customer runs rather than a service it resells: a separate AI Server to deploy and manage, knowledge sources you prepare yourself as Markdown, and MCP as the interface for connecting outside assistants. That fits the self-hosted, admin-controlled identity the product has always sold on, and it is the opposite of the hosted-only approach most of the unified-communications field is taking. The portal changes point the same way — the subscription mechanics that used to require a conversation are becoming self-service, which is what a vendor does when it wants administrators, not account managers, driving the relationship.
Expect Update 10 to move from alpha to general availability with the AI Server as its headline, and expect the MCP surface to grow from connecting assistants into exposing call data and agent actions as tools other systems can call.
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.
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 3CX or HOMER.
A maintenance-mode Electron wrapper that reworked its window model and now gates remote control on consent.
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.
Meet is bolting consent controls onto the AI features it spent the last year adding.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. 3CX 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. 3CX 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.
Top 3CX alternatives in Meetings are ranked by recent ship velocity. Browse the "3CX alternatives" section above for the current picks, or visit /alternatives/3cx for the full list with editorial commentary on each.
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.