Dashboard
Start a rollout and follow it machine by machine.
Generations, the dashboard, how a rollout handles a failure, and the ways to start one.
See what changed between any two versions of a machine, roll it back to an earlier one, or pin it where it is.
~ checkout 4.2.0 → 4.2.1 ~ setting READER_TIMEOUT 5s → 2s = printer 1.3.0 = secret payments-key, version 3 = OS 2026.10.1 1 app restarts. The machine stays up.
Every device, what it runs and how it's doing.
| Device | Status | Software | Resources | Last seen |
|---|---|---|---|---|
| kiosk-12-astore-12 | Online | #42 · Current | MemDisk | now |
| kiosk-12-bstore-12 | Online | #42 · Rolled back #43 | MemDisk | now |
| kiosk-12-cstore-12 | Online | #42 · Current | MemDisk | now |
| kiosk-07-astore-07 | Online | #42 · Current | MemDisk | 4s ago |
| kiosk-07-bstore-07 | Offline | #41 · Current | No data | 3h ago |
| kiosk-31-astore-31 | Online | #42 · Current | MemDisk | now |
| lab-pioffice | Online | #40 · Pinned | MemDisk | 12s ago |
A simulated rollout to 160 machines, in three scenarios.
UpdatedFailedRolled backNot updated
Start a rollout and follow it machine by machine.
Preview and deploy from your terminal.
Deploy when code is merged. The job fails if the rollout fails.
Suggest a fix for a person to approve.
Tell us what you’re building, and we’ll set up a rollout on one of your machines with you.
hello@suta.dev