Adobe Connect vs Wowza

Wowza Streaming Engine 4.11 is the one concrete release in an otherwise blog-heavy feed: it adds standards-based WHIP and WHEP signaling, full ICE candidate generation and connectivity checks, and configurable STUN/TURN for NAT traversal. The rest of the recent entries are use-case articles and stream-security explainers rather than product changes. The throughline is sub-second WebRTC delivery with broader encoder and browser interop, no custom SDK required.

The release direction points at production-grade, standards-compliant WebRTC as a first-class ingest and playback path alongside HLS, plus a more cloud-native deployment model. Surrounding content leans on edge deployments, manifest and token stream security, and capacity planning, aiming the self-managed engine at low-latency, security-sensitive verticals like transport ops, public TV, and remote sites. Note that this feed crawls the Wowza blog, so most entries read as positioning rather than shipped changes.

Expect follow-on 4.11.x hardening of the WHIP/WHEP path and more STUN/TURN configurability; the recurring security explainers suggest token-auth and m3u8 manifest protection are the next likely product surface.