OMT already ditched the NDI toll. WAVE gives it a home.
OMT is open, royalty-free, studio-quality video over ordinary Ethernet — no per-device license, no vendor fence. WAVE puts that feed behind the same gateway, the same key, and the same fail-closed scope-gate as every other transport you run — one governed front door instead of one more stack to babysit.
Preview — the front door and gateway scope-gating are live today; the native off-LAN metered relay is not yet GA.
The toll is gone. The silo doesn't have to be next.
Broadcast engineers already know OMT freed them from NDI's per-device tax. But an open transport can still end up on its own island — its own credential, its own limits, separate from every other stream in the building. WAVE closes that gap: OMT calls carry the identical Authorization: Bearer <key> and fail-closed scopes (omt:read / omt:write) as Dante and NDI, on the same api.wave.online gateway.
1. Point it at WAVE
Your OMT source or receiver talks to omt.wave.online — the edge front door for the protocol.
2. One key, fail-closed
The WAVE gateway enforces omt:read on reads and omt:write on writes — every call, no exceptions.
3. Same rails as everything else
OMT joins Dante (audio) and NDI (video) on one gateway, one key, one metering model — not a bespoke integration per protocol.
What teams build on WAVE's rails
OMT is one transport on the rails — here's what the same governed gateway lets you build across every protocol WAVE fronts.
Route OMT the same way you already route Dante
One WAVE key, one gateway — the camera feed and the audio channel are governed the same way instead of living in two different vendor stacks.
Gear from different vendors, one governed key
OMT is open by design so different vendors' cameras and encoders already interop. WAVE gives that mixed floor a single front door instead of a per-device NDI license to reconcile.
One auth pattern, reused across every transport
Build against `Authorization: Bearer
Where this goes
A real duplex OMT adapter already speaks the protocol inside WAVE's transport engine — this is shipped code, not a roadmap slide. Next, the same gateway carries your OMT feed off the LAN to any authorized endpoint, metered exactly like every other WAVE transport — so escaping NDI's toll doesn't just save a license fee, it puts your video on the same governed, payable rail as everything else you run on WAVE.
The spec
request
│
▼ OMT front door — fail-closed at the gateway
POST / ─▶ {…}
│
└─ auth + scope + metering federate through api.wave.online
Federated — auth, entitlement, and metering run through api.wave.online; this spoke renders the front-door and forwards the rest.