mediasoup
mediasoup has moved off data-channel plumbing and into the media path — timing first, now layer selection.
Comparison · Meetings
Fourwaves vs HOMER
A side-by-side editorial comparison of Fourwaves and HOMER — release velocity, themes, recent moves, and the top alternatives to consider.
Fourwaves vs HOMER: at a glance
What is Fourwaves?
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.
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.
Fourwaves vs HOMER: editorial side-by-side
Fourwaves
5.0MEETINGS
Fourwaves is closing the gaps around its payments layer and its form editor at the same time.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
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 Fourwaves 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 Fourwaves or HOMER.
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
WebinarJam
WebinarJam's feed is a funnel-marketing curriculum with no product releases in it.
See all Fourwaves alternatives → · See all HOMER alternatives →
Recent activity from Fourwaves and HOMER
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3h agoHOMERCatalog backup/restore CLI ships; QoS axes follow dashboard timezone
- 1d agoFourwavesSelf-service account creation from the sign-in page
- 1d agoHOMERNative compaction made safe for live catalogs; retention in hours
- 2d agoFourwavesReferenced form fields can no longer be deleted
- 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
- 6d agoFourwavesAuthorize.net added as a payment processor
- 7d agoFourwavesFree plan shown as a card in upgrade checkout
- 8d agoFourwavesTracks field usable as a confirmation-email variable
- 9d agoFourwavesFix: Website section shown to program chairs
Frequently asked questions
What is the difference between Fourwaves and HOMER?
They serve adjacent needs but don't currently overlap on shipped themes. Fourwaves 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 Fourwaves better than HOMER?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Fourwaves 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 Fourwaves?
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.
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.