// the find
OvenMediaLabs/OvenMediaEngine
OvenMediaEngine (OME) is a Sub-Second Latency Live Streaming Server with Large-Scale and High-Definition. #WebRTC #LLHLS
OvenMediaEngine is a C++ live streaming server built around sub-second latency via WebRTC and LLHLS. It handles the full pipeline: ingest (RTMP, SRT, WHIP, RTSP), transcode (ABR with hardware encoder support), and delivery. It's aimed at anyone who needs to self-host a Twitch-scale streaming stack without the licensing costs of Wowza or the opacity of a CDN.
The protocol coverage is genuinely wide — WHIP simulcast, SRT, E-RTMP, and WebRTC all as first-class ingest paths, not bolted-on afterthoughts. The embedded TURN server and WebRTC-over-TCP fallback means it actually works for viewers behind restrictive firewalls, which is the thing most WebRTC streaming projects get wrong. Origin-edge clustering is built in with its own OVT protocol rather than forcing you to put Nginx in front of everything. The admission webhook system for access control is well thought out — it's a clean HTTP callback rather than a custom auth plugin system.
It's Linux-only and the build system is a maze of custom Make targets plus CMake in parallel, which makes contributing or debugging build issues painful. The configuration is XML, which in 2026 is a real ergonomics hit — no env-var override story means container deployments need templated XML files. H.265 hardware-only is a real constraint: if your GPU goes sideways, you lose HEVC entirely with no software fallback. The REST API is versioned at v1 with no indication of stability guarantees, and the OpenAPI spec in api/ome.yml looks hand-maintained, which means it drifts.