Wowza
Wowza keeps arguing its case for detection inside the streaming pipeline
A side-by-side editorial comparison of HOMER and Mux — release velocity, themes, recent moves, and the top alternatives to consider.
Homer's native compaction engine goes from do-not-touch to safe-to-try in one day.
The release stream is a rapid sequence of production failures found and closed, nearly all of them in the DuckDB/DuckLake storage layer. The last two entries tell one story: 11.0.320 bounded a DuckDB compaction merge that was silently SIGKILLing the process with the catalog lock held, and explicitly told operators not to switch to the native engine; 11.0.321 then made native compaction safe for a live catalog. Around that sit alert-query replay, per-user dashboard IDs, raised DuckDB memory caps for SIPREC ingest, an Arrow timestamp-unit fix, opt-in time-range routing, and two inline GHSA fixes hardening node /query auth.
Every manual control Mux ships now arrives with a Robots workflow that does it for you
Mux is building out Robots, its automated video-processing layer, faster than anything else in the product. Six workflows landed at once at the start of July — captions, dubbing, scene detection, thumbnails, engagement insights — followed by an API for creating and running Directives programmatically. The most recent releases pair a manual control with its automated counterpart: set a default thumbnail by hand via API or dashboard, or let the find-best-thumbnail workflow choose one.
The release stream is a rapid sequence of production failures found and closed, nearly all of them in the DuckDB/DuckLake storage layer. The last two entries tell one story: 11.0.320 bounded a DuckDB compaction merge that was silently SIGKILLing the process with the catalog lock held, and explicitly told operators not to switch to the native engine; 11.0.321 then made native compaction safe for a live catalog. Around that sit alert-query replay, per-user dashboard IDs, raised DuckDB memory caps for SIPREC ingest, an Arrow timestamp-unit fix, opt-in time-range routing, and two inline GHSA fixes hardening node /query auth.
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. The same instinct shows in the coordinator's smart routing, which avoids querying storage nodes that cannot hold the window, and in raising container memory ceilings rather than shrinking workloads. Defaults stay conservative while each escape hatch is proven.
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.
Mux is building out Robots, its automated video-processing layer, faster than anything else in the product. Six workflows landed at once at the start of July — captions, dubbing, scene detection, thumbnails, engagement insights — followed by an API for creating and running Directives programmatically. The most recent releases pair a manual control with its automated counterpart: set a default thumbnail by hand via API or dashboard, or let the find-best-thumbnail workflow choose one.
The shape is consistent enough to read as deliberate. A capability ships as a manual control, then as a Robots workflow, then becomes reachable from the API — thumbnails have now completed all three steps within six weeks. Alongside that, the player SDKs keep absorbing platform-specific delivery work, with offline Widevine downloads the latest addition on Android. Billing and reporting get occasional attention but are not where the investment is.
Expect the remaining manual asset controls to acquire matching Robots workflows, and for those workflows to be exposed through the Directives API as they land.
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 HOMER or Mux.
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
WebinarJam's feed is a funnel-marketing curriculum with no product releases in it.
Muvi cleared SOC 2 and immediately turned it into the centerpiece of its enterprise pitch.
3CX is rebuilding around an AI Server, and it just handed the channel the AI edition to sell.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Mux is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Mux is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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.
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.
Top Mux alternatives in Meetings are ranked by recent ship velocity. Browse the "Mux alternatives" section above for the current picks, or visit /alternatives/mux for the full list with editorial commentary on each.