A managed browser for the screen on the wall
If it runs in a browser, it can run on a DisplayOps screen. We manage the browser, the device, and the recovery.
For: Teams displaying internal web apps, status pages, queue boards, and KPI views.
- CPU temp
- 51.2 °C
- Wi-Fi
- -58 dBm
- Storage
- 6.1 / 29 GB
- Uptime
- 41 d 3 h
- Browser
- Healthy
- Agent
- v0.4.2
The usual pain
- Web apps on wall screens fail in slow, silent ways: memory leaks, expired sessions, changed layouts.
- Nobody owns the screen, so nobody fixes it.
With DisplayOps
- Watchdog restarts the browser when it hangs or leaks.
- Scheduled refresh keeps long-running pages fresh.
- Screenshots let you verify what is on screen from anywhere.
Setup
- 1Pair the device.
- 2Set the URL and a refresh interval.
- 3Enable screenshots and health alerts.
Live MikroTik traffic monitor on a wall display
A MikroTik router already knows which device is using the connection. The open-source mikrotik-home-netflow-plus collector turns its flow export into a web interface with a page built for a small always-on screen. This guide turns on flow export, runs the collector in one container, picks the right wall display URL, handles the optional password, and keeps a Raspberry Pi on it with DisplayOps.
Guide · Uptime KumaUptime Kuma status page on a TV or wall display
Uptime Kuma status pages need no login, refresh themselves and look good on a TV with a few settings. This guide builds one for the wall, makes it private with basic auth at your reverse proxy, shows how the live monitor dashboard can go on a screen as well, and keeps the whole thing running on a Raspberry Pi.
Guide · Custom dashboardYour own dashboard page on a TV, kept private
Sometimes the right dashboard for the wall is one page you wrote yourself: a few big numbers, a list, a clock. This guide covers designing for a TV three metres away, a starter page that reads a JSON file, hosting it with Caddy, putting it behind basic auth, and adding it to DisplayOps so the screen signs in by itself.
Guide · HTTP authenticationHTTP basic auth pages on a TV without typing the password
Credentials in the URL stopped working in 2017 and leak everywhere. DisplayOps now stores a username and password encrypted on the content item and the screen answers the browser's Basic or Digest challenge itself, for the page and everything it loads. This guide covers putting any page behind basic auth with Caddy or nginx, adding it in the portal or the API, verifying it, and the security model.
Questions
Can I inject a cookie or header?
HTTP basic and digest authentication are supported: store the username and password on the content item and the screen answers the prompt for the page and everything it loads. Header and cookie injection are on the roadmap.Guide: a page behind basic auth on a TV
Connect a screen. Tell it what to display. We keep it running.
Three displays are free. No card, no sales call, no signage jargon.