Open the interactive StreamHelpers demo in a browser. No router, phone, invitation or Pro subscription is needed.
The demo is separate from the real rig. Its fictional data and saves stay in the browser; lightweight, read-only PHP renders overlay previews when design options change. It cannot reach equipment or modify an account. All available demo tabs and Pro options are enabled for exploration and customization, but there is no login, payment, account pairing or real public link.
A real rig lets you choose which tabs, features, header chips and overlay designs to use. The demo exposes the available options; this does not put every overlay on air at once. A few preset Clock, Weather and GPS examples run in the program previews. Designers and editors update their own previews, but do not change those preset program examples.
The bottom of the demo links back to the homepage and explains that this is an incomplete simulation for illustrating the ecosystem, not a fully functioning rig.
Reset demo is the only button in the top toolbar. Reloading also discards the synthetic state. Panels start collapsed, including after Reset, except the Companion video preview, which starts expanded. There is no incident picker or bottom Companion visibility toggle. Modal dismissal buttons simply say Close, including Guided setup. Nothing is saved to a router or server. Do not enter personal information into fictional crew messages.
Short, silent, openly licensed film excerpts stand in for camera inputs, clips and backup video: Big Buck Bunny, Elephants Dream, Tears of Steel and the Sintel trailer. Each is a bundled 12-second, 640 x 360 loop; visitors do not load complete external movies. Media credits and licenses identify the creators, sources, licenses and edits, including PNG film stills, public-domain USGS / USDA NAIP aerial imagery and the captured NOAA radar. Browser graphics compose camera layouts, overlays, photos, clips and BRB. Synthetic data supplies bonding, GPS, weather, viewers, chat, games, device roles, warnings, destinations and receiver status. Header chips have example readings, including a healthy 30 FPS before starting the simulated broadcast; these are not measurements.
Backup video, a backup receiver and a spare director are different things. Losing camera ingest shows the receiver's backup picture; losing the main receiver changes the delivery server; losing the director changes which phone is the encoder.
Restreamer represents a self-hosted media server. Restream.io represents the separate cloud publishing service. Their example addresses and accounts are fictional. See how the real products fit together.
The dashboard tabs now use the production page markup, scripts and hosted designers rather than the earlier simplified recreations. This includes Bonding, Network, Restreamer, Restream.io, GPS, Weather, Clock, games, Photos, Supporters, Companion controls, Director Mini, Settings and the header chips editor. Their service responses are simulated in browser memory. A visible control is not a promise that every hardware operation is implemented: unsupported commands report that boundary explicitly.
Router uses the real, separate router health and administration panels with fictional temperatures, CPU, memory, clients, storage and uptime. Bonding accumulates a changing graph with fake per-link rates, health, signal strength and carrier details; illustrative traffic flows even before the demo broadcast starts. Companion includes example video and image clips, including a BRB background. DJI demonstrates detection and connection using a fictional camera. SJCAM displays the real QR presentation with fictional Wi-Fi and destinations, but the symbol encodes only a demo label, not a camera provisioning command. Settings → System update shows example installed/latest versions and a last check of one hour ago; no update runs.
Open Timer to try the actual Timer page, production JavaScript and overlay renderer against simulated browser-local endpoints.
The Timer's title, fonts, colors, templates, arrangement, picture options, background, border and animations are editable. Drag and resize the actual overlay in its preview, start and stop a count-up timer, or run a duration/finish-time countdown. The separate stream timer supports manual controls and can follow the demo's Start stream state in Automatic mode. Changes survive tab navigation but are discarded on reload or Reset demo.
The Live video preview background is fictional. Sponsorship edits are local. AI is never called. Overlay visibility switches change local control state, not the fixed program examples; the Timer's stop-time hide/restore question and custom overlay groups remain disabled with an explanation. No router files or external services are used at runtime.
The Weather, Clock, GPS and other preview templates use the same presentation calculations as the real product. Red text beside Live preview says Demo only, does not update video preview. Designers update their own previews, not the fixed program examples. On a real rig, saving applies the design exactly as shown in its designer. Map exploration is limited to the bundled Magic Kingdom aerial crop rather than a worldwide tile service. A single read-only preview endpoint renders HTML, CSS and embedded appearance options. Timers, telemetry, preferences, games, crew messages, media playback and map motion remain browser-driven. This is not a video encoder.
Unsupported controls and More controls on the real page explain features that are not modeled, using plain descriptions without internal filenames, paths or service addresses. Real radio scans, Bluetooth, OAuth, arbitrary destinations, AI, voice input, billing, invitations, public links, media uploads, restores and system updates do not run. Guided setup uses the real question flow with simulated discovery and browser-only saves, not real provisioning.
Settings uses the actual dashboard form rendered with fake configuration. Menu bar switches change which demo tabs are visible after Save settings. Non-secret preferences can be explored locally. Destination fields are replaced visually with a simulated-destination label; password, key and upload inputs are disabled, including dynamically added fields. Device installation, account configuration, restores and system updates are explanation-only. No setting changes a real endpoint or equipment.
The Companion panel is a synchronized browser recreation, not an Android emulator or the actual app. The real Android app has many one-handed operations and quick access to the controls, messages and stream information IRL streamers need. The mockup does not show all of these controls. Layouts are browser compositions, not encoded streams. Audio switches display state but do not record, play or process sound. This is not a test of SRT latency, codec quality, phone temperature, bandwidth, actual failover timing or hardware compatibility.
The Mini preview is omitted from this demo. The real dashboard works on desktop and mobile; the demo presents its desktop view to illustrate the range of options and settings.
Each demo page has one Help with this page (wiki) link below its content. In-page help icons and duplicate help links are omitted, and the dashboard help setting is disabled in the demo. This does not change the help options on a real rig.
In Guided setup, What the one key gets you. opens the complete public AI feature guide in a separate tab. This deliberate documentation link does not enable AI calls, account navigation or equipment access.
Supporters and tips is not a menu tab. Open it through Overlays → Supporters and credits → Edit. The Theme parks tab and its nearby-ride picker are not included in the demo dashboard or Companion simulator.
The server serves static files and small bundled video loops, plus brief PHP requests for allowlisted, read-only preview templates. Simulation and saved demo state run in the visitor's browser. There is no streaming backend, per-visitor encoder, persistent visitor storage or background job. Camera, microphone, location and Bluetooth access are disabled. There are no network API calls: dashboard service contracts are answered in browser memory. Only static assets and allowlisted read-only HTML presentation documents are loaded. No platform-chat, weather-service or map-tile requests are made.
The header identifies the dashboard and Companion versions represented by the demo. Controls marked explanation-only describe a workflow rather than carrying it out.