QSR Inspector Vision
Network Requirements — for the IT team
This one-pager describes everything the QSR Inspector Vision appliance needs from your network. It was written for network administrators; the summary is one line:
✓ Outbound HTTPS (TCP 443) only. No inbound connections. No port forwarding. No firewall exceptions for inbound traffic, ever.
What the device is
A single small Linux appliance (NVIDIA Jetson) that processes camera video locally on the device. Video never leaves the building — only small operational telemetry messages (kilobytes) are sent to our cloud. Typical sustained bandwidth is under 10 kbps.
Connections it makes (all outbound, all TLS)
| Destination | Port | Purpose |
|---|---|---|
*.supabase.co | 443 | Telemetry & configuration API |
*.tailscale.com / *.tailscale.io | 443 | Managed remote-support tunnel (outbound-only; relays over TLS when UDP is unavailable) |
| NTP (system default) | 123/udp | Clock sync (falls back to HTTPS time if blocked) |
What it needs from the LAN
- DHCP — one IPv4 lease. (MAC address is printed on the unit for allow-listing.)
- Reachability to the site's camera VLAN or the NVR (RTSP, TCP 554) — local traffic only.
- No captive portal on the segment used.
What it never does
- No inbound connections from the internet — the device is unreachable from outside.
- No video or audio upload. No PII: the AI tracks anonymous positions, not identities.
- No scanning, no discovery traffic beyond DHCP/DNS/NTP, no traffic to other LAN hosts except the cameras/NVR you designate.
If policy can't accommodate this
No problem — the install kit includes a cellular (LTE) gateway. The appliance operates entirely on it, touching only the camera VLAN/NVR locally. Zero footprint on your network.
Questions: support@qsrinspector.com · Randys Rips LLC — QSR Inspector, New Orleans, LA