Stream Bridge Stream Bridge

Remote client video monitoring

Stream Bridge gives clients a private, polished view of the production without pulling them into the control room. Pick your source, share a branded browser link with a password if you need one, and let them watch at the quality and audio mix that's right for them.

Signal Flow

4 Simple Steps

  1. Pick the feed

    Programme, clean feed, cameras or graphics: whatever the client should see.

  2. Pair the app

    Install Stream Bridge, add a device on the dashboard and enter its connection key.

  3. Share a link

    Send a viewer link, password optional. No port forwarding or network admin needed.

  4. They watch live

    Open it in Chrome, Firefox, Edge or Safari. Direct where possible, via our cloud when not.

How it works

Client viewing works like any other Stream Bridge output. Pair a device, select the NDI, OMT, desktop or DeckLink source you want the client to see, and create a stream from the dashboard.

Different people can get different links from the same stream - branding, custom URL, password, controls and audio are all set per link, so you're not stuck with one generic experience for everyone.

The viewer connects through their browser with no receiver app, VPN or port forwarding needed. We try a direct connection first and use our cloud network automatically if the client's network is more restrictive.

Connection stats and the live viewer count stay visible to you the whole time, and you can adjust bitrate while it's running to balance quality against the client's actual connection.

Get Started Quickly

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.

Devices

Studio A

Online
Sources 5 sources
Last Seen 18 January 2026 | 10:21 AM
CPU 21%
GPU 20%
Under the hood

Technical Breakdown

A closer look at source handling, production audio, encoding performance, delivery quality, networking, and access control.

Supported Sources

NDI, OMT, desktop or DeckLink sources on a paired device.

Explore details

Stream Bridge works with an NDI, OMT, desktop or DeckLink/SDI source available to a paired device - programme outputs, multiviews, camera feeds, clean feeds and graphics returns are all typical picks for a client link.

Discovery is controlled per device, so you can turn off input families you don't use, or restrict results to local sources on a busy network.

Audio

Programme audio travels with the source; add extra tracks as needed.

Explore details

Programme audio can travel with the source, and up to 16 channels are available where the source supports it. Additional tracks and return communication can be configured separately.

Different audiences don't need the same audio. Configure extra tracks and communication tools at the viewer-link level to suit each role.

Performance

NVENC where available, CPU as the fallback.

Explore details

NVENC on a supported NVIDIA GPU keeps encoding latency and CPU use low - the recommended route. CPU encoding is the fallback when there's no compatible GPU, or it's already committed elsewhere.

Live telemetry makes encoder headroom visible. If load's getting close to the top or frames start dropping, cut back on concurrent work or move the encode to better hardware.

Viewer Quality & Latency

Live bitrate control, typically under 500ms.

Explore details

Password and player changes apply at link level, so one production stream can serve different client groups. Every viewer is a separate connection, and the configured bitrate applies to each one - two viewers at 5Mbps needs roughly 10Mbps upload.

A static presentation and a fast sports camera put very different demands on the encoder, so tune bitrate live while watching device and viewer behaviour.

Networking

Direct connection first, cloud relay when that's blocked.

Explore details

There's no manual IP exchange or router forwarding required. Each session negotiates its own route automatically.

Corporate and venue networks sometimes block a direct connection. When that happens, Stream Bridge falls back to relay, and you can drop the bitrate if the longer route has less headroom.

Security & Customisation

Custom links, passwords and branding per audience.

Explore details

Custom URLs, passwords, colours, logos and controls let you match the viewer experience to its audience. Up to 25 viewer links can be created per stream.

Security isn't just about the connection - keep your dashboard account protected, keep pairing keys private, password anything sensitive, and don't reuse access beyond the event it was made for.

Remote client video monitoring

Frequently Asked Questions

Practical answers about setup, delivery, quality, audio, bandwidth, and reliability for this Stream Bridge workflow.

Workflow setup

Any NDI, OMT, desktop or DeckLink source available to a paired device. Make sure the relevant source type is enabled and the source is available, then create a stream and pick a viewer or Bridge Sharing destination.

Just a browser - Chrome, Firefox, Edge or Safari. Chrome's the most reliable for WebRTC, and nothing needs installing at their end.

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.

Monitoring & delivery

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. Programme audio can travel with the source, and up to 16 channels are available where the source supports it. Additional audio and return communication are set per viewer link.

Yes, 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.

Related workflows