Stream Bridge Stream Bridge

Remote production video transport

Stream Bridge moves cameras, programme feeds, multiviews and graphics between remote teams through one platform - browser viewers and receiving production devices can both work from the same live source.

Join Beta
Signal Flow

4 Simple Steps

  1. Pick your sources

    Cameras, mixers, graphics, multiview or programme, with production audio.

  2. Pair both ends

    Install Stream Bridge at each site and pair each device with its connection key.

  3. Bridge the stream

    Pick the source and bridge it to the receiving device. No ports, VPN or network admin.

  4. Watch or output

    Browser viewers for the team, NDI, OMT or SDI outputs for the production.

How it works

A single live source can be watched by people in browsers, delivered into another production system, or both at once, rather than needing a separate tool for each destination.

Each destination stays independently controlled. Viewer links carry their own access, branding and audio, while device bridges publish named NDI or OMT sources and can route to compatible SDI hardware.

The public internet connection is handled without a shared VPN or forwarded ports. We prefer a direct connection, with cloud relay available automatically when network topology gets in the way.

Live telemetry, bitrate control, jitter handling, keyframe recovery and bridge reconnection all help the transport stay usable on real-world networks, without asking every remote endpoint to reconfigure.

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.

Join Beta View Documentation

Devices

Studio A

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

Technical Breakdown

How this workflow handles capture, sound, processing, latency, connectivity, and secure sharing.

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 typical picks.

Keep the source running before starting the stream. Newly connected devices can take around 30 seconds to finish discovery, especially with a lot of sources on the 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.

Additional audio sources can carry commentary, a clean feed, programme sound or a submix alongside the picture. Two-way and group communication are only enabled on the links that need them.

Performance

NVENC where available, CPU as the fallback.

Explore details

Encoding can run on NVIDIA NVENC or the CPU. NVENC generally gives the lowest latency and CPU use; CPU mode is useful on systems without compatible hardware or where GPU capacity is already committed.

The dashboard enforces separate GPU and CPU session caps, four and two by default. Actual capacity depends on the source format, viewer load, hardware and whatever else is running on the machine.

Viewer Quality & Latency

Live bitrate control, typically under 500ms.

Explore details

Plan upload bandwidth for every viewer and bridge route, and use wired connections wherever a feed is production-critical. Every browser viewer and receiving-device bridge is its own connection - plan sender upload for the bitrate multiplied by the number of simultaneous routes.

Choose bitrate based on the content and the whole route, not just the source resolution. Start conservative, watch the connection stats, and adjust live if detail or stability isn't there.

Networking

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

Explore details

The sending site and viewer don't need to join one VPN. Stream Bridge introduces the two endpoints and prefers a peer-to-peer connection across their existing internet.

When a peer-to-peer route isn't available, time-limited relay access kicks in automatically. You don't need to reconfigure the stream, but allow for the relay's extra distance and bandwidth.

Security & Customisation

Separate, controllable links per audience.

Explore details

Access and presentation are set at link level, so a polished client player and a technical operator view can share a source without sharing controls or branding.

Use separate, revocable links for different audiences, and remove links or bridge routes once a production no longer needs them.

Remote production video transport

Frequently Asked Questions

Answers about connection requirements, picture quality, production audio, network planning, and recovery.

Workflow setup

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

Yes. The receiving device can publish a named NDI or OMT source, and where compatible Blackmagic hardware and Card Output are enabled, it can also be assigned to selected SDI ports.

On a strong direct path with NVENC, it can feel close to local. CPU encoding, Wi-Fi, congestion, long distances and relay can all add delay, so test the real route in advance.

Monitoring & delivery

A 5Mbps stream watched by two people and bridged to one device works out at roughly 15Mbps of source upload before overhead. Stable capacity matters more than a one-off speed test.

Programme audio can travel with the source, with up to 16 channels available where the source supports it. Additional audio and return communication are set per viewer link.

The route is negotiated automatically, with TURN as a fallback for difficult NAT or firewall conditions. Bridge state is retained, so a temporary outage doesn't mean rebuilding the route.

Related workflows

Custom branded viewer links for clients Enterprise remote production infrastructure Group talkback for remote production teams Multi-site live production streaming