Current 64-bit OS architecture
The project follows the official Trixie arm64 web-kiosk example with Cage and Chromium instead of mutating a floating latest image through an X11 chroot.
Player · Raspberry Pi appliance tooling
The Canvas Relay Pi project uses the existing browser player in Cage/Chromium and adds current Raspberry Pi image tooling, A/B partitions, hardware watchdog, local telemetry, actual capture and controlled reboot. Source is ready; production hardware support is not claimed yet.
Appliance architecture
Pinned rpi-image-gen source and static validation
Unique local-agent credential, Cage, Chromium
Six-digit code creates the cloud device identity
systemd, hardware watchdog, last-known-good release
Appliance tooling · physical QA required
rpi-image-gen project and static validation are available. A downloadable release image and exact Pi/display/storage compatibility require a real build and physical QA.
The project follows the official Trixie arm64 web-kiosk example with Cage and Chromium instead of mutating a floating latest image through an X11 chroot.
First boot generates a local agent credential. Canvas Relay pairing still creates the unique cloud device identity on screen; credentials are not baked into the image.
systemd restarts the agent and kiosk, Raspberry Pi's kernel/systemd hardware watchdog covers a wedged OS, and the browser player preserves last-known-good content.
A localhost-only agent reports model, OS, architecture, uptime and boot identity, and enables capability-gated actual screenshot capture and clean reboot.
The image uses rpi-image-gen's A/B base and persistent data layout. Canvas Relay does not invent an unsafe OTA flasher; slot update and rollback remain release-engineering work to validate.
Sample cloud-init customization reflects current Raspberry Pi Imager behavior. Wi-Fi values remain deployment inputs, never repository secrets.
Use the browser path immediately while the appliance image goes through release QA.
Read more →Compare a commercial signage host that uses the same browser renderer and Fleet Health contract.
Read more →Review truthful expected previews, actual captures, telemetry history and remote actions.
Read more →Not yet. The repository contains reproducible rpi-image-gen source and structural validation, but Canvas Relay does not claim a downloadable production image or physical-hardware pass until an image is built and exercised on the target Pi, display and storage media.
The current project follows Raspberry Pi's official 64-bit Trixie rpi-image-gen web-kiosk and A/B layout guidance. Package inputs still need a controlled snapshot or recorded manifest for byte-for-byte release reproducibility.
Use current Raspberry Pi Imager cloud-init/rpi-preseed customization or Ethernet. Legacy boot-partition wpa_supplicant.conf guidance is not valid on current Bookworm/Trixie images, and no shared Wi-Fi credential is baked into the image.
The hosted browser player retains its complete last-known-good release and starts without waiting on a public ping. Actual power-cut, cache-pressure and long-duration offline behavior still belongs in the physical QA checklist.
Run the static validator, build with a pinned rpi-image-gen revision, verify manifests, then complete the physical power, network, display, cache, capture and rollback checklist.
Try the editor — no account neededFree plan includes one live screen. No credit card. No trial clock.