HOMER
Homer's storage churn pauses long enough to ship a catalog backup CLI.
A side-by-side editorial comparison of Asterisk and Fourwaves — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Fourwaves is closing the gaps around its payments layer and its form editor at the same time.
Fourwaves publishes a near-daily, one-line changelog covering small changes to the conference organiser's admin surface. The August window is dominated by payments and money administration: transaction filtering by organisation and by payment gateway, the Free plan surfaced in the upgrade checkout, and Authorize.net added as a supported processor. The two newest entries move elsewhere — self-service account creation from the sign-in page, and a guard that blocks deleting fields, sections, or choices still referenced elsewhere in an event, with a warning naming what depends on them.
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.
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.
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.
Fourwaves publishes a near-daily, one-line changelog covering small changes to the conference organiser's admin surface. The August window is dominated by payments and money administration: transaction filtering by organisation and by payment gateway, the Free plan surfaced in the upgrade checkout, and Authorize.net added as a supported processor. The two newest entries move elsewhere — self-service account creation from the sign-in page, and a guard that blocks deleting fields, sections, or choices still referenced elsewhere in an event, with a warning naming what depends on them.
The work is aimed at multi-event organisations rather than single-conference organisers; transaction filtering and a second payment processor only matter if you run several events through shared gateways. The referential-integrity guard on form fields points at the same maturity problem from the other side — events configured deeply enough that deleting a field silently breaks something downstream, which is a complaint you only get once customers build complex forms. Individually each change is minor; together they describe a platform being made to hold more events per customer.
Expect the payments thread to continue — further gateway options or per-organisation payment configuration are the natural next step now that transactions can be filtered by gateway. The date-stamped daily format suggests the cadence holds regardless of the size of what ships.
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 Fourwaves.
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
Every manual control Mux ships now arrives with a Robots workflow that does it for you
See all Asterisk alternatives → · See all Fourwaves 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 Fourwaves 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 Fourwaves 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 Fourwaves alternatives in Meetings are ranked by recent ship velocity. Browse the "Fourwaves alternatives" section above for the current picks, or visit /alternatives/fourwaves for the full list with editorial commentary on each.