Fourwaves
Fourwaves follows its participant inbox with a week of admin fixes and security hardening.
A side-by-side editorial comparison of Asterisk and HOMER — release velocity, themes, recent moves, and the top alternatives to consider.
The three-branch cycle closes: 20, 22 and 23 all promote to final with the same 28-issue set.
The release round that opened on August 7 has finished. Asterisk 20.21.0, 22.11.0 and 23.5.0 all tagged within a minute of each other, each carrying 39 commits from 16 authors, 28 resolved issues and zero security advisories. The counts are identical across all three branches, which is the same backport-in-lockstep pattern the certified track and the June security round both followed.
HOMER 11.0.369 fixes S3 auth on Ceph-based storage and stops compaction memory growth.
HOMER's 11.0 line is still hardening its DuckDB tiered-storage layer. 11.0.368 retries incomplete tier moves and fixes tiered queries that missed lake tables. The 11.0.369 pre-release stops sending the AWS session token with static S3 keys, which broke Vultr/Ceph RGW, and keeps DuckDB's file cache off on write paths so compaction memory plateaus. Security fixes (bound tiered lookup parameters, hono bump) ride alongside.
The release round that opened on August 7 has finished. Asterisk 20.21.0, 22.11.0 and 23.5.0 all tagged within a minute of each other, each carrying 39 commits from 16 authors, 28 resolved issues and zero security advisories. The counts are identical across all three branches, which is the same backport-in-lockstep pattern the certified track and the June security round both followed.
Nothing about the shape has changed: three mainline branches plus a certified track, one fix set, promoted together. The rc1-to-rc2-to-final progression narrowed from 27 issues to a single websocket segfault fix and then closed, which is a cycle converging on schedule. Release bodies still publish counts and links rather than user-facing notes, so the feed measures release discipline rather than product direction.
Expect the certified track to pick up this same fix set in its next cert release, following the lag it showed after the June round. The next mainline round should open with rc1 tags on all three branches again.
HOMER's 11.0 line is still hardening its DuckDB tiered-storage layer. 11.0.368 retries incomplete tier moves and fixes tiered queries that missed lake tables. The 11.0.369 pre-release stops sending the AWS session token with static S3 keys, which broke Vultr/Ceph RGW, and keeps DuckDB's file cache off on write paths so compaction memory plateaus. Security fixes (bound tiered lookup parameters, hono bump) ride alongside.
Almost every release since early October fixes the parquet lake: compaction, cache behaviour, tiering and S3 compatibility. The storage rewrite is being shaken out in production on more varied object stores. Feature work, such as OTLP log events on the call ladder, has paused while this stabilises.
Expect 11.0.369 to be promoted from pre-release, followed by more storage fixes for non-AWS object stores before feature work picks up again.
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 Asterisk or HOMER.
Fourwaves follows its participant inbox with a week of admin fixes and security hardening.
Element Call starts moving to new LiveKit transports and falls back to remote SFUs when needed.
JW Player moves CMAF VOD into the dashboard, adds AV1, and opens Broadcast Live to audio-only feeds.
rtpengine opens the mr26.3 branch with a rollback message and leaner call state.
Nextcloud Talk Desktop 2.3.3 adds accessibility options and bundles Talk v25.0.6.
Nextcloud Talk patches v22 and v23 while v25 stable sits five weeks past its last RC.
See all Asterisk alternatives → · See all HOMER alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Asterisk and HOMER 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. Asterisk and HOMER 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 Asterisk alternatives in Meetings are ranked by recent ship velocity. Browse the "Asterisk alternatives" section above for the current picks, or visit /alternatives/asterisk 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.