WAVE fabrics

Every transport and protocol WAVE speaks — each a first-class peer with the same complete support: one key, one scope grant, one metering rate ($0.005/min), and a combined API reference. The point of WAVE is that no fabric is half-wired.

Direct vs. bridged reach. WAVE owns no transport — it is the conversion layer above all of them — so a fabric is classified by how it reaches the WAN. Direct fabrics (SRT, MoQ, RIST, OMT; NDI too) are WAN-reachable: an encoder hits a hosted edge directly. Bridged fabrics are host-local (MXL) or LAN-multicast (Dante, AES67, ST 2110): a WAVE node on the source converts them to a WAN transport you choose (MoQ / SRT / RIST), ships them, and a far-side node converts them back — re-emitting native multicast on the destination LAN for on-prem consoles and playout. So even a LAN-only fabric becomes something you can ingest, distribute, and integrate across on-prem, cloud, and multi-cloud — in both directions.

Network ingest

WAN-reachable (reach: direct) — an encoder/publisher hits a hosted *.wave.online edge worker directly. Also the bridge TARGETS that LAN fabrics convert to.

Host-local

Shared-memory / IPC on a single host (reach: bridged) — a WAVE node reads the host buffer and converts it to a WAN transport; no raw hosted spoke.

LAN multicast

Real-time media on a local network (reach: bridged) — a WAVE node ingests the multicast, converts it to a WAN transport, and a far-side node re-emits it as native multicast on the distribution LAN.