Skip to content
Security

Only you can change your machines.

The safeguards built into Suta, and the records it keeps for you.

Signed updates

Machines install only what Suta signed.

Machines refuse anything that isn’t signed by Suta, so nobody can push code to them by pretending to be Suta.

  1. SutaSends a signed update
  2. MachineChecks the signaturerefuses anything unsigned
  3. MachineInstalls it and runs its health checks
  4. MachineKeeps it, or goes back to the previous version
Access

Who can reach your machines.

Time-limited access

Shell access is off until someone turns it on, and it turns itself off again. Every session is recorded.

Access on kiosk-12-b · turns off in 54m

Permissions

People, CI pipelines and AI agents each get only the permissions you give them.

ci-deploy token · Deploy software · kiosks only

Activity log

Who changed what, on which machine and when, whether it was a person, a pipeline or an agent.

Maya approved a restart for Claude · 3 machines
Compliance

Records for compliance.

When a customer or regulator asks what’s running on your devices and who changed it, the answer is already there. It’s the kind of record the EU Cyber Resilience Act asks device makers to keep.

Generation 7b19e4d0
Contents
214 components, listed
Built from
acme/kiosk at 9f3c2a1
Built by
GitHub Actions, run 4182
Running on
211 machines in 3 sites
Signed
verified on every machine

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