Wowza Streaming Engine: on-prem and self-hosted live deployments
Wowza Streaming Engine — the on-prem / self-hosted live-streaming product. License model, deployment patterns, hardware requirements, and where on-prem live makes sense.
Wowza Streaming Engine is the self-hosted variant of Wowza's product line. For operators with sovereign-cloud requirements, contribution-edge workloads, or scale economic constraints that rule out cloud-managed live, Streaming Engine is one of the few production-grade options. The trade-off is operational responsibility — you run the infrastructure.
What Wowza actually has
Streaming Engine ships as a Java-based application installable on Linux (Ubuntu, RHEL, Debian, Amazon Linux), Windows Server, or macOS Server. Per-instance licensing — typically $1,995-$4,995/year per Streaming Engine instance with annual support. Same protocol breadth as Streaming Cloud (RTMP/SRT/RTSP/WebRTC/MPEG-TS/HLS ingest + output). Configuration via XML files or web portal (portal is the primary path; XML is the underlying state). Multi-instance deployments for HA via Wowza's Load Balancing add-on. Wowza's Stream Targets handle rebroadcast to other destinations (CDN origins, RTMP push, additional servers). Hardware-accelerated encoding via NVIDIA NVENC or Intel Quick Sync depending on host.
Where it's the right fit
Sovereign-cloud and regulated workloads (defense, healthcare with PHI in video, financial services with audit-trail requirements) where the entire live pipeline must run in your perimeter. Edge ingest workloads where Streaming Engine runs at the broadcast contribution site (sports stadiums, event production locations) and replicates upstream. Cost-economic workloads at extreme scale (very-large 24/7 channel counts) where managed-service per-channel pricing is uneconomical.
Where the gaps show up
Operating Wowza Streaming Engine at production scale requires real SRE capacity — the cloud-managed variant abstracts complexity that Streaming Engine puts on your operational team. Annual licensing per-instance can be expensive for many-small-instance deployments (edge ingest patterns). Updates and version upgrades are operational responsibility — Wowza ships releases, you deploy them.
Pricing implications
Streaming Engine licensing: $1,995-$4,995/year per instance depending on edition (Standard, Enterprise). Plus support contracts, plus hardware costs. For large deployments, volume licensing exists but contract-driven. At 100-instance fleets, expect $300K-$500K/year in licensing alone.
MpegFlow self-hosted licensing is flat-fee per cluster (not per-instance) — different model entirely. For live-only deployments today, Wowza Streaming Engine is the established choice. When MpegFlow Live ships in 2026 Q3, the self-hosted licensing math becomes attractive for many-instance fleets where Wowza's per-instance model compounds. For mixed live + VOD workloads, MpegFlow's unified self-hosted product is one binary; Wowza requires Streaming Engine + their VOD product separately.
- Self-hosted
- wowza
- streaming-engine
- on-prem