Supported Sources
Full-bandwidth NDI and NDI HX sources on the paired device.
Stream Bridge turns cameras, programme feeds, multiviews and graphics into high-quality browser viewers - low latency, controlled access, production audio, and no NDI Tools needed at the viewing end.
Programme, multiview, cameras, graphics or a clean feed from your NDI network.
Install Stream Bridge, add a device on the dashboard and enter its connection key.
Send a viewer link, password optional. No port forwarding or network admin needed.
Open it in Chrome, Firefox, Edge or Safari. Direct where possible, via our cloud when not.
Stream Bridge keeps NDI capture beside the source and gives each remote person a dedicated browser player for exactly the feed they need - install the desktop app, pair a device, and any NDI sources it can see are ready to stream.
One NDI stream can support different audiences through separate links. A director can get multichannel audio and communication controls, while a client gets a branded, password-protected player with a simpler set of controls.
Every viewer gets an individual connection. We prefer a direct route and use our cloud network when restrictive NAT or firewall policy stops the browser and production device connecting directly.
Live bitrate control, per-viewer connection information, device telemetry and background recovery all help protect the monitor throughout a production, while viewers just see the picture.
To get started straight away, join our beta, download the application, and get streaming. We also have a host of documentation available that goes through all of the features of Stream Bridge, troubleshooting issues, and our support team are ready to help if needed.
Technical detail on the source, audio path, encoding load, picture quality, internet route, and viewer controls.
Full-bandwidth NDI and NDI HX sources on the paired device.
Up to 16 channels, individually controllable.
NVENC where available, CPU as the fallback.
Live bitrate control, typically under 500ms.
Direct connection first, cloud relay when that's blocked.
Custom links, passwords and branding per audience.
What production teams need to know before configuring this source, route, and destination.
Any NDI or NDI HX source the paired device can see. Make sure NDI discovery is switched on in Device Settings and the source is actively transmitting, then create a stream and pick a viewer or Bridge Sharing destination.
They open the link in Chrome, Firefox, Edge or Safari - Chrome's the most reliable for WebRTC - and don't need anything installed.
Latency's usually in the hundreds of milliseconds rather than seconds, but no internet path is fixed - use wired connections and leave headroom where timing matters.
Set something both the sender and the weakest receiver can sustain. Many 1080p30 feeds start around 3-5Mbps, with higher-motion or 60fps content often needing more.
Yes, up to 16 channels come through, individually controllable. Additional audio sources can be exposed separately, and return communication is set per viewer link.
No, a direct route is preferred but not required. Relay access is supplied automatically when the endpoints can't reach each other, and the app works to recover any interrupted connection.