FreeSWITCH
With the legacy purge done, FreeSWITCH spent 1.11.2 bounds-checking everything that parses bytes
A side-by-side editorial comparison of Wowza and HOMER — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Three security advisories in three days as HOMER locks down the query layer it just opened up.
HOMER ships multiple patch releases per day against a single 11.0.x line, and the work is overwhelmingly corrective rather than additive. Two long-running threads dominate: unifying HEP capture identity (node_id, node_name, "Capture ID") across the results table, filters and Prometheus labels, and keeping DuckDB/DuckLake storage honest. In the first week of August a third thread took over — three separate GHSA advisories closed in 11.0.309, and 11.0.313.
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.
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.
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.
HOMER ships multiple patch releases per day against a single 11.0.x line, and the work is overwhelmingly corrective rather than additive. Two long-running threads dominate: unifying HEP capture identity (node_id, node_name, "Capture ID") across the results table, filters and Prometheus labels, and keeping DuckDB/DuckLake storage honest. In the first week of August a third thread took over — three separate GHSA advisories closed in 11.0.309, and 11.0.313.
The security run is not incidental: each advisory lands on surface area the project recently added. The node query endpoint and DuckDB's external scanners are exactly the pieces that make HOMER queryable beyond its own UI, and they are now being fenced with token auth and a stricter SQL validator. Expect the identity-unification work to keep filling patch releases while the query layer hardens around it, since both are prerequisites for anyone building on captured data rather than just reading it.
The next releases likely continue tightening ValidateRawSQL and the node auth path, since two of the three August advisories came from that one surface. Whether the MCP natural-language parser seen in 11.0.308 grows past instrumentation is not yet visible in these entries.
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 Wowza or HOMER.
With the legacy purge done, FreeSWITCH spent 1.11.2 bounds-checking everything that parses bytes
Switcher Studio's tracked feed is search-driven streaming education, not product news.
Four parallel branches, one fix set — Asterisk's changelog is a backport ledger, not a feature list.
3CX is bolting AI onto the PBX and rewriting its licensing to match
CallHippo is arguing that compliance, not features, is what sells business calling.
A UCaaS marketing blog split between buyer education and channel-partner enablement.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
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.
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.
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.
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.