Wowza Streaming Engine 4.11 Updates WebRTC for Production-Scale, Cloud-Native Streaming

What’s New In Wowza Streaming Engine 4.11?

Wowza Streaming Engine 4.11 upgrades its WebRTC implementation across ingest, signaling, and network traversal. The release adds WHIP and WHEP support, full ICE candidate generation and connectivity checks, and configurable STUN and TURN servers. Teams gain broader encoder and browser interoperability along with a deployment model that fits cloud-native architectures.

WebRTC has moved well past its origins as a browser-based video chat technology. It now powers low-latency live events, real-time surveillance feeds, AI-driven video pipelines, and interactive streaming applications across nearly every industry Wowza serves. Today, we are pleased to announce Wowza Streaming Engine 4.11 ships a reimplemented WebRTC stack engineered for that production reality. This brings the platform in line with current W3C and IETF specifications, adding the signaling and network traversal capabilities modern deployments require.

What WebRTC Improvements Are In Wowza Streaming Engine 4.11?

Wowza Streaming Engine 4.11 delivers four headline changes to the WebRTC stack:

• Reimplemented WebRTC engine: An upgraded stack aligned with current W3C and IETF specifications, removing the dependency on proprietary client libraries for connection.
• WHIP and WHEP support: Standardized HTTP-based signaling for WebRTC ingest (WHIP) and playback (WHEP), opening WSE to a growing ecosystem of compatible encoders and players.
• Full ICE candidate generation and connectivity checks: Complete Interactive Connectivity Establishment support that raises the rate of successful peer-to-server connections across NATs, firewalls, and corporate networks.
• Configurable STUN and TURN servers: Custom network traversal infrastructure that meets the requirements of enterprise, government, and air-gapped deployments.

Improved Encoder and Browser Interoperability

The 4.11 update’s reimplemented WebRTC stack expands what can be done with Wowza Streaming Engine out of the box. WHIP support means standards-compliant encoders can publish directly to WSE without custom integration work. That includes OBS Studio, FFmpeg, and hardware from vendors such as Osprey, Teradek, AJA, and Haivision encoders. Onboarding a new encoder no longer requires a Wowza-specific SDK or bespoke signaling code.

On the playback side, WHEP gives viewers a standards-based path to sub-second latency through any compatible player. Browser-based WebRTC clients connect using the same offer/answer flow defined in the W3C specification. This keeps client code simpler and reduces the maintenance burden as Chrome, Safari, Firefox, and Edge update their WebRTC implementations.

For development and operations teams, expect less custom code to write and maintain, faster encoder onboarding, and a smaller surface area to monitor as the broader WebRTC ecosystem evolves. In short, connecting browsers and encoders via WebRTC is easier and less error-prone in Wowza Streaming Engine.

Reliable Connectivity Across Real-World Networks

Full ICE candidate generation and connectivity checks solve one of the most common sources of failure in real-world WebRTC deployments (getting two endpoints to find a working network path). Wowza Streaming Engine 4.11 gathers the complete set of host, server-reflexive, and relay candidates, then systematically validates connectivity. The result is a higher success rate for direct connections, especially in environments where reliability matters most. That includes enterprise networks, hospital systems, and government facilities.

Configurable STUN and TURN support gives teams full control over the network traversal layer. Operators can point Wowza Streaming Engine at their own STUN and TURN infrastructure when public servers will not suffice, whether the reason is data sovereignty, security policy, or operating in an air-gapped environment. Pre-configured public STUN servers ship as a default, so smaller deployments and proofs of concept work immediately without additional setup.

For Wowza customers running mission-critical workloads in restrictive networks, this configurability makes WebRTC a deployment-ready ingest and playback path that holds up under enterprise IT requirements.

A Flexible Deployment Model

Modern Wowza Streaming Engine deployments increasingly run in Docker and Kubernetes alongside the rest of an organization’s services. The HTTP-based signaling in WHIP and WHEP fits that pattern without exception. Signaling traffic looks like any other HTTP API call. That means it routes through the same load balancers, ingress controllers, API gateways, and observability tools the rest of the stack already uses. The new signaling model does not require sticky sessions or WebSocket-aware routing.

Horizontal scaling becomes more straightforward as a result. WHIP and WHEP endpoints distribute cleanly across multiple containers or pods without connection affinity concerns. This matches the disposable nature of containerized workloads. WebSocket signaling remains available for interactive use cases that benefit from a persistent channel. Teams running mixed workflows can choose the right approach for their use case.

WebRTC Use Cases Among Wowza Customers

Across live events, surveillance, and countless other use cases, Wowza Streaming Engine 4.11 strengthens WebRTC for the streaming workflows Wowza customers run every day.

Surveillance and monitoring operators gain a reliable low-latency option for publishing browser-based and WebRTC-capable feeds into control rooms, command centers, and analytics platforms. Expanded STUN and TURN configuration enables video surveillance deployments that often live behind restrictive firewalls or inside isolated networks.

Live event broadcasters can ingest sub-second WebRTC contribution from OBS Studio or hardware encoders over WHIP, then fan that single ingest out to HLS, LL-HLS, DASH, RTMP, and SRT for large audience delivery. One ingest path, many delivery paths, all from the same media server. Production teams supporting events and entertainment workflows gain a path to real-time contribution without integrating a proprietary client stack.

AI and video intelligence pipelines built on Wowza inherit a hardened, standards-aligned WebRTC ingest path. This path feeds the same processing infrastructure already powering object detection, event logging, and video intelligence workflows.

Cloud and platform teams running Wowza Streaming Engine in Kubernetes get a WebRTC implementation that follows the same architectural conventions. This removes a long-standing source of friction for cloud-native deployments.

The Wowza Streaming Engine Foundational Advantage

Wowza Streaming Engine 4.11 ships alongside the security patches and stability improvements customers expect with every Wowza release. The full WebRTC modernization applies across every supported deployment model, including bare metal, virtual machines, Docker, Kubernetes, on-premises, hybrid, public cloud, and edge environments. There is no special case to manage and no separate package to install.

This release builds on the trajectory established with Wowza Streaming Engine 4.9.7. Each release deepens the operational backbone behind video intelligence, automation, and real-time delivery, giving teams infrastructure that grows with their workflows rather than constraining them.

Get Started With Wowza Streaming Engine 4.11

For a complete breakdown of changes, configuration steps, or to get a more detailed walkthrough of what’s new, talk to a Wowza streaming expert and see how WebRTC, WHIP/WHEP, and configurable network traversal fit into a specific workflow. You can view the full release notes here. For customers looking to update to the newest release, here is how to update your Wowza Streaming Engine installation.

Frequently Asked Questions

What is new in Wowza Streaming Engine 4.11?

Wowza Streaming Engine 4.11 upgrades the platform’s WebRTC implementation. The release updates the WebRTC stack to align with current W3C and IETF specifications, adds WHIP and WHEP support for standards-based ingest and playback signaling, introduces full ICE candidate generation and connectivity checks, and adds configurable STUN and TURN server support.

Does Wowza Streaming Engine 4.11 support WHIP and WHEP?

Yes, Wowza Streaming Engine 4.11 adds native support for both WebRTC-HTTP Ingestion Protocol (WHIP) for publishing and WebRTC-HTTP Egress Protocol (WHEP) for playback. Standards-compliant encoders such as OBS Studio, FFmpeg, and hardware from vendors including Osprey, Teradek, AJA, and Haivision can publish directly to WSE over WHIP without custom client code.

Can Wowza Streaming Engine 4.11 use custom STUN and TURN servers?

Yes, Wowza Streaming Engine 4.11 supports configurable STUN and TURN endpoints, including private deployments inside enterprise networks, government facilities, healthcare environments, and air-gapped infrastructure. Pre-configured public STUN servers ship as the default for immediate out-of-the-box functionality.

Does the new WebRTC stack work with standard browsers without a custom SDK?

Yes. Because Wowza Streaming Engine 4.11 follows W3C and IETF WebRTC specifications, any standards-compliant browser or native client can connect directly. The release does not require a Wowza-specific JavaScript SDK or proprietary client library for signaling.

Does Wowza Streaming Engine 4.11 still support WebSocket-based WebRTC signaling?

Yes. WebSocket signaling is still available for interactive and bidirectional WebRTC workflows that benefit from a persistent connection. Wowza Streaming Engine 4.11 supports WHIP and WHEP alongside WebSocket signaling, so broadcast-style and interactive use cases can each choose the most appropriate method.

Is Wowza Streaming Engine 4.11 compatible with Docker and Kubernetes deployments?

Yes. The HTTP-based signaling model used by WHIP and WHEP integrates naturally with containerized infrastructure, including Kubernetes ingress controllers, service meshes, and standard load balancers. Wowza Streaming Engine 4.11 runs across bare metal, VMs, Docker, Kubernetes, on-premises, hybrid, cloud, and edge environments.

Where can teams download Wowza Streaming Engine 4.11?

Existing customers can update to the newest version of Wowza Streaming Engine 4.11 by following the instructions here. Teams new to the platform can request a free trial or contact a Wowza streaming expert for a one-on-one demonstration.