Stream Bridge Stream Bridge

Encrypted live streaming for production

Stream Bridge carries production feeds through encrypted WebRTC connections and controlled viewer links - your source network stays private, there's no inbound port to open, and clients, internal teams or confidential events can all get password protection.

Join Beta
Signal Flow

4 Simple Steps

  1. Pick a private feed

    Cameras, programme, multiview or internal content you need to keep private.

  2. Pair the app

    Install Stream Bridge, add a device on the dashboard and enter its connection key.

  3. Share a controlled link

    Add a password and audience settings per link. Media is encrypted in transit.

  4. Approved viewers watch

    They watch in a browser with no access to your production network.

How it works

Stream Bridge is built to share the feed, not expose the network behind it. Media travels through WebRTC encryption, and each viewer only gets the player and features configured for their link.

Sensitive streams can use separate links and passwords for different audiences, so a private rehearsal, internal announcement, client feed or unreleased production stays isolated from links used elsewhere.

No inbound production port needs opening to the viewer. We negotiate the route automatically and use our cloud relay network when a direct connection isn't possible.

Transport security works alongside practical access discipline - keep connection keys private, remove viewer links when they're no longer needed, and check the dashboard for which streams and viewers are active.

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

A closer look at encrypted transport, viewer access, direct and relayed routes, production audio, performance and operational control.

Supported Sources

NDI, OMT, desktop and DeckLink sources stay on the paired production device.

Explore details

Stream Bridge works with an NDI, OMT, desktop or DeckLink/SDI source available to it - cameras, mixers, graphics, presentations, multiviews and programme outputs 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

Production audio travels inside the same protected real-time session as the picture.

Explore details

Programme and additional audio can be routed according to the chosen source and viewer configuration, and up to 16 channels are available where the source supports it.

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 or CPU encoding prepares the source without exposing the production network.

Explore details

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

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

Low-latency WebRTC media protected in transit between every connected endpoint.

Explore details

A viewer link is still a credential - use unique links, passwords and sensible distribution practices for sensitive productions. Every viewer is a separate connection, and your bitrate applies to each - 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, with authenticated, time-limited cloud relay when required.

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 viewer links, optional passwords and revocable access 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.

Encrypted live streaming

Frequently Asked Questions

Practical answers about media encryption, viewer access, relay routes and protecting a live production feed.

Routing & setup

Yes. Every viewer session runs over WebRTC, which protects the live audio and video in transit between the connected endpoints.

No. The viewer receives the selected encoded feed through a browser link - they don't join the local NDI or OMT network, and they don't get access to the paired device or dashboard.

Yes. Passwords and player settings belong to individual viewer links, so clients, directors and internal teams can each use a separate access path to the same stream.

Bandwidth & reliability

Yes. When a direct route isn't available, Stream Bridge uses authenticated, time-limited relay credentials, so you don't need to publish inbound ports or share permanent relay credentials.

Yes. Viewer links can be changed or removed independently - changing a password affects new and refreshed sessions, and deleting the link removes that access path entirely.

No. Stream Bridge establishes the WebRTC route across the existing internet connections at each end. A VPN and inbound port forwarding aren't required for the viewer.

Related workflows

GPU encoding for low-latency live streaming TURN relay for production streaming behind firewalls Blackmagic SDI over the internet Low-latency NDI over the internet