Install
Markdown
Ask AI
Share

Self-hosted PaaS compared: six tools, one fair table (2026)

Coolify, Levelrail, Dokploy, CapRover, Dokku and Kamal side by side: approach, license, multi-server, interfaces and stated RAM, with a source for each claim.

Markdown
Ask AI
Share

Coolify, Dokploy, CapRover, Dokku and Kamal all put your apps on a server you own, and they do it in different ways. Some are dashboards, one is a git remote, one is a CLI. This page puts the facts for six tools in one table, with a link to the official source for each claim.

We make Levelrail, so read its section with that in mind. We kept the claims about every tool to what its own repository and docs say, and where a doc is silent the table says “not stated”. For a per-feature view with sources, see the compare pages and the alternatives page.

Summary table#

ToolApproachLanguageLicenseMulti-serverInterface and APIMinimum RAM stated in docs
CoolifyDashboard over Docker, SSH to serversPHPApache-2.0Yes, needs a registry and your own load balancerDashboard, API, CLI, MCP server2 GB
LevelrailOne Go binary, agents on each nodeGoApache-2.0BetaDashboard, CLI, API, MCP server1 GB boots, no minimum benchmarked
DokployDashboard over Docker, Traefik, SwarmTypeScriptApache-2.0 with additional termsYes, Docker Swarm and remote serversDashboard, CLI, API, MCP server2 GB
CapRoverDashboard over Docker Swarm, NginxTypeScriptApache-2.0 with additional termsYes, Docker SwarmDashboard, CLI, HTTP API1 GiB
DokkuGit remote on one host, buildpacksShellMITOptional k3s schedulerCLI over SSH1 GB
KamalCLI that deploys over SSHRubyMITYes, needs a registry and a load balancerCLINot stated

The Dokploy and CapRover licenses are Apache-2.0 with additional terms. Read the Dokploy license file and the CapRover license file before you fork or redistribute either one.

Coolify#

Coolify deploys from a Git repository, a Dockerfile, a Compose file or a prebuilt image, and lists 360+ one-click services in its README. It reaches your servers over SSH, so there is nothing to install on them beyond Docker. Self-hosted gets every feature at no cost, per its pricing page.

On several servers, its multi-server docs say extra servers do not spread traffic by themselves, so you bring a load balancer, and images move through a registry. Its installation docs ask for 2 CPU cores and 2 GB of RAM.

It fits people who want a dashboard with a large service catalog.

Levelrail#

Levelrail is one Go binary. Per its README, the control plane idles at about 200 MB of RAM (measured in docs/performance.md), there are 570+ templates in the catalog and 346 of them have a recorded real-engine pass. You can drive it from the dashboard, the CLI, the HTTP API or 259 MCP tools, and it is Apache-2.0 with one edition.

What is built in: metrics and full-text log search, one-click rollback with pinned images, readiness-gated deploys, preview environments for pull requests, scheduled jobs, managed databases with scheduled backups, IAM policies, passkeys and TOTP, and an audit log with a verifiable hash chain. Agents on extra nodes dial out over mTLS, so they need no inbound ports. It also has two person deploy approvals, deploy freeze windows, a public status page and apps that sleep when idle and wake on the next request. A read-only live demo is online, and each feature carries a stable, beta or experimental label in its feature status.

It fits one or a few servers where you want metrics, rollback, an audit log and an API or agent in the same binary.

Dokploy#

Dokploy has native Docker Compose support, Traefik routing, a template list of 600+ and database backups to external storage, per its README. For several servers it uses Docker Swarm and remote servers, and its MCP server exposes its API endpoints as tools.

Its remote server docs say build servers push to a registry and handle Applications only, not Compose. Part of the code sits under a separate proprietary license (see above). Its installation docs ask for 2 GB of RAM and 30 GB of disk.

It fits teams that already think in Swarm and want a dashboard with an official MCP server.

CapRover#

CapRover has a web GUI and a CLI, runs on Docker Swarm, uses an Nginx template for load balancing and issues free Let’s Encrypt certificates, per its README. Its get started guide asks for 1 GiB of RAM and 5 GiB of disk, the lowest stated figure among the dashboards here.

Its Docker Compose support imports only part of the format and is marked experimental. The setup guide assumes Ubuntu and a wildcard DNS record. The license appendix restricts changes to its paid features.

It fits a handful of apps on a Swarm-based panel.

Dokku#

Dokku calls itself a Docker powered mini-Heroku, per its README. You deploy with a git push to a dokku remote. Heroku buildpacks are the default, and it also takes a Dockerfile or an image, with nginx, Caddy, HAProxy, Traefik or OpenResty as the proxy, per its docs.

You drive it from the command line over SSH. Its web UI and JSON API are only in the paid Dokku Pro, per its Pro page. Multi-server uses the k3s scheduler, which is marked new, needs a registry and lacks some commands.

It fits one server and a terminal, with no control plane service to keep up.

Kamal#

Kamal deploys over SSH from your machine with kamal setup and kamal deploy, builds from your Dockerfile and uses kamal-proxy for zero-downtime cutover, per its site. It started as the Rails deploy tool, and 37signals says it moved HEY and its other apps to its own hardware with it. It is MIT licensed and has no paid tier.

A registry is required, and per its installation docs several servers need a load balancer in front. Its proxy docs say automatic Let’s Encrypt works only for single-server deploys, and with several hosts you provide a certificate. It is CLI only, with no dashboard.

It fits teams that want the fewest moving parts and no server-side software.

Also worth a look#

Haloy is a Go tool with a CLI and a REST API.

How to choose#

  • One server and you want a dashboard: Coolify, Dokploy, CapRover or Levelrail.
  • Many servers: Coolify, Dokploy, CapRover (Swarm), Dokku (k3s) and Kamal each take a different route. Plan for a registry and a load balancer where noted above.
  • A Rails shop: Kamal.
  • You want git push and nothing else: Dokku.
  • You want an API or an agent to drive it: Levelrail, Dokploy and Coolify all list an MCP server.
  • You want an audit log, IAM policies and deploy approvals in one free edition: Levelrail.

Read each project’s own docs before you commit.

If you want to see Levelrail before installing it, open the read-only demo or read the code at github.com/glincker/levelrail. The Coolify comparison covers the closest match in detail.

Frequently asked questions#

Which self-hosted PaaS is the best?

It depends on how many servers you run and what interface you want. Dokku is a git remote on one host. Kamal is a CLI with no control plane. Coolify, Dokploy and CapRover are dashboards over Docker. Levelrail is one Go binary with metrics, rollback, an audit log and an API built in. The how to choose section lists them by situation.

Which of these runs on the smallest server?

CapRover and Dokku state 1 GiB and 1 GB of RAM in their docs, and Coolify and Dokploy state 2 GB. Levelrail's control plane idles at about 200 MB and its install page says 1 vCPU and 1 GB boots Docker and the control plane. Kamal states no figure.

Which of these tools can manage more than one server?

Coolify, Dokploy and Kamal manage several servers, and Coolify and Kamal need a registry and your own load balancer. CapRover uses Docker Swarm. Dokku does it through an optional k3s scheduler. Levelrail supports it as a beta feature.

Next steps

Keep reading

Leaving Vercel? Self-host it instead Leaving Vercel? Self-host it instead

comparison 6 min read

Self-Hosted Vercel and Heroku Alternatives, Compared

Coolify, Dokploy, CapRover, Dokku and Levelrail next to Vercel, Heroku and Railway: what each does well, where it fits, and which to pick for your setup.

  • Self-hosting
  • Comparison
  • PaaS