DigitalOcean
KamalCloud builds servers in your DigitalOcean team, hardens them and runs Kamal against your repository. DigitalOcean bills you for the machines, at its own price.
Open the API page in the DigitalOcean control panel.
Generate a personal access token with both read and write scopes.
Paste it into KamalCloud. Nothing is created until you ask for it.
Pick a machine type, location and image from the connection's catalog, with prices. The machine is created in your own DigitalOcean account.
Firewall, SSH lockdown, fail2ban and unattended upgrades, read back off the server every time you open the page.
The official Kamal image runs against your repository from GitHub, GitLab, Gitea or Bitbucket. Deploy on a push to a branch or tag, once you turn it on.
Databases and volumes, scheduled, to buckets you control, with restore and download. Deleting an app, environment or server backs them up first.
Certificates issued and renewed, and DNS checked against what is actually resolving.
Spend estimated from the provider's own price list, per server, with idle resources flagged.
No. Servers are created in your own DigitalOcean account and DigitalOcean bills you for them, at its own price. KamalCloud never resells infrastructure.
A personal access token with both read and write scopes, generated on the API page of the DigitalOcean control panel. It is encrypted at rest and never shown again.
The machine is destroyed at DigitalOcean, disk and all. Its databases and volumes are backed up first, and if a backup can't be taken, nothing is deleted. Disconnecting the team is different: it removes KamalCloud's record of the machines and destroys nothing.
Yes. An account can hold as many connections as it likes, including several to the same provider, each with its own keyring and server names.
Paste a token, then build a server when you are ready. Nothing is created until you ask for it.
Sign-ups are paused while the app is in maintenance.