Skip to content
Platform

Deploy, watch and roll back.

Generations, the dashboard, how a rollout handles a failure, and the ways to start one.

History

Every version is kept.

See what changed between any two versions of a machine, roll it back to an earlier one, or pin it where it is.

kiosk-12-b · #42 → #43
~ 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.
Dashboard

Your whole fleet on one screen.

Every device, what it runs and how it's doing.

app.suta.dev/projects/kiosks/devicesSample fleet

Devices

Add device
212 online1 rolled back1 offline3 sites
Filter devicesAll sites All tags Group by site
DeviceStatusSoftwareResourcesLast seen
kiosk-12-astore-12Online#42 · CurrentMemDisknow
kiosk-12-bstore-12Online#42 · Rolled back #43MemDisknow
kiosk-12-cstore-12Online#42 · CurrentMemDisknow
kiosk-07-astore-07Online#42 · CurrentMemDisk4s ago
kiosk-07-bstore-07Offline#41 · CurrentNo data3h ago
kiosk-31-astore-31Online#42 · CurrentMemDisknow
lab-piofficeOnline#40 · PinnedMemDisk12s ago
Simulation

How a rollout handles a failure.

A simulated rollout to 160 machines, in three scenarios.

UpdatedFailedRolled backNot updated

Simulated rollout · v2.4.00 / 160 updated
  1. Canary8 machines
  2. Batch 148 machines
  3. Batch 2104 machines
Ways to deploy

Start an update from wherever you work.

Dashboard

Start a rollout and follow it machine by machine.

Command line

Preview and deploy from your terminal.

CI pipelines

Deploy when code is merged. The job fails if the rollout fails.

AI agents

Suggest a fix for a person to approve.

Want to see Suta on your hardware?

Tell us what you’re building, and we’ll set up a rollout on one of your machines with you.

hello@suta.dev