Stream Bridge Stream Bridge

Low-latency NDI over the internet

Stream Bridge combines NVENC encoding, a direct-first connection, managed buffering and automatic recovery to move NDI between sites with latency that can stay under 500ms.

Signal Flow

4 Simple Steps

  1. Pick an NDI source

    Live cameras, programme feeds or multiviews from your local NDI network.

  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. Switch it remotely

    A low-latency NDI source at the far end, ready to switch, monitor or record.

How it works

Low latency comes from the whole path, not one setting - Stream Bridge is built to cut delay at capture, encoding, connection and playback so a remote feed stays useful for directing, monitoring and live production.

Supported NVIDIA hardware uses NVENC to keep encoder delay and CPU impact low. You can tune bitrate live and watch device load, viewer state and connection information from the dashboard without rebuilding the route.

We always try to send media directly between the paired devices first. Where that's blocked, Stream Bridge uses cloud relay automatically - a small trade of extra delay for reliable reachability.

Jitter handling, packet-loss recovery, fresh keyframe requests and bridge reconnection all run continuously through the session. In ideal conditions latency can be as low as 50ms, though we advertise around 500ms to allow for realistic internet buffering.

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

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

Supported Sources

Full-bandwidth NDI and NDI HX sources on the paired device.

Explore details

Stream Bridge works with full-bandwidth NDI and NDI HX sources the paired device can see - cameras, vMix, OBS, PTZ cameras, graphics systems and other NDI sources.

Keep the source running before starting the stream. Newly connected devices can take around 30 seconds to finish discovery on a busy network.

Audio

Up to 16 channels, individually controllable.

Explore details

Stream Bridge can capture up to 16 audio channels from a single NDI source, delivered as individually controllable programme tracks.

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 - the best fit alongside live production software. CPU encoding is the fallback where there's no compatible hardware.

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

Viewer Quality & Latency

Live bitrate control, typically under 500ms.

Explore details

Actual delay depends on encoding choice, distance, congestion, and whether the route needs TURN relay. 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.

Low-latency NDI over the internet

Frequently Asked Questions

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

Routing & setup

A paired desktop device with NDI discovery switched on and the source actively transmitting on a reachable network. Create a stream, then pick a viewer or Bridge Sharing destination.

Either. 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, the feed 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.

Bandwidth & reliability

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.

Up to 16 channels come through, individually controllable. Additional audio sources can be exposed separately, and return communication is 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