Amazon Web Services
KamalCloud builds EC2 servers in your AWS account, in the region you choose, hardens them and runs Kamal against your repository. AWS bills you directly.
Create an IAM user in the AWS console, without console access.
Give it AmazonEC2FullAccess, and AWSPriceListServiceFullAccess if you want costs.
Create an access key and paste both halves into KamalCloud, with the region to build in.
Pick a machine type, location and image from the connection's catalog, with prices. The machine is created in your own AWS 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.
AmazonEC2FullAccess to build and manage servers, and AWSPriceListServiceFullAccess if you want KamalCloud to show what they cost. The user needs no console access.
The one you give when you connect. A connection aims at one region, so a second region is a second connection.
No. Servers are EC2 instances, and your app runs on them as ordinary Kamal containers behind kamal-proxy.
No. Servers are created in your own AWS account and AWS bills you for them, at its own price. KamalCloud never resells infrastructure.
Paste an access key, 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.