Skip to content
Tilecast Edge is in preview. Its software is complete, but it is not qualified on physical hardware yet. Use the stable Linux Player on production screens until a Tilecast release supports your hardware.

Edge requirements

These are the minimums Edge needs. A computer that meets them can still differ in graphics, codecs, and display hardware, so run a pilot screen before you roll Edge out. See Plan your rollout.

  • Linux kernel 5.6 or later;
  • systemd 248 or later;
  • a 64-bit x86_64 or aarch64 computer;
  • enough local storage for Edge, its database, downloaded content, and a second release during an update;
  • network access to Tilecast Server.

Debian 12 and later meet the kernel and systemd minimums. Treat another distribution as supported only when the Tilecast release notes list it.

Edge brings its own copy of WPE WebKit and the libraries that only WebKit needs, so you don’t install them. It expects the usual Debian 13 libraries from the operating system, which keeps them patched. A Debian 13 desktop install has them. A minimal install may not.

  • the runtime packages listed in system-baseline.txt (GLib, GStreamer, libsoup, Mesa’s GBM and DRM libraries, ICU, and similar);
  • bubblewrap and xdg-dbus-proxy, which WebKit starts to sandbox web content;
  • the GStreamer plugin sets and Mesa drivers for the video formats and graphics hardware you use.

Edge also needs the kernel to allow unprivileged user namespaces, which is the Debian default.

Edge draws with WPE WebKit instead of Electron. The installer and the migration run Edge directly on the display (DRM/KMS) on the first console, without a desktop session. A computer that must keep its desktop session can’t use this release of Edge.

Output depends on the real graphics hardware, rotation, connectors, hardware decoding, CEC and DDC/CI, so check a pilot screen with the display you plan to use.

Check the release notes for the supported architecture, Linux distribution, display output, codecs, and Display Control hardware. If your computer doesn’t fit, keep using the AppImage Player.

Edge uses the normal Tilecast Player HTTPS and WebSocket connections to your server, and downloads updates only from your server, never from GitHub. LAN discovery is optional, so manual server entry works on networks that block multicast.

Use HTTPS for public hostnames. Local HTTP works only for the same trusted local addresses that the stable Tilecast Player accepts.