Dante

Planned · LAN multicast fabric · reach: bridged · meters at $0.005/min. 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.

Dante is the most widely deployed pro-audio networking technology. Its reach is bridged, and dante.wave.online is the Dante WAN Bridge product (a node-fronted relay, not raw native ingest): a WAVE node on the Dante LAN ingests the audio multicast, converts it to MoQ, SRT, or RIST, and a far-side node re-emits Dante on the destination audio LAN so remote consoles see native channels. The meter and gateway wiring are live. The bridge is gated on three real dependencies: the bridge runtime (CF Containers), the native Dante adapter (Audinate SDK), and the R1 clock — cross-WAN PTP is not feasible, so cloud playout is wallclock/frame-accuracy. Until those ship, the hosted endpoint is a stub — do not treat it as live.

WAN-bridge endpoint: dante.wave.online — a node-fronted relay (not raw ingest), gated on the bridge runtime.

Reach: bridged (the WAN bridge)

WAVE owns no transport — it is the conversion layer — so even a lan multicast fabric becomes WAN-distributable. Dante is reached in two legs:

1. Ingest leg — a WAVE node on the source LAN joins the multicast group, stamps clock + integrity + metering, and converts the media to a WAN transport you choose: moq, srt, rist.
2. Egress leg — a far-side node receives the WAN stream and converts it back to native Dante, re-emitting it as local multicast on the destination LAN so on-prem devices see a native source.

The bridge target is operator-selectable per session (moq, srt, rist today; MoQ for general low-latency relay, SRT for ultra-low-latency point-to-point, RIST when the WAN is lossy or SMPTE-grade reliability is required). The conversion is a lossless envelope — not a transcode — so it stays cheap and high-margin.

Dante is PTP-disciplined for sample-accurate interop. Cross-WAN PTP is not feasible, so cloud playout is wallclock/frame-accuracy; for sample-accurate facility interop keep the egress node on-prem (node-to-node). The hosted bridge runtime is gated on CF Containers and (for some fabrics) a native adapter — see the phase above before treating the endpoint as live.

Install

Native adapter not built yet — runs through the WAVE node metering bridge today.

# Bridge a Dante channel to WAVE via a WAVE node (planned — endpoint is a stub today)
wave node bridge --in dante://Console-01:0 --out moq://moq.wave.online

Every fabric authenticates with the same WAVE key (Authorization: Bearer $WAVE_KEY) and is gated by the same scope grant. A call carrying x-wave-protocol: dante is attributed to this fabric end-to-end.

API reference

The WAVE gateway (api.wave.online) enforces auth, scope, entitlement, and metering for Dante — the same contract as every other fabric.

A subscription to the Dante product grants both dante:read and dante:write. Usage is reported as wall-clock minutes under the metering dimension duration_ms:dante, which bills the live Stripe meter wave_usage_duration_ms_dante once STRIPE_PRICE_STREAM_MIN_DANTE is provisioned. Read your own accumulated usage at GET /v1/usage (scope usage:read).

All fabric reference fields above are generated from the fabric-support contract (catalog/fabrics.json) and the pricing SSOT, so the docs can never drift from what the gateway actually enforces.

Pricing

Every transport fabric meters at the uniform $0.005/min anchor. Metering is wall-clock and mutually exclusive — a minute is billed under duration_ms:dante or the aggregate stream dimension, never both. Prices are inert until your subscription is attached; you are billed only for minutes the gateway observes.