Fourwaves
Fourwaves follows its participant inbox with a week of admin fixes and security hardening.
A side-by-side editorial comparison of HOMER and Whereby — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Whereby ships monthly digests aimed squarely at the embedding developer, not the meeting host.
The feed is a run of monthly SDK and product round-ups, consistently framed around developer experience rather than end-user features. The specifics that do surface are embedding-side: session ratings for call quality feedback, session insights, stronger authentication options, and a native iOS SDK that left beta earlier in the year.
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.
The feed is a run of monthly SDK and product round-ups, consistently framed around developer experience rather than end-user features. The specifics that do surface are embedding-side: session ratings for call quality feedback, session insights, stronger authentication options, and a native iOS SDK that left beta earlier in the year.
Whereby is a video product sold to developers who embed it, and the cadence reflects that: incremental SDK work, quality telemetry and authentication rather than the in-meeting AI features that dominate the conferencing category. The digest format itself is the notable pattern, since it bundles a month of changes behind a generic headline and makes individual releases hard to assess from the feed alone.
Expect continued monthly SDK round-ups with quality and telemetry themes; the entries carry too little detail to predict a specific capability with confidence.
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 Whereby.
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 HOMER alternatives → · See all Whereby alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. HOMER is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 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. HOMER is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 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 Whereby alternatives in Meetings are ranked by recent ship velocity. Browse the "Whereby alternatives" section above for the current picks, or visit /alternatives/whereby for the full list with editorial commentary on each.