New Remote player tuning, live logs and a JS console

Push once.
Live on every screen.

Relay is the console for your screens — kiosks, TVs, tablets and web players. Pair a device in seconds, push content over a live connection, tune the player remotely and watch its logs as it runs.

Early access · Android, Android TV, iOS and macOS players · Self-hostable

app.relay.opencivileng.com/devices/…
Relay console device page: info, now showing, recent logs, screenshot and remote control
~1 sfrom push to screen, over a persistent socket
6 digitsto pair a new screen — no cables, no config files
40player settings you can change remotely, live
7 daysof searchable device logs, tail-able in real time
How it works

From power-on to live content in four steps

  1. 1

    Install the player

    Sideload the Android APK or run a native client. It registers itself with your Relay server on first boot.

  2. 2

    Read the code

    The screen shows a six-digit pairing code — the way a smart TV does when you set it up.

  3. 3

    Claim it

    Type the code into the console. The device joins your tenant and connects over a secure socket.

  4. 4

    Push and tune

    Assign content, a playlist or a schedule; adjust player settings; read its logs. All live.

Fleet console

Every screen, one dense, honest view

A persistent connection per device means status is live, not a guess. Filter the fleet by status, name, MAC or label, see app version and load at a glance, and open any screen for its full picture.

  • Online / offline within seconds of it happening
  • Labels and smart groups that keep themselves current
  • Multi-screen machines report each display separately
Relay console devices list with status, labels, app version and CPU/memory per device
Remote player tuning

Change how a player behaves without touching it

WebView, playback, logging and connection settings — set once for the tenant, override per device, pushed live over the socket. Every value shows where it comes from and can be reset with one click.

  • Autoplay, permission grants, user agent, cache, mixed content
  • Remote debugging over chrome://inspect, on demand
  • Periodic reloads, injected JS, a status overlay for the install crew
Player settings editor filtered to WebRTC and P2P relevant settings
Logs & live console

See what the player sees — then poke it

Console output, network failures and player lifecycle stream back from every device into one tail-able log, filterable by device, level and source. Run JavaScript inside a device’s WebView and get the result back in the same stream.

  • Live tail, search, download, seven days of history
  • Per-device logs right on the device page
  • Reload, hard reload, screenshot, restart — one click each
Terminal-style device log viewer with an exec_js prompt
Content, playlists, schedules

Images, video, web pages and HTML — in order, on time

Upload or link content, build playlists where every item has its own duration, and schedule changes with cron. Deploy to a device, a group, or a label in one flow.

  • Drag to reorder, per-item durations
  • Cron schedules with failure alerts
  • Assign to a screen index on multi-display machines
Playlist editor with ordered items, durations and the content library
Everything else you need

The parts of a CMS you only notice when they’re missing

Pair in seconds

A new screen shows a six-digit code. Type it in, it’s yours. Remove it and it gets a fresh code on its own.

Labels & smart groups

Auto-label by OS, resolution, MAC or subnet the moment a device connects; groups match labels with AND/OR.

Multi-tenant

One login, many locations. Every view re-scopes when you switch tenants from the header.

Roles & permissions

Viewer, operator, admin, owner — and per-action minimum roles you can change from Settings.

Alerts

Device offline, storage near quota, schedule failed — in the bell menu, critical ones by email.

Audit log

Every state-changing action — including every command and every settings change — with who and when.

Remote commands

Reload, restart, screenshot, volume, brightness, next/previous, clear cache, run JS — each with a delivery ack.

Open API & docs

Everything the console does goes through a documented REST API, plus a documented device protocol.

Built for web players

Your HTML app, running on every screen — and observable

Relay treats a web page as a first-class player. Your page can learn which device it is on, log straight into Relay, and you can change the WebView around it without shipping a new build.

  • Device identity via URL params or the JS bridge
  • console.* forwarded with a configurable level
  • Autoplay and media permissions for WebRTC, per device
Read the player guide
player.js
// Who am I? (when the JS bridge is enabled)
const info = JSON.parse(RelayPlayer.getDeviceInfo());
// → { deviceId, screenIndex, assetId, webviewVersion … }

const pc = new RTCPeerConnection(config);
pc.onconnectionstatechange = () =>
  RelayPlayer.log('info', `peer ${pc.connectionState}`);
Device override · pushed live
{
  "webview": { "remoteDebugging": true, "autoGrantPermissions": true },
  "player":  { "appendDeviceParams": true, "reloadIntervalSec": 3600 },
  "logging": { "consoleLevel": "debug" }
}
Where it runs

Native players, one console

Android & Android TV

The reference player: WebView, ExoPlayer video, full remote tuning and log forwarding.

Available

iOS & iPadOS

Native SwiftUI client with pairing, playlists and all remote commands.

Available

macOS

Multi-display aware — each connected screen is its own addressable target.

Available

Windows, Linux, Tizen, webOS

Planned. Any browser can already show your content; native players add control.

Planned
Use cases

Screens that have to be right

Retail & QSR

Menu boards that change the moment a price does.

Lobbies & offices

Reception screens and directories that show today, not last week.

Hospitality & venues

Day-parted content that switches on its own schedule.

Campus & transit

Wayfinding and urgent messages pushed everywhere at once.

Interactive kiosks

Your web app, full screen, with remote reloads and logs.

Labs & prototypes

Test web and WebRTC players across many devices on one network.

FAQ

Questions, answered plainly

Something else? Get in touch.

Which devices can run the player?

Android and Android TV (the reference player, a sideloaded APK), plus native iOS/iPadOS and macOS clients. Anything that can render a web page can show your content; the native players add pairing, remote commands, telemetry and log forwarding.

Can I show my own web app on the screens?

Yes — URL and HTML content run in a full WebView you can tune remotely. Your page can read its device identity and write to Relay’s logs through the optional window.RelayPlayer bridge.

What happens when a screen loses its network?

It keeps showing what it has and reconnects on its own with backoff. Relay marks it offline within seconds and, if you want, raises an alert after a threshold you choose.

How are devices secured?

TLS on every connection, a unique token per device issued at pairing, role checks on every request, and an audit log of every state-changing action. Mutual TLS is supported by the server and can be enabled per deployment.

Can I self-host it?

Relay is a Go server, Postgres, S3-compatible storage and two static web apps, deployed with Docker Compose. The deployment guide is part of the docs.

Is there pricing?

Not yet — Relay is in early access. New workspaces start with room for five screens; ask if you need more.

Bring your first screen online today.

Create a workspace, install the player, type in the code.