Wowza vs Digital Samba

This source is the Wowza blog, not a changelog: the recent window is explainers, thought-leadership essays, and customer stories, with no dated release notes in the top entries. The one genuine release visible anywhere in the feed — Streaming Engine 4.11, which adds WHIP and WHEP signaling, full ICE connectivity checks, and configurable STUN and TURN servers — sits several entries down and is echoed second-hand in the use-case posts above it. Everything more recent is about the Video Intelligence Framework, described as a layer that pulls frames off live streams, runs them through AI models, and emits metadata, overlays, and alerts.

Wowza is repositioning from a streaming server toward an inference pipeline for video nobody watches — substation cameras, traffic feeds, campus security. The essay cadence around VIF, custom model training, and content authenticity is the argument being built before the products arrive, aimed at operational buyers rather than broadcasters. The underlying engineering thread is more conventional: modernizing WebRTC in Streaming Engine so sub-second delivery works from standard browsers without an SDK. Because this feed tracks publishing rather than shipping, the velocity score here reflects blog cadence, not product activity.

The concentration of VIF material points to packaging or pricing news for the framework, but this source will only show it as another blog post. The useful fix is on our side: point the crawler at the Wowza release notes so Streaming Engine versions stop arriving as marketing echoes.