Skip to content

Player · BrightSign developer host

Commercial signage hardware, without another renderer.

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.

Cloud basedAccess anywhere
Design onceUpdate in real time
Relay everywhereAny screen, any size
Reliable & secureOffline playback built in

Host architecture

A thin BrightSign host around the browser player.

The package and host bridge are implemented. Production support remains gated by a recorded playback, recovery, capture, and reboot pass for the exact model and BOS release.
brightsign
Model and BOS QA required
01
Build autorun package

Deterministic zip and SHA-256 manifest

NO TENANT SECRET
02
Provision device

SD/USB root or controlled B-Deploy package

PACKAGE
03
Launch roHtmlWidget

Full-screen Canvas Relay browser renderer

CHROMIUM
04
Bridge fleet operations

Telemetry, requested capture, reload, diagnostics

BSMESSAGEPORT
OUTPUTAssigned Canvas Relay board

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.

What the BrightSign host provides

01

One browser renderer

roHtmlWidget launches player.canvasrelay.app full-screen. BrightSign integration supplies host operations and telemetry rather than duplicating scene/widget rendering.

02

Deterministic autorun output

The build creates a stable autorun package plus SHA-256 manifest with normalized file order and timestamps for controlled distribution.

03

B-Deploy-ready provisioning

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.

04

Fleet hardware telemetry

The bridge reports BrightSign model, BOS version, serial-derived platform identity, boot/uptime and explicit remote-operation capabilities to Fleet Health.

05

Actual capture is explicit

Supported hosts capture through roVideoMode only after an operator request, then upload bounded image bytes to private R2-backed device storage.

06

Safe recovery and updates

Persistent Chromium storage, network recovery, package checksums and BrightSign recovery/B-Deploy conventions support controlled unattended rollout without enabling inspectors or insecure HTTPS.

Questions, answered

01Does Canvas Relay use a separate BrightSign renderer?+

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.

02Which BrightSign models and BOS versions are supported?+

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.

03Can operators capture the actual display?+

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.

04Does the package contain my Canvas Relay secret?+

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.

Validate the exact hardware before rollout.

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 needed

Free plan includes one live screen. No credit card. No trial clock.