Stream Bridge Stream Bridge

Custom branded viewer links for clients

Stream Bridge lets you brand each audience's viewer separately - your own logo, colours, URL slug, controls and audio options, all powered by the same low-latency stream.

Signal Flow

4 Simple Steps

  1. Pick the feed

    Programme, cameras, multiview or a clean feed from your production.

  2. Pair the app

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

  3. Brand the link

    Set the logo, colours, controls, password and URL for each audience.

  4. They watch your player

    A branded player in their browser that matches your production. Nothing to install.

How it works

The live stream and how it's presented are two separate things. The same production feed can support a polished client viewer, an internal technical monitor and a director link, without forcing every audience into the same layout and controls.

Player appearance, readable URL, password, controls, additional audio and communication features are all set per link. Up to 25 links can be created for a stream, so one source can serve a lot of clearly defined roles.

The viewer opens the branded page in a browser with nothing to install. The WebRTC connection underneath is negotiated automatically, direct where possible and through our cloud network when relay's needed.

Your account username forms part of custom viewer addresses, so repeat productions and clients get consistent links. Because access stays link-based, individual viewers can be changed or removed without touching the source stream.

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

A closer look at per-link branding, custom URLs, player controls, audience variants, access and the underlying live stream.

Supported Sources

Any Stream Bridge source can power several audience-specific viewer designs.

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 and additional audio controls can look different per audience.

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

Branding doesn't create another video encode or interrupt the live source.

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

The branded player keeps the same low-latency WebRTC delivery.

Explore details

Your account username forms part of custom viewer URLs - changing it updates new addresses and invalidates links already shared under the old username. 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

Custom presentation works across direct and cloud relay routes.

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

Logo, colours, custom URL, password and controls per viewer link.

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.

Custom viewer branding

Frequently Asked Questions

Practical answers about logos, colours, URLs, separate audiences and changing the player around a live feed.

Workflow setup

A viewer link can carry its own URL, logo, colours, password, visible controls and audio or communication options - the exact combination can be different for every audience.

Yes. Up to 25 viewer links can be created for a stream, so client, director, operator and event experiences can all use the same live source without sharing one player design.

No. Branding changes the viewer page around the media - multiple links can use the same underlying encode, though every connected viewer still uses its own stream connection.

Monitoring & delivery

Yes. Custom viewer URLs are built around your account username and the link name you choose, making repeat client and production addresses easier to recognise.

Yes, viewer settings can be updated without recreating the production source, though an existing viewer may need to refresh before every change becomes visible.

Yes. Passwords are set at the same link level, so a polished client-facing player can also have its own access control and feature set.

Related workflows