Streaming and Visualizer
Recommended flow
- Your frontend asks your backend for a session.
- Your backend calls the Hub GraphQL control API.
- Your backend returns the bootstrap payload to the frontend.
- Your frontend connects with that payload.
requestDeviceWebrtcConfigfor device sessions such as Web Terminal and live logsrequestDeviceAppConnectionfor app sessions and visualizer sessions
Backend-mediated by default
Do not call these bootstrap flows directly from the browser with a Hub API key. The backend should own Hub credentials and return only the derived connection payload.
Visualizer is the default recommendation
- camera streams
- detections and overlays
- richer outputs such as point clouds
When to use custom rendering
- you need a fully bespoke UI
- your stack is not centered on the JavaScript visualizer path
- you want to own the full rendering pipeline yourself
Connection modes
- Hub-mediated remote access over WebRTC for remote portals, Hub UI, and customer-facing cloud products
- Same-LAN direct access over websocket for local/device-side access patterns
Related Hub features
- Web Terminal uses the device session path.
- Live app logs use the device session path.
- App frontends and visualizer sessions use the app connection path.