Deployment.sh

Kamal alternative for teams that want a dashboard, roles and rollbacks

Kamal is a free, open source command line tool that deploys containerized apps to your own servers with zero downtime. Teams look for a Kamal alternative when deploys stop being one engineer's job: they need a shared dashboard, control over who can deploy, an audit trail, backups and one-click rollback. Deployment adds that layer on your own servers, from 49 USD a month.

plan.sh

$ deployment plan

Paste a repository and get a deploy plan

Paste a public GitHub or GitLab repository. We read only the manifests and store nothing beyond the plan.

Environment

Your servers stay in your own cloud account. No card needed for the demo.

See pricing

$ deployment plan

Building your deploy plan

$ deployment plan

$ deployment plan

Private repository or no stack found

Choose the framework and runtime and we build the full plan anyway.

Deployment and Kamal side by side

Both deploy to servers you own, and both avoid the per-service bills of a hosted platform. Kamal is a tool each engineer runs from a terminal against a config file in the repository. Deployment is a hosted panel where the team shares servers, sites, environments and history. The Kamal column below follows the Kamal documentation.

DeploymentKamal
FormHosted web panel plus git deploysOpen source command line tool
Price49 to 1 499 USD a month, half price billed yearly, plus your serversFree, plus your servers
Where deploys run fromThe panel and git push, no local setupAn engineer's machine or a CI job with the config and secrets
ReleasesHealth checked zero downtime releases and one-click rollback in the interfaceZero downtime deploys and rollback from the command line
PackagingNative runtimes for PHP, Node.js, Python, Rails, Go, Java, .NET and static sites, or Docker and composeDocker containers, any app that can be containerized
Teams and auditRoles (owner, admin, developer, viewer), per-server access and an audit log on Team and aboveNone built in, access is whoever holds the SSH key and secrets
BackupsScheduled database backups to your own S3 compatible bucketNot part of the tool
ServersStarter 3 servers and 15 sites, Team 15 servers and 100 sitesAs many as you list in the config

Who moves from Kamal and why

The typical buyer is a product team or small agency that adopted Kamal to leave a hosted platform, saved money, and then hit the limits of a tool with no interface. Three signs show up. A second and third engineer start deploying and the secrets file gets copied around. A client or auditor asks who shipped what and when. Or the one person who understood the setup is on holiday and nobody else wants to run a rollback from a terminal.

If that is you, the question is not whether Kamal works, it does. It is whether the 49 USD a month for Starter is cheaper than the hours spent maintaining the process around it, and most teams that count those hours find it is.

What changes on the bill

Kamal costs nothing, so a switch adds money. Your servers stay the same, at roughly 25 to 50 USD a month for a 8 GB, 4 vCPU machine, and Starter adds 49 USD a month (24 USD billed yearly), which covers 3 servers and 15 sites. Team at 199 USD covers 15 servers, 100 sites, 10 members, roles and an audit log. Review the plans and limits before choosing.

You are paying for time: shared access without sharing SSH keys, rollbacks anyone on the team can run, and backups that exist before the day you need one. If you are still comparing options, the self-hosted PaaS and Coolify alternative pages show how a panel differs from a tool you host yourself.

When Kamal is the better choice

Keep Kamal when one or two engineers deploy, the whole team is comfortable on the command line and a deploy.yml in the repository is exactly the process you want. Its price is hard to beat, the config travels with the code, and it avoids a hosted dependency. If you add a panel later, your servers and containers do not change. Our guide to zero downtime deployment explains what the health checked release does in either tool.

Move from Kamal in five steps

Your app keeps serving from the current setup until you switch DNS, so there is no downtime window.

  1. 1. Connect the servers

    Attach the servers you already deploy to over SSH, or create new ones in your cloud account from the panel. They need Ubuntu or Debian.

  2. 2. Add each repository

    Deployment detects the stack and offers a native runtime or Docker. A Dockerfile you already use for Kamal can stay.

  3. 3. Move the secrets

    Paste the values from your Kamal secrets into the encrypted environment per site, and check them against deploy.yml.

  4. 4. Deploy to a temporary domain

    Run the first release, watch the health check pass and test the app before any traffic moves.

  5. 5. Switch DNS

    Change the records, let the Let's Encrypt certificate issue and retire the laptop based deploy routine.

Kamal alternative questions

What is a good alternative to Kamal?

If you like Kamal's model of deploying to your own servers but need a shared interface, Deployment is a hosted panel that deploys from git to servers you own, with zero downtime releases, one-click rollback, an encrypted environment per site, backups to your S3 compatible bucket and roles on Team and above.

Is Kamal free?

Yes. Kamal is open source and costs nothing to use, and your only bills are the servers. What you pay for instead is the work around it: secrets handling, who may deploy, an audit trail, backups and keeping every laptop on the same version. Deployment charges 49 USD a month for Starter to cover that layer.

Does Deployment use Docker like Kamal?

Deployment runs apps natively for PHP, Node.js, Python, Rails, Go, Java, .NET and static sites, and also supports Docker and Docker Compose. You choose per site, so a Rails app that ships a Dockerfile can keep its container while other sites run natively.

Can I move from Kamal without downtime?

Yes. Connect the same servers over SSH or add new ones, add the repository, copy the values from your Kamal secrets into the encrypted environment, deploy to a temporary domain, test it, then switch DNS. The old Kamal setup keeps serving until you cut over.

When should I stay on Kamal?

Stay on Kamal when one or two engineers deploy, everyone is comfortable on the command line and a deploy.yml in the repository is the process you want. A panel earns its fee when more people deploy, when you need to prove who did what, or when handing off to non-engineers.

Keep your servers, give the team a dashboard

Run one repository through the demo, then connect a server and ship the first release.

Try the demo