See it
Every page, with a real fleet in it
Thirteen screens across six floors, two of them down for days, one that cannot cover other apps. A demo where everything is green teaches nobody anything, so this one is not.
The panel
What an operator sees
Twelve pages, in the order you would meet them. These are drawn rather than photographed — the columns, labels and numbers are the panel's own, and every one of them stays readable however far you zoom in. Hover a row.
Dashboard
Fleet status, a day of heartbeats, and what every screen is playing.
Screens
Pairing codes, live status, and the one screen that cannot cover other apps.
Compose an alert
Layout, priority, duration and targets, with a live preview of the screen.
Alert history
Every alert sent, and what each screen did with it.
Playlists
Loops of media and announcements, with per-item timing.
Schedules
What plays when, on which screens, and who wins where windows overlap.
Media library
Images and video, checksummed so a screen downloads a file once.
Announcements
Designed cards that need no external design tool.
Users & roles
Four roles, each a named set of permissions rather than a job title.
Audit log
Who did what, to which screen, when.
System health
Database, cache, queue, scheduler, broadcaster and storage.
Demo requests
Leads from the product site, in the same panel.
The wall
What everybody else sees
Nobody buys signage for the admin screen. This is the product from the corridor, photographed.
Content playing
A designed announcement from the loop, filling the screen.
An emergency alert
Takes the whole screen, whatever was playing, until its time is up.
A banner over content
Lower priority interrupts less: the loop keeps running underneath.
A screen waiting to be paired
Six characters, typed into the panel once. That is the whole setup.
A drawing only goes so far
Ask for a demo and drive the real one yourself: send an alert, watch it land, take a screen offline and see the panel notice.
No open demo, no sign-up wall, a person reads every request.