Stream Bridge Stream Bridge

Remote producer feed over the internet

Stream Bridge gives a remote producer the picture, production audio and communication they need to stay part of the show, through one dedicated browser link.

Signal Flow

4 Simple Steps

  1. Pick the feed

    Programme, multiview, a clean feed or a camera for the producer to follow.

  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

Pair a device, select the programme, multiview, clean feed or camera you want the producer to see, and create a stream from the dashboard.

Programme audio, clean feeds, commentary and other sources can be offered with independent controls. Audio Return or Group Audio can be added when the producer also needs to talk to the control room or remote team.

The producer joins through a browser, no VPN or inbound port configuration needed. We choose a direct route whenever possible and use our cloud network automatically when the connection needs relay.

Separate producer and client links can point at the same stream while exposing different features, and viewer state, device load and live bitrate control all stay with the production team throughout the show.

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

What operators need to know about inputs, audio channels, device performance, bandwidth, routing, and 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 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

A supported NVIDIA GPU encodes through NVENC with barely any CPU impact - normally the best fit beside live production software. CPU encoding is the fallback when there's no compatible hardware, or it's 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

Separate producer and client links can point at the same stream while exposing different controls, audio, passwords and branding. Every viewer is a separate connection, and the configured bitrate applies to each one - two viewers at 5Mbps needs roughly 10Mbps upload.

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 producer feed over the internet

Frequently Asked Questions

Common questions from source discovery through to the receiving viewer or production device.

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.

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

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.

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