Fourwaves
Fourwaves adds custom domain support for event websites, removing the hosted-subdomain constraint for conference organizers
A side-by-side editorial comparison of HOMER and Vidyo — release velocity, themes, recent moves, and the top alternatives to consider.
HOMER patches a SQL injection in /exec and stabilizes Azure and DuckDB storage in 11.0.x
HOMER is an open-source VoIP call capture and observability platform running a rapid 11.0.x patch cadence. The 11.0.342 release closed a SQL injection vulnerability in the POST /exec endpoint by parameterizing the query, accompanied by security dependency bumps across hono, js-yaml, and gRPC. The storage layer has received parallel stability work: OTLP tables now participate in compaction and retention discovery, DuckDB temp directory configuration is pinned for tiering reliability, and Azure managed-identity orphan records are cleaned up.
Vidyo's tracked feed is largely scraped historical release notes — quiet on net-new direction.
Vidyo's last ten entries are a mix of corporate boilerplate, release-notes index pages, and historical version notes (versions 18.2.6 through 23.1.0 surfacing out of order). The substantive items concern OPUS audio codec support, AES-256 media encryption, a stethoscope integration for healthcare use, breakout rooms, and a PinParticipant API. Most of those are older feature notes being re-served by the feed source.
HOMER is an open-source VoIP call capture and observability platform running a rapid 11.0.x patch cadence. The 11.0.342 release closed a SQL injection vulnerability in the POST /exec endpoint by parameterizing the query, accompanied by security dependency bumps across hono, js-yaml, and gRPC. The storage layer has received parallel stability work: OTLP tables now participate in compaction and retention discovery, DuckDB temp directory configuration is pinned for tiering reliability, and Azure managed-identity orphan records are cleaned up.
The Azure Blob Storage DuckLake backend added in 11.0.334 extends HOMER's tiering from S3-only to multi-cloud, and the subsequent Azure patches show that path is being actively maintained. The overall posture across this window is incremental hardening—security patching, dependency governance, and infrastructure reliability—rather than new user-facing features. The DuckLake integration (DuckDB + S3/Azure tiering) appears to be HOMER's infrastructure bet for handling high-volume VoIP capture at scale.
The next meaningful move is likely formal documentation and operator onboarding for the DuckLake multi-cloud storage tier; the backend is functionally in place for both S3 and Azure, and the stability patches suggest it is approaching production readiness.
Vidyo's last ten entries are a mix of corporate boilerplate, release-notes index pages, and historical version notes (versions 18.2.6 through 23.1.0 surfacing out of order). The substantive items concern OPUS audio codec support, AES-256 media encryption, a stethoscope integration for healthcare use, breakout rooms, and a PinParticipant API. Most of those are older feature notes being re-served by the feed source.
Vidyo's posture in this feed reads like a mature enterprise video platform doing standards work (codec, encryption) and vertical integrations (healthcare via stethoscopes) rather than chasing the AI-meeting-assistant arms race that Zoom, Teams, and Google Meet are running. There is no AI summarization, transcription, or agent surface in any of these entries.
Without fresher entries it's hard to call the next concrete move, but the visible pattern points to continued enterprise/regulated-vertical hardening (encryption, compliance, codec support) before any AI-meeting feature surfaces. If the feed is genuinely current, that absence of AI is itself the loudest signal.
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 Vidyo.
Fourwaves adds custom domain support for event websites, removing the hosted-subdomain constraint for conference organizers
BigBlueButton 4.0 enters release candidate with LiveKit fully replacing the legacy audio stack.
JW Player automates CMAF rendition ladders and sharpens ad attribution by player and placement
Nextcloud Talk Desktop is approaching Talk v25 stable while its July managed-config feature unlocks enterprise mass deployment for the first time.
Nextcloud Talk v25 adds classified conversations and an owner role, targeting regulated enterprise deployments.
Element Call is removing its legacy architecture — the federated multi-SFU model is now the only option.
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 Vidyo alternatives in Meetings are ranked by recent ship velocity. Browse the "Vidyo alternatives" section above for the current picks, or visit /alternatives/vidyo for the full list with editorial commentary on each.