Keeping your rig secure
The dashboard controls your router, your cameras and your stream, so treat access to it like access to the stream key.
The short version
Set a dashboard password under Settings → Dashboard login, and always set one before sharing the dashboard with anyone.
Never port-forward the dashboard or put it on a public IP. Reach it from the rig's own Wi-Fi, over
Tailscale, or with the dashboard's own share links.
Treat these as secrets: overlay URLs, the Pro pairing link, dashboard share links, Trivia/Polls/Jokes helper links, dashboard passwords, stream keys,
API keys and your settings backup file. Don't show them on stream, and blank them out of screenshots.
Turn sharing off when the person you shared with is done.
Overlay URLs are keys
An encoder, OBS or a remote guest loading a browser source can't log in, so overlay pages don't ask for a password. They're protected by a long random token in the URL instead. That is true whether or not the dashboard has a password.
The login gate
The dashboard ships without a password, because on a private network behind the router it doesn't need one, and a forgotten password on a device you're about to walk out of the door with is its own outage.
Settings → Dashboard login turns the gate on.
Type a Username, Password and Password again, then press Save settings. Clearing the username switches the login off.
You can let devices on the rig's own network skip the login with Don't ask on the router's own WiFi, so the rig's tablet opens quickly while anything coming from outside must log in. The gate is then only as strong as what you let onto that network.
The sign-in page has Stay signed in on this device. It is signed by the router and expires after about 30 days. Changing the dashboard password invalidates remembered devices.
Overlays and their data feeds keep working with the gate on, so turning it on never breaks a running stream.
Sharing the dashboard
| Method | Who can reach it | Notes |
| Tailscale (tailnet) | only devices you have added to your tailnet | Preferred. No public address at all. |
| Share link (Tailscale Funnel) | anyone with the link | A random public HTTPS address made on the router. Use it for someone you can't add to your tailnet. |
| Trivia/Polls/Jokes helper link | anyone with the helper link | Opens only those three audience-game pages, not the full dashboard. |
Sharing is off until you turn it on, and the address is random rather than guessable.
Set a dashboard password first. With the gate off, the share link is the only thing between the internet and full control of your router.
On the Router tab, Create a public link makes the full-dashboard link, New link — cuts off the old one replaces it, and Stop sharing turns it off.
On Trivia, Polls or Jokes, Share with a helper has Turn on, Turn off and New link for the helper-only link.
Revoking either link stops it at once, and making a new one kills the old one.
Offline mode. Over a Tailscale or share link, the dashboard needs the router's own internet connection. If that drops (a ride, a tunnel, no signal), a helper's changes are kept in their browser and an orange Router unreachable bar shows how many are waiting. When the router comes back, they are sent in order. Show lists them, Send now retries at once, and Discard all throws them away. Only changes are kept, and only ones that clearly never reached the router, so nothing runs twice. Uploads are not kept, and saved changes older than 12 hours are dropped.
Pro Chat and StreamHelpers Pro
Your platform sign-ins (YouTube, Twitch, Kick and others) are held by StreamHelpers, not on the router, and your browser never receives them. The router keeps only a pairing secret and gets short-lived access when it needs it. Unpairing from the dashboard ends that access.
Settings backups
Settings → Backup & restore → Download backup is one file with your whole setup in it. API keys and passwords are left out unless you ask for them, so a normal backup is safe to keep in cloud storage. A backup that includes them should be stored like a password. The router's own internal signing key is never in any backup, so a backup file can't be used to get into your router.
Use Include passwords and API keys only when you need those secrets moved. If a backup has redacted secrets, restoring it leaves whatever is already on the router alone instead of blanking it.
Found a security problem?
Don't post it in public. Send a private message to a member with the Trusted role on Discord. They pass it on straight away.