HOMER
HOMER patches a SQL injection in /exec and stabilizes Azure and DuckDB storage in 11.0.x
A side-by-side editorial comparison of Wildix and Element Call — release velocity, themes, recent moves, and the top alternatives to consider.
Wildix opens up an agentic-AI revenue platform on top of its UCaaS, doubling down on European sovereignty.
The dominant move in this window is Revenue Intelligence — an AI-powered platform layered on Wildix's communications stack, marketed around 100% visibility into sales communications, automated dashboards, and an 'Ask Wilma AI' query surface positioned as agentic. Surrounding it: scraped changelog navigation pages for WMS 6/7 and Salesforce/Microservices, plus three press releases (MSP-UK channel events, an industry spokesperson appointment, and a digital-sovereignty positioning piece tied to France's pivot away from US collaboration platforms).
Element Call is removing its legacy architecture — the federated multi-SFU model is now the only option.
Element Call has spent the last two months removing compatibility scaffolding: MatrixRTC legacy mode (v0.25.0) and .well-known transport discovery (v0.24.0) are both gone. Every participant now connects to their homeserver's SFU with no fallback to the old negotiated single-SFU model. React Compiler is enabled for rendering performance, and media quality settings got a dedicated UI in v0.24.0. The RC release cadence is high while stable releases remain patch-focused.
The dominant move in this window is Revenue Intelligence — an AI-powered platform layered on Wildix's communications stack, marketed around 100% visibility into sales communications, automated dashboards, and an 'Ask Wilma AI' query surface positioned as agentic. Surrounding it: scraped changelog navigation pages for WMS 6/7 and Salesforce/Microservices, plus three press releases (MSP-UK channel events, an industry spokesperson appointment, and a digital-sovereignty positioning piece tied to France's pivot away from US collaboration platforms).
Wildix is repositioning from a European UCaaS vendor into an AI-native business-communications platform with a vertical (revenue operations) lifted out of the call surface. The European-sovereignty framing is being weaponized as competitive positioning against Microsoft Teams and Zoom in the public sector. The product feed itself is mostly index pages — actual changelog entries live one click deeper than this scraper sees.
Expect more agentic AI surfaces stacked on top of communications data — likely customer-experience scoring, automated coaching, and outbound-call assistance — and continued public-sector wins in France, Italy, and Germany framed as sovereign alternatives. A second 'AI Wilma' vertical (likely customer support or HR) is plausible within two to three quarters.
Element Call has spent the last two months removing compatibility scaffolding: MatrixRTC legacy mode (v0.25.0) and .well-known transport discovery (v0.24.0) are both gone. Every participant now connects to their homeserver's SFU with no fallback to the old negotiated single-SFU model. React Compiler is enabled for rendering performance, and media quality settings got a dedicated UI in v0.24.0. The RC release cadence is high while stable releases remain patch-focused.
The architecture is settled: federated multi-SFU, homeserver-anchored, no legacy bridges. The breaking changes are pruning maintenance surface rather than adding capability. The next period is likely refinement — call quality controls, edge-case stability, and mobile experience polish — within the established architecture. Element Call's trajectory is now governed by the Matrix ecosystem roadmap more than its own feature backlog.
Stable releases catching up to the RC channel, with polish on the media quality controls from v0.24.0 and mobile layout improvements. Homeserver-level call routing policies are a plausible next capability now that the SFU model is uniform across all deployments.
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 Wildix or Element Call.
HOMER patches a SQL injection in /exec and stabilizes Azure and DuckDB storage in 11.0.x
Fourwaves adds custom domain support for event websites, removing the hosted-subdomain constraint for conference organizers
BigBlueButton 4.0 enters release candidate with LiveKit fully replacing the legacy audio stack.
JW Player automates CMAF rendition ladders and sharpens ad attribution by player and placement
Nextcloud Talk Desktop is approaching Talk v25 stable while its July managed-config feature unlocks enterprise mass deployment for the first time.
Nextcloud Talk v25 adds classified conversations and an owner role, targeting regulated enterprise deployments.
See all Wildix 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. Wildix and Element Call are shipping at a similar cadence (velocity 6.3 vs 6.3, 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. Wildix and Element Call are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Meetings products to evaluate alongside.
Top Wildix alternatives in Meetings are ranked by recent ship velocity. Browse the "Wildix alternatives" section above for the current picks, or visit /alternatives/wildix 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.