Fourwaves
Fourwaves is closing the gaps around its payments layer and its form editor at the same time.
A side-by-side editorial comparison of 3CX and Element Call — release velocity, themes, recent moves, and the top alternatives to consider.
3CX is rebuilding around an AI Server, and it just handed the channel the AI edition to sell.
Recent releases split between the AI Server — sizing guidance, deployment updates, MCP and admin control in the V20 Update 10 alpha — and steady client work, most recently the V5.8 softphone beta with one-click SSO and outbound number choice. Packaging moved too: partner and distributor NFR subscriptions were replaced with the AI Edition.
Element Call now routes every participant through their own homeserver's SFU.
Element Call publishes release candidates rather than finals, and is at v0.24.0-rc.1. The structural change in this window landed in v0.21.0-rc.1, which made multi-SFU the default: each participant connects to the media server associated with their own homeserver, and subscribes read-only to streams on others. Since then the work has been media quality controls, mobile layout for voice and group calls, and a breaking removal of .well-known transport discovery.
Recent releases split between the AI Server — sizing guidance, deployment updates, MCP and admin control in the V20 Update 10 alpha — and steady client work, most recently the V5.8 softphone beta with one-click SSO and outbound number choice. Packaging moved too: partner and distributor NFR subscriptions were replaced with the AI Edition.
The AI Server is being treated as infrastructure customers deploy themselves rather than a hosted add-on, with hardware guidance, dedicated deployment tooling and an MCP endpoint for connecting assistants. Putting the AI Edition into partner hands and easing self-managed subscription changes both point at pushing that stack out through the channel rather than upselling it centrally.
Expect V20 Update 10 to move from alpha toward release with the AI Server management changes already previewed, and the V5.8 softphone beta to reach general availability.
Element Call publishes release candidates rather than finals, and is at v0.24.0-rc.1. The structural change in this window landed in v0.21.0-rc.1, which made multi-SFU the default: each participant connects to the media server associated with their own homeserver, and subscribes read-only to streams on others. Since then the work has been media quality controls, mobile layout for voice and group calls, and a breaking removal of .well-known transport discovery.
The arc is toward removing negotiation and configuration from the connection path. Multi-SFU removed the argument over which server hosts a call; dropping .well-known transport discovery and the default server config removes guesses that were usually wrong. Alongside that, a steady mobile and widget-embedding thread continues, with React Compiler and spotlight re-render work aimed at the performance cost of running in someone else's app.
With multi-SFU now the default and legacy single-SFU still reachable through developer settings, the likely next step is retiring that legacy path rather than adding another connection mode.
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 Element Call.
Fourwaves is closing the gaps around its payments layer and its form editor at the same time.
Homer's storage churn pauses long enough to ship a catalog backup CLI.
mediasoup has moved off data-channel plumbing and into the media path — timing first, now layer selection.
Wowza keeps arguing its case for detection inside the streaming pipeline
Vimeo ships another batched product post: six changes to embeds and the player
Switcher Studio's feed is a livestreaming how-to blog, not a changelog
See all 3CX alternatives → · See all Element Call alternatives →
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 0 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 0 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 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.