Fourwaves
Fourwaves is closing the gaps around its payments layer and its form editor at the same time.
Comparison · Meetings
FusionPBX vs HOMER
A side-by-side editorial comparison of FusionPBX and HOMER — release velocity, themes, recent moves, and the top alternatives to consider.
FusionPBX vs HOMER: at a glance
What is FusionPBX?
The release feed stops in 2018, so nothing here describes the current product
Every visible entry predates 2019. The newest is 4.4.1, a minor bug-fix release covering call centre login, device password propagation and call detail record naming. Below it sit 4.4.0 with user change logs, call recording management, QR-code provisioning and added translations, and two 4.2.x releases focused on bug fixes and SQL injection hardening in LUA scripts.
What is HOMER?
Homer's storage churn pauses long enough to ship a catalog backup CLI.
The release stream is a rapid sequence of production failures found and closed, nearly all of them in the DuckDB/DuckLake storage layer. 11.0.320 bounded a DuckDB compaction merge that was silently SIGKILLing the process with the catalog lock held and told operators not to switch to the native engine; 11.0.321 then made native compaction safe for a live catalog and added hours as a retention unit. 11.0.323 is the first quiet release in the run — a QoS chart axis fix for dashboard timezones, plus the catalog backup and restore CLI that shipped untagged in 11.0.322. Around these sit alert-query replay, per-user dashboard IDs, raised DuckDB memory caps for SIPREC ingest, and two inline GHSA fixes hardening node /query auth.
FusionPBX vs HOMER: editorial side-by-side
FusionPBX
0.0MEETINGS
The release feed stops in 2018, so nothing here describes the current product
◆ Current state
Every visible entry predates 2019. The newest is 4.4.1, a minor bug-fix release covering call centre login, device password propagation and call detail record naming. Below it sit 4.4.0 with user change logs, call recording management, QR-code provisioning and added translations, and two 4.2.x releases focused on bug fixes and SQL injection hardening in LUA scripts.
◆ Where it's heading
What the archive shows is a project that treated security hardening as release-worthy in its own right and steadily broadened administrative tooling around FreeSWITCH. What it cannot show is anything about the last several years — the feed has been silent since 2018, so no current direction is observable.
◆ Prediction
There is not enough recent data to predict a next move. Until this feed carries releases again, the product's current state is unreadable from here.
HOMER
5.0MEETINGS
Homer's storage churn pauses long enough to ship a catalog backup CLI.
◆ Current state
The release stream is a rapid sequence of production failures found and closed, nearly all of them in the DuckDB/DuckLake storage layer. 11.0.320 bounded a DuckDB compaction merge that was silently SIGKILLing the process with the catalog lock held and told operators not to switch to the native engine; 11.0.321 then made native compaction safe for a live catalog and added hours as a retention unit. 11.0.323 is the first quiet release in the run — a QoS chart axis fix for dashboard timezones, plus the catalog backup and restore CLI that shipped untagged in 11.0.322. Around these sit alert-query replay, per-user dashboard IDs, raised DuckDB memory caps for SIPREC ingest, and two inline GHSA fixes hardening node /query auth.
◆ Where it's heading
Homer is stabilizing a storage rewrite by moving work out of DuckDB rather than tuning it further — native compaction merges in Go, outside DuckDB's memory_limit, and lets DuckLake alone allocate snapshot and file IDs, the exact behavior that corrupted catalogs before. A backup and restore path for the catalog is the logical next admission that the catalog is the thing most likely to break, and shipping it inside another release rather than tagging it separately fits a project releasing several times a week. Defaults stay conservative while each escape hatch is proven.
◆ Prediction
If native compaction holds up in the field, expect it to become the default engine and the DuckDB compaction path to be deprecated; the near-term releases will likely keep closing memory and catalog-locking edges around it.
Alternatives to FusionPBX 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 FusionPBX or HOMER.
mediasoup
mediasoup has moved off data-channel plumbing and into the media path — timing first, now layer selection.
Wowza
Wowza keeps arguing its case for detection inside the streaming pipeline
Vimeo
Vimeo ships another batched product post: six changes to embeds and the player
Switcher Studio
Switcher Studio's feed is a livestreaming how-to blog, not a changelog
Mux
Every manual control Mux ships now arrives with a Robots workflow that does it for you
See all FusionPBX alternatives → · See all HOMER alternatives →
Recent activity from FusionPBX and HOMER
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3h agoHOMERCatalog backup/restore CLI ships; QoS axes follow dashboard timezone
- 1d agoHOMERNative compaction made safe for live catalogs; retention in hours
- 2d agoHOMERCompaction merge bounded after silent OOM kills on live catalogs
- 4d agoHOMERAlerts store the firing query and replay it in search
- 5d agoHOMERDuckDB memory caps raised so high ingest stops killing the engine
- 5d agoHOMERPer-user dashboard IDs unblock multi-user installs
- 8y agoFusionPBXFusionPBX 4.4.1: call centre, device and CDR fixes
- 8y agoFusionPBXFusionPBX 4.4: recordings management, QR provisioning, email templates
- 9y agoFusionPBXFusionPBX 4.2.2: default settings and SIP alias fixes
- 9y agoFusionPBXFusionPBX 4.2.1 hardens every database-touching LUA script
Frequently asked questions
What is the difference between FusionPBX and HOMER?
They serve adjacent needs but don't currently overlap on shipped themes. HOMER is currently shipping more aggressively (velocity 5.0 vs 0.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.
Is FusionPBX better than HOMER?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. HOMER is currently shipping more aggressively (velocity 5.0 vs 0.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.
What are the best alternatives to FusionPBX?
Top FusionPBX alternatives in Meetings are ranked by recent ship velocity. Browse the "FusionPBX alternatives" section above for the current picks, or visit /alternatives/fusionpbx 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.