Fourwaves
Fourwaves is closing the gaps around its payments layer and its form editor at the same time.
Comparison · Meetings
Asterisk vs HOMER
A side-by-side editorial comparison of Asterisk and HOMER — release velocity, themes, recent moves, and the top alternatives to consider.
Asterisk vs HOMER: at a glance
What is Asterisk?
Four parallel branches, one fix set — Asterisk's changelog is a backport ledger, not a feature list.
Asterisk maintains mainline 20, 22 and 23 branches alongside a certified track, and lands each fix set across all of them at once. The June 25 batch was a coordinated security release resolving roughly 20 advisories on every branch simultaneously. The August 7 batch opens the next cycle with release candidates carrying identical commit, author and issue counts across 23.5.0, 22.11.0 and 20.21.0.
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.
Asterisk vs HOMER: editorial side-by-side
Asterisk
5.0MEETINGS
Four parallel branches, one fix set — Asterisk's changelog is a backport ledger, not a feature list.
◆ Current state
Asterisk maintains mainline 20, 22 and 23 branches alongside a certified track, and lands each fix set across all of them at once. The June 25 batch was a coordinated security release resolving roughly 20 advisories on every branch simultaneously. The August 7 batch opens the next cycle with release candidates carrying identical commit, author and issue counts across 23.5.0, 22.11.0 and 20.21.0.
◆ Where it's heading
The visible output is backport discipline rather than feature development. Release notes carry counts, tags and advisory IDs but no feature text, so the changelog reads as a stability and security ledger for a mature telephony core. The certified track deliberately lags mainline and picks up a smaller subset of each cycle.
◆ Prediction
The three release candidates should promote to final within the project's usual short RC window, with the certified branch taking the same fixes a cycle later. Nothing in these entries points to feature work in flight.
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 Asterisk 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 Asterisk 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 Asterisk alternatives → · See all HOMER alternatives →
Recent activity from Asterisk 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
- 11d agoAsteriskCertified 22.8-cert4: 8 community-reported fixes
- 11d agoAsterisk23.5.0-rc1 opens the cycle with 27 issues resolved
- 11d agoAsterisk22.11.0-rc1 mirrors the 23.5.0 fix set
- 11d agoAsterisk20.21.0-rc1 carries the same set back to the LTS line
- 1mo agoAsterisk23.4.1 security release resolves 20 advisories
- 1mo agoAsterisk22.10.1 takes the same 20-advisory security set
Frequently asked questions
What is the difference between Asterisk and HOMER?
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.
Is Asterisk better than HOMER?
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.
What are the best alternatives to Asterisk?
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.
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.