Your Dante network just left the building
Dante audio has stayed on the LAN for twenty years. WAVE bridges a live Dante or AES67 source to a URL that plays in any browser, with nothing to install on the listening end. It is live at listen.wave.online.
A live Dante or AES67 source on your network can be a URL. Open listen.wave.online in any browser and you are hearing a real Dante feed, bridged through WAVE, with nothing installed on the listening end. That is the whole announcement. The rest of this post is what changed and how to use it.
What shipped
For twenty years professional audio has run on Dante: stadiums, houses of worship, broadcast trucks, theaters, corporate AV. The protocol is excellent at what it was built for, moving uncompressed audio across a rack room with low latency and automatic discovery. It was never built to reach a phone in the parking lot or a producer three states away. Getting it out of the building meant licensed hardware, a VPN, or a vendor's event-gated cloud.
WAVE puts a bridge at the edge of the LAN. It discovers Dante and AES67 sources the way any Dante-aware device does, by listening for them on the network. Discovery follows the announcements Dante devices already make, so nothing new is installed on the console or the switch. The bridge takes the audio off the closed plane and onto WAVE's transport. The output is a URL. A browser opens it and plays, live.
AES67 is the open interoperability standard for audio over IP, and most current Dante devices can publish an AES67 stream alongside their native one. The bridge accepts either. If your console speaks one of the two, the bridge sees it.
Three things do not change. Your Dante license is yours; WAVE does not resell it or sit between you and the Dante ecosystem. Your controller stays your controller; the engineer who owns the console keeps routing exactly as before, upstream, on the LAN. And Dante stays audio; WAVE's video path is separate infrastructure, not a Dante feature.
What WAVE meters is the reach: the flow from the bridge to each listener. Not the license underneath.
The bridge is not a separate product with its own login. Dante and AES67 are two adapters on the WAVE Media Engine, next to SRT, MoQ, WebRTC, and HLS, and they reach the same gateway every other capability does. Auth, metering, and identity are handled once there. A person with a key and an agent paying over x402 reach the bridge on the same route, so a venue's feed can be consumed by an operator in a browser today and by an automated monitoring agent tomorrow without a second integration.
What it means
A broadcast engineer stops asking IT to open a VPN tunnel so a remote producer can hear program. A house of worship stops racking a hardware box whose one job is streaming the sermon feed. A stadium operations team stops treating "get this feed to someone offsite" as a project with a purchase order. The feed is a link, and a link can be sent to anyone.
On the listening end there is nothing to buy. No controller license, no virtual soundcard license, no plugin, no app. A producer on a laptop in another city opens the link the way they open any web page.
The latency is what a live audio transport gives you, not a buffered file. Latency figures for the public stream are not published; open it next to the room and compare.
How to use it
Hear the live bridge first:
https://listen.wave.online
Then read the transport docs at docs.wave.online for how the Dante and AES67 adapters sit on the Media Engine next to SRT, MoQ, WebRTC, and HLS, each with its live, building, or planned label. To put your own source on the bridge, start there; the adapters carry their status label where they are listed.