Stream Bridge Stream Bridge

NDI to remote NDI over the internet

Stream Bridge sends an NDI source from one production network and delivers it as NDI on another. The internet transport happens between paired devices, so OBS, vMix and other NDI systems just see a clearly named local source - no VPN, no port forwarding.

Join Beta
Signal Flow

4 Simple Steps

  1. Pick an NDI source

    Cameras, mixers, graphics or playback systems on 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. NDI at the far end

    It appears on the receiving network as a named NDI source, like a local one.

How it works

The sending device discovers the source locally, Stream Bridge carries the encoded feed across the internet, and the receiving device publishes a new NDI source on its own network - the experience at both ends stays the same as any other NDI workflow.

The output name is set per bridge, so the destination can identify remote cameras and programme feeds alongside its local sources. One sending stream can also feed additional receiving devices or browser viewers if the production grows.

The WAN path is handled separately from NDI discovery. We negotiate a direct connection wherever possible and use our cloud network when the sites can't communicate directly.

If either device or the original source drops out temporarily, the bridge stays part of the configuration. Recovery works to restore the connection and local NDI output as soon as both ends come back.

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

What operators need to know about inputs, audio channels, device performance, bandwidth, routing, and control.

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

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 source format, viewer load, hardware and whatever else is running.

Viewer Quality & Latency

Live bitrate control, typically under 500ms.

Explore details

The same active stream can be bridged to more than one receiving device, with bandwidth used for each route. 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.

NDI to remote NDI over the internet

Frequently Asked Questions

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

Setup & sources

A paired desktop device at each end, 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.

As a named NDI or OMT source on the receiving device, 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.

Delivery & performance

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, up to 16 channels, 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

Send DeckLink / SDI as remote NDI Stream NDI straight to a web browser Convert NDI to WebRTC Convert OMT to remote NDI