Stream Bridge Stream Bridge

Enterprise remote production infrastructure

Stream Bridge brings device management, browser monitoring, bridge routing, communication and operational visibility into one platform, so distributed production teams can run studios, venues, offices and remote sites the same way.

Join Beta
Signal Flow

4 Simple Steps

  1. Connect each location

    Studios, venues, offices and remote teams, each with a paired device.

  2. Manage it centrally

    Devices, sources, viewers and bridges for every location, all in one dashboard.

  3. Connect worldwide

    Direct routes between locations where possible, managed cloud relay where not.

  4. Watch or output

    Controlled browser viewing and production-ready NDI, OMT or SDI outputs.

How it works

Devices pair to a central dashboard, sources stay local to each site, and selected feeds are routed only to the people and systems that need them - one operating model across different locations and source technologies.

Browser viewers, production bridges, multichannel audio and communication can all be managed together, cutting down the number of unrelated tools an organisation has to train, monitor and support across repeat events and permanent facilities.

Connections prefer direct WebRTC routes and use managed cloud relay where network policy requires it. Each route is independent, so you can plan capacity and resilience around actual audiences and critical feeds.

Enterprise deployments can be shaped around the sites, concurrent viewers, infrastructure and support model you need. Custom domains, full white labelling, dedicated infrastructure, advanced permissions and 24/7 support are roadmap options and need availability confirmation.

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 multi-site sources, central control, encoding capacity, network routes, audience access and deployment options.

Supported Sources

NDI, OMT, desktop and DeckLink sources across paired production devices.

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, multichannel, additional and return audio managed within the same platform.

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

Device telemetry and configurable GPU or CPU encoding limits at each site.

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

Browser viewers and production outputs built from the same controlled sources.

Explore details

Custom domains, full white labelling, dedicated infrastructure, advanced permissions, account management and 24/7 support are enterprise roadmap options and need availability confirmation. 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, managed relay for sites where policy blocks peer-to-peer.

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 devices, links, passwords, routes and audience experiences managed centrally.

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.

Enterprise remote production

Frequently Asked Questions

Practical answers about multiple sites, central control, mixed source types, network policy, capacity and deployment planning.

Workflow setup

Yes. Paired devices can represent studios, venues, offices and remote production computers, with their available sources and active routes visible through the dashboard.

Yes. One source can serve browser viewers while Bridge Sharing delivers it to another paired device as NDI, OMT or compatible SDI, with each destination independently controlled.

No. Stream Bridge devices can work with NDI, OMT, desktop and compatible DeckLink/SDI inputs, and remote bridge outputs can be chosen to suit the receiving production.

Monitoring & delivery

Connections use outbound WebRTC and prefer a direct path. Cloud relay is available when NAT or firewall policy prevents peer-to-peer traffic, without needing inbound port forwarding.

Plan encoding load at each paired device, sender upload for every active viewer or bridge, and relay requirements for restricted sites - live telemetry gives you visibility of device and connection health.

No, these are deployment options that need availability confirmation - requirements like dedicated infrastructure, custom domains, advanced permissions, white labelling and 24/7 support should be scoped directly with Stream Bridge.

Related workflows

Custom branded viewer links for clients Group talkback for remote production teams Multi-site live production streaming Remote NDI monitoring for clients and directors