Manage screens you cannot walk over to

Commands a screen picks up on its own schedule

There is no persistent open connection to a screen and no push infrastructure a screen has to keep alive, since a lot of signage hardware runs on cellular data or shared retail Wi-Fi that is not reliable enough for that. Instead, a device checks in for pending commands on a short, regular cadence as part of its normal operation, the same channel used for instant content push.

An admin queues a restart, a reboot, or an app update from the dashboard, and the target device picks it up and executes it the next time it checks in, typically within a few minutes. This works exactly the same whether the screen is in the next room or in a location you have never physically visited.

Fleet health, without waiting for someone to notice

Every device reports its online status, last-seen time, storage, and battery telemetry back to the dashboard. A screen that goes quiet shows up as stale, then offline, well before a customer or employee in front of it thinks to mention it to anyone. For a network spread across multiple retail locations or a distributed ad network, that early warning is often the entire difference between catching a dead screen the same day and finding out about it a week later from an advertiser complaint.

Over-the-air app updates, staged

Rolling out a new player app version does not mean visiting every device with a USB cable. An update is published as a draft, reviewed, then rolled out to a specific device group or your entire fleet in one action. Devices download and install it automatically on their next check-in, the same mechanism as any other remote command.