Supported Sources
OMT programme, multiview, camera and graphics sources on the paired device.
Stream Bridge lets anyone view an OMT source in their web browser without joining the production network - just a link that opens in Chrome, Firefox, Edge or Safari, with production audio and controlled access built in.
Programme, cameras, multiview or graphics from your local OMT 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.
OMT discovery and capture stay on the paired production device - the person watching doesn't need any of that. Pick the source, create a stream, and share a link that opens straight into a browser player.
The same stream can have multiple viewer links for different roles. Each one can carry its own URL, password, branding, controls and audio without touching the underlying OMT source.
The viewer doesn't need access to the OMT LAN, a VPN or a forwarded port. We negotiate a direct connection and use our cloud network automatically when the endpoints can't connect directly.
You stay in control after the link goes out - viewer counts, connection information, device performance and live bitrate changes are all in the dashboard, while the person watching just sees the player.
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.
A closer look at OMT discovery, browser playback, production audio, latency, connection routes and link-level control.
OMT programme, multiview, camera and graphics sources on the paired device.
Up to 16 channels, plus optional return communication.
Real-time H.264 encoding through NVENC or CPU.
Low-latency playback in Chrome, Firefox, Edge and Safari.
Direct connection first, cloud relay as a fallback.
Custom links, passwords, branding and controls per viewer.
Practical answers about receivers, browser support, latency, audio, bandwidth and viewer access.
No. Only the paired device needs access to the OMT source - remote viewers just open the assigned link in a supported browser.
Chrome, Firefox, Edge and Safari. Chrome's the most reliable for WebRTC, especially where advanced audio features are in use.
Latency's usually in the hundreds of milliseconds rather than seconds. The final figure depends on encoding, browser buffering, network conditions and whether relay's required.
Yes. Viewer links can include source channels and additional audio feeds, with independent browser controls.
Each viewer is a separate connection - as a planning example, two viewers on a 5Mbps stream need roughly 10Mbps of sender upload before overhead.
Yes. Separate links can carry different URLs, passwords, branding, controls and communication options while using the same underlying OMT stream.