1. Player boots
Thin player on the clinic LAN or Wi‑Fi pairs with a code or QR.
Security & network
Closed network. Open screens.
StreamScreen players are outbound-only. They start the connection to the cloud. Clinics don’t open inbound firewall holes for day-to-day waiting-room signage.
How it works
Players call out. Your LAN stays closed.
2. Outbound connect
Player initiates outbound HTTPS to StreamScreen — no inbound port forward.
3. Desk publishes
Wait, hours, and promo push from the dashboard. Player pulls and plays.
What we need
- DHCP or static on clinic network
- Outbound HTTPS (and CDN asset fetch)
- DNS resolution
- Bandwidth for media sync after first cache
What we don’t need
- Inbound ports from the internet
- Public IP on the TV VLAN
- Remote desktop into the waiting room
- USB tours for routine updates
Access model
- Dashboard seats are invited — not public signup
- Front desk: wait / hours / promo
- Ops: groups, stale/offline visibility
- Restart / resync without a truck roll
For IT / MSP
Questions to settle before a pilot
Is outbound HTTPS allowlisted on the waiting-room VLAN?
If you lock destinations, ask us for the current domain allowlist.
Ethernet or clinic Wi‑Fi?
Either works. Ethernet is preferred when the TV location allows it.
Who gets invited seats?
Usually the office manager plus an ops owner. We provision — no public self-serve login on this marketing site.
Send this to IT
Request a demo and loop in your MSP — we’ll walk outbound-only pairing on a real player.