Fleet operations for connected hardware
Run the machines you’ve shipped from anywhere. Deploy software, see how every machine is doing, and fix problems without going on site.
Software, settings, secrets and the OS are versioned together, so you always know what's on each machine.
Which software changes, which machines restart and what stays the same. What you see is exactly what ships.
~ checkout 4.2.0 → 4.2.1 = printer unchanged = OS unchanged 212 machines will update 1 pinned, keeps what it runs 0 restarts
If a new version breaks a machine, it goes back to the last one that worked, even when it's offline.
New versions reach a handful of machines first. If something goes wrong there, the rest of the fleet keeps running what works.
Paused: 1 machine failed. The other 201 were not updated.
Logs, metrics and alerts for every machine, and a shell on any of them when you need one.
# update.sh for host in $(cat kiosks.txt); do ssh admin@$host 'docker pull acme/checkout && docker restart checkout' done ssh: connect to host kiosk-31-a port 22: No route to host Error response from daemon: manifest unknown … 37 hosts later, nobody knows which ones updated
Each one takes weeks to get right, and has to be tested again for every new machine and OS release.
Generations, the dashboard and how a rollout handles a failure.
What agents can do on their own, and how you approve the rest.
How machines check updates, who can reach them, and the records Suta keeps.
Tell us what you’re building, and we’ll set up a rollout on one of your machines with you.
hello@suta.dev