Stream Bridge Stream Bridge

Send NDI over the internet

Stream Bridge moves NDI between locations without extending the LAN, opening ports or setting up a VPN. It carries the source over a low-latency internet connection and recreates it on a paired device as a named NDI or OMT source, ready for the receiving production.

Join Beta
Signal Flow

4 Simple Steps

  1. Pick an NDI source

    Any NDI or NDI HX source: cameras, vMix, OBS, PTZ, graphics or programme.

  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. Use it at the far end

    It appears on the receiving machine as a named NDI or OMT source, or on SDI.

How it works

The setup is the same as any Stream Bridge source. Install the desktop app on both ends, create a device on the dashboard, and enter the connection key. Once connected, select the NDI source you want to send and bridge it to the receiving device.

Bridge Sharing is controlled centrally from the dashboard. The same live stream can go to more than one paired device, and each bridge can have its own NDI name, OMT name and SDI output routing.

Each site-to-site route is negotiated automatically. We prefer a direct connection between the devices, then fall back to our cloud relay if NAT or firewall rules make that impossible.

The bridge is built to survive normal production interruptions - if a source stops or a device goes offline, the route stays configured and works to reconnect once both ends are available again.

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

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, especially with a lot of sources on the 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

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

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

NDI and OMT outputs can be enabled, disabled and named independently per bridge without tearing down the connection. 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.

Send 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 a source actively transmitting on a reachable network. Create a stream from the dashboard, 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, 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.

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, individually controllable. Additional audio sources can be exposed separately, and return communication is set per viewer link.

The platform negotiates the route 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

Low-latency NDI over the internet Blackmagic SDI over the internet Encrypted live streaming for production GPU encoding for low-latency live streaming