Webex
The feed is a marketing blog; the actual GA announcements arrive between the thought leadership
Comparison · Meetings
HOMER vs Wowza
A side-by-side editorial comparison of HOMER and Wowza — release velocity, themes, recent moves, and the top alternatives to consider.
HOMER vs Wowza: at a glance
What is HOMER?
HOMER 11's DuckLake rearchitecture is in its hardening phase, shipping near-daily.
HOMER is releasing at near-daily cadence — twelve tags across 11.0.304 to 11.0.315 in nine days. The work concentrates on the DuckDB/DuckLake storage layer that HOMER 11 is built on: sanitizing bad RTPengine HEP timestamps that were creating future date partitions, stopping false-positive forbidden-keyword matches on Call-IDs, reconnecting DuckDB on catalog refresh. Two security advisories closed in the same window — a self-service admin escalation via PATCH /api/v4/users/:id, and an under-authenticated node /query endpoint that also exposed DuckDB external scanners. Separately, the search UI learned to treat HEP node name as an identity distinct from the numeric capture ID.
What is Wowza?
Wowza is turning its media server into an inference layer, and NVIDIA just shipped a model into it.
Nearly every recent post orbits one thing: the Wowza Video Intelligence Framework, an intelligence layer for Streaming Engine that pulls frames out of live streams, routes them to AI models, and converts inference results into metadata, overlays, alerts and logs. The framework supports customer-trained custom models, and the pitch is explicitly architectural — analysis running on the same media server that ingests and delivers the video, rather than in a separate downstream system. NVIDIA's Synthetic Video Detector has now launched inside it.
HOMER vs Wowza: editorial side-by-side
HOMER
5.0MEETINGS
HOMER 11's DuckLake rearchitecture is in its hardening phase, shipping near-daily.
◆ Current state
HOMER is releasing at near-daily cadence — twelve tags across 11.0.304 to 11.0.315 in nine days. The work concentrates on the DuckDB/DuckLake storage layer that HOMER 11 is built on: sanitizing bad RTPengine HEP timestamps that were creating future date partitions, stopping false-positive forbidden-keyword matches on Call-IDs, reconnecting DuckDB on catalog refresh. Two security advisories closed in the same window — a self-service admin escalation via PATCH /api/v4/users/:id, and an under-authenticated node /query endpoint that also exposed DuckDB external scanners. Separately, the search UI learned to treat HEP node name as an identity distinct from the numeric capture ID.
◆ Where it's heading
Nearly every entry here repairs something the new coordinator-and-storage-node design exposed rather than adding surface — which is the signature of a rearchitecture being shaken out in production rather than a feature push. 11.0.315 is the first release in this window that optimizes instead of repairs: the coordinator now caches each node's {min_ts,max_ts} from a stats endpoint and skips nodes whose range cannot overlap the query window. The security fixes cluster on the same young components, the node /query path and the raw-SQL validator.
◆ Prediction
Expect smart routing to move from opt-in toward default once the historical pcap and replay-ingest caveat is resolved, and the raw-SQL validator to keep absorbing fixes as more DuckDB surface gets exposed through it.
Wowza
6.3MEETINGS
Wowza is turning its media server into an inference layer, and NVIDIA just shipped a model into it.
◆ Current state
Nearly every recent post orbits one thing: the Wowza Video Intelligence Framework, an intelligence layer for Streaming Engine that pulls frames out of live streams, routes them to AI models, and converts inference results into metadata, overlays, alerts and logs. The framework supports customer-trained custom models, and the pitch is explicitly architectural — analysis running on the same media server that ingests and delivers the video, rather than in a separate downstream system. NVIDIA's Synthetic Video Detector has now launched inside it.
◆ Where it's heading
Wowza is repositioning away from streaming delivery toward live video as an operational data source, and the target customers are the ones named repeatedly: utilities with substation cameras, cities with traffic feeds, hospital campuses, stadiums. The recurring argument is that most live video is never watched because it cannot be, so the value is in detection rather than viewing. Content authenticity is emerging as the second thread — verifying what is real is framed as an operational problem for anyone ingesting video from many sources, which is the gap the NVIDIA detector fills. Earlier WebRTC and captioning posts show the delivery-layer work continuing underneath.
◆ Prediction
Expect the framework's model catalog to grow through more partnerships on the NVIDIA pattern, with detection categories aimed at the infrastructure and public-safety deployments the content keeps describing.
Alternatives to HOMER and Wowza
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 Wowza.
mediasoup
mediasoup's Rust line is shipping subchannel fixes every few days and nothing else
Daily.co
One real release is buried in a feed that is mostly captured page furniture.
Fourwaves
A daily drip of conference-platform polish, with finance filtering and attendee self-service leading.
CasparCG Server
Broadcast playout server reaches for HDR and sets a hardware floor to get there
FreeSWITCH
With the legacy purge done, FreeSWITCH spent 1.11.2 bounds-checking everything that parses bytes
Recent activity from HOMER and Wowza
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoHOMERCoordinator skips storage nodes outside the query time range
- 3d agoHOMERSecurity: node /query auth hardened, DuckDB scanners blocked
- 5d agoHOMERNode Name search and column, plus Prometheus label alignment
- 5d agoHOMERNode reconnects DuckDB on catalog refresh
- 5d agoWowzaHow NVIDIA And Wowza Are Detecting Synthetic Video In Live Streams ⚡
- 5d agoHOMERSecurity: blocks privilege escalation to admin via user PATCH
- 5d agoHOMERCall flow consolidates by Capture ID; MCP parser metrics
- 12d agoWowzaHow Different Models Can Transform The Same Video Feed
- 14d agoWowzaHow Does Wowza Video Intelligence Framework Support Real-Time Detection At The Streaming Layer?
- 19d agoWowzaHow Can Wowza VIF Turn Live Video Into Real-Time Operational Signals?
- 21d agoWowzaVideo Intelligence Belongs In The Pipeline, Not Bolted Onto It
- 25d agoWowzaContent Authenticity And Moderation In The Age Of AI Video
Frequently asked questions
What is the difference between HOMER and Wowza?
They serve adjacent needs but don't currently overlap on shipped themes. Wowza 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.
Is HOMER better than Wowza?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Wowza 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.
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.
What are the best alternatives to Wowza?
Top Wowza alternatives in Meetings are ranked by recent ship velocity. Browse the "Wowza alternatives" section above for the current picks, or visit /alternatives/wowza for the full list with editorial commentary on each.