Product · Linked data & live content

Keep the screen useful without pretending every pixel is a database dashboard.

Combine designed scenes with linked menu/product records, clocks, weather, QR, ticker/feed content, slideshows, hours, and supported web/API paths — while keeping the actual capability boundary visible.

Try the editor — no account needed Create a screen free

Real linked records

Structured values update without rebuilding the composition.

The Data panel is the actual operator surface for supported linked menu and product records. It is deliberately narrower than arbitrary database binding.

Prices and sold-out state stay linked to supported records
Widgets own explicit refresh and offline policies
Player compatibility remains visible before assignment

The real Canvas Relay data panel with linked menu and product records — Real linked recordsCaptured from Canvas Relay

Cloud basedAccess anywhere

Design onceUpdate in real time

Relay everywhereAny screen, any size

Reliable & secureOffline playback built in

Live where it helps, designed everywhere else

Linked menu/product records

Bind supported menu/product content and prices so routine data changes can flow through without manually editing every text element.

Clock + hours

Keep time and operating-hour context current while the rest of the screen remains a deliberately designed composition.

Weather

Use the registered weather widget where the player supports it and the location/context makes live conditions useful.

Ticker / feed content

Bring supported feed-style information into a controlled region instead of making the whole TV a browser page.

QR + calls to action

Pair on-screen information with a scannable action that can coexist with the rest of the visual hierarchy.

API + webhooks

Pro-level automation paths can integrate Canvas Relay publishing/device events without turning undocumented integrations into marketing promises.

Player capability still matters.

Browser/Pi has the widest web-runtime fidelity. Roku has a separate native rendering boundary, so unsupported web-only elements should be surfaced before assignment rather than discovered on the TV.

Compare players →

Keep exploring

Widgets

See the visual building blocks available inside the editor.

Scheduling

Change supported content by day, time and date.

Questions, answered

01Can Canvas Relay connect any database to any element?+

No. Canvas Relay supports defined linked menu/product data plus its registered widget, feed, web, API, and webhook paths. This page deliberately does not market arbitrary database binding.

02What live widgets are available?+

The current product includes registered widgets such as clock, weather, ticker/RSS-style content, QR, slideshow, hours, and menu/product display patterns, with platform-specific rendering differences where applicable.

03Does live data break offline playback?+

The board/release can remain cached and playing offline. Data that truly depends on an external source can become stale or unavailable until connectivity returns, so player/content design should account for that distinction.

Design the screen first. Add live context where it earns the space.

Try the editor and build a screen that still works as a design even when a live source is temporarily unavailable.

Try the editor — no account needed

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