Your account, your machines
Servers are created in your own Hetzner project, DigitalOcean team or AWS account. KamalCloud owns no servers, and resells no infrastructure.
About
KamalCloud is a client of your infrastructure, not the owner of it. Everything it writes is something you could have written yourself.
We are a small team running our own Rails applications on Hetzner with Kamal. We got tired of the half-finished hardening checklist, the backup nobody had restored, and the SSH key three people shared. It exists because we wanted it.
Kamal builds, ships and swaps traffic, and it does that better than anything else. Everything that happens to the box before and after — creating it, locking it down, keeping it patched, proving the restore works, knowing what it costs — was still somebody's Tuesday afternoon. That is the part we built.
Servers are created in your own Hetzner project, DigitalOcean team or AWS account. KamalCloud owns no servers, and resells no infrastructure.
The API and CLI read your servers and apps. Every change they ask for is a request an admin approves, recorded against the token that asked and the person who decided.
Your repository's deploy.yml stays as it is, and KamalCloud writes standard Kamal destination and secrets files beside it on the runner, run by the pinned official Kamal image. With those files and your own SSH access, Kamal works without KamalCloud.
The list that usually turns up after signup. It is here instead.
There is no support tier and no queue to escalate through. Mail goes to the team.
Ask a personRegister a machine, and read what the hardening panel says about it before you change anything.
Sign-ups are paused while the app is in maintenance.