One browser renderer
roHtmlWidget launches player.canvasrelay.app full-screen. BrightSign integration supplies host operations and telemetry rather than duplicating scene/widget rendering.
Player · BrightSign developer host
Canvas Relay wraps its existing browser player in a thin BrightSign autorun host. The package, telemetry bridge, capture path and B-Deploy-style workflow are testable now; production support remains model-and-BOS hardware-QA gated.
Host architecture
Deterministic zip and SHA-256 manifest
SD/USB root or controlled B-Deploy package
Full-screen Canvas Relay browser renderer
Telemetry, requested capture, reload, diagnostics
Developer package · hardware QA required
Developer package and structural validation are available. No BrightSign model or BOS release is labeled production-supported until physical-device QA records a pass.
roHtmlWidget launches player.canvasrelay.app full-screen. BrightSign integration supplies host operations and telemetry rather than duplicating scene/widget rendering.
The build creates a stable autorun package plus SHA-256 manifest with normalized file order and timestamps for controlled distribution.
Use SD installation or register the generated autorun package in a controlled B-Deploy workflow. Runtime pairing creates the unique device credential; package files contain no tenant secrets.
The bridge reports BrightSign model, BOS version, serial-derived platform identity, boot/uptime and explicit remote-operation capabilities to Fleet Health.
Supported hosts capture through roVideoMode only after an operator request, then upload bounded image bytes to private R2-backed device storage.
Persistent Chromium storage, network recovery, package checksums and BrightSign recovery/B-Deploy conventions support controlled unattended rollout without enabling inspectors or insecure HTTPS.
Review the renderer and offline release behavior hosted by BrightSign Chromium.
Read more →Compare the reproducible Pi kiosk path for deployments that do not require BrightSign hardware.
Read more →See health scoring, remote actions, history and actual-versus-expected capture truth.
Read more →No. The native host launches the existing hardened browser-class player in BrightSign's documented roHtmlWidget Chromium environment. Scenes and widgets keep the same browser rendering path.
The package targets current roHtmlWidget-capable hardware, but Canvas Relay does not claim a production model/BOS pass until that exact combination is exercised on physical hardware and added to the compatibility matrix.
The host implements BrightSign's documented roVideoMode screenshot path and uploads only in response to a short-lived, tenant-scoped Canvas Relay capture request. A server-rendered expected preview remains clearly separate.
No. The deterministic autorun package contains only public player configuration. The device establishes its unique Canvas Relay identity through the normal on-screen pairing flow after provisioning.
Build the package, provision a QA player, pair it normally and record playback, recovery, capture and reboot results by model and BOS version.
Try the editor — no account neededFree plan includes one live screen. No credit card. No trial clock.