Supported Sources
Password protection is available on viewer links for any Stream Bridge source.
Stream Bridge adds a simple password gate to any live viewer link. Approved people open the link, enter the password, and continue into the player - without getting access to your dashboard, source device or wider production network.
Programme, cameras, multiview or a clean feed from your production.
Install Stream Bridge, add a device on the dashboard and enter its connection key.
Add a password to the viewer link, so only approved people can get in.
They enter the password and watch live in any modern browser.
Password protection adds a clear boundary without complicating the viewing experience - the approved person opens the normal link, enters the password, and continues straight into the live player.
It's set per link rather than per stream, so you can create separate client, director and internal links, each with its own password, branding, controls and audio, all pulling from the same encoded source.
The viewer never gets access to the dashboard or local production network. We handle the WebRTC connection directly or through our cloud network, with no VPN or inbound port forwarding needed.
Passwords can be changed whenever access requirements change, and links can be removed entirely once an event ends. Existing viewers stay connected until they refresh after a password change, so you can plan the transition.
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.
A closer look at link-level passwords, viewer sessions, live changes, media delivery, account security and audience control.
Password protection is available on viewer links for any Stream Bridge source.
Password protection doesn't remove any configured player audio features.
Access is checked before playback, without creating another encode.
The same low-latency WebRTC playback after authentication.
No VPN or production-network access for the approved viewer.
Independent passwords, URLs and player settings per audience.
Practical answers about link passwords, active viewers, separate audiences and protected playback.
No. Passwords are set per viewer link - the same stream can have separate links and passwords for clients, directors, operators or internal teams.
New and refreshed sessions need the new password. People already watching stay connected until they refresh or reconnect.
No. The password only unlocks that viewer page and its configured features - it doesn't expose the dashboard, paired device controls or local production network.
Yes. Password protection can be combined with a custom URL, player branding, additional audio and communication options on the same link.
No. Multiple viewer links can use the same underlying stream. Every active viewer still uses its own connection bandwidth, but a separate link doesn't create another source encode automatically.
Yes. Delete the viewer link when it's no longer required, and the old address stops providing access to the stream.