# Best self-hosted PaaS in 2026: which should you pick? > The best self-hosted PaaS: Ployz for GitHub deploys to several servers your agent runs, Coolify for Compose, Dokku to replace Heroku. All free. Published 2026-10-02, updated 2026-11-15, by Nick Potts. For agents: [llms.txt](https://ployz.dev/llms.txt) indexes the Ployz docs as Markdown. **TL;DR:** Ployz to deploy from GitHub to your own servers, one or many, with a free hosted dashboard your coding agent can run. Coolify to run Docker Compose files as they are. Dokku to replace Heroku on one server. None of the six needs Kubernetes. Coolify, Dokploy, Dokku, CapRover, Kamal and Ployz are free on your own servers, so on one server you pay only for the server, about **$7 to $10 a month** for 4 GB: - **Pick Ployz if** you deploy from GitHub to servers you rent and want a preview for every pull request, one app across several servers without Kubernetes, and a dashboard you don't have to host. It's free on any number of servers, and your coding agent can run it through `ployz mcp`, with anything risky waiting for your approval. Have a Compose file? Your agent turns each container into a Ployz service. - **Pick Coolify if** your app is a Docker Compose file and you want built-in S3 backups, hundreds of templates, free team roles and GitLab, Bitbucket or Gitea support. - **Pick Dokploy if** you want Coolify's feature set with one app spread across servers through Docker Swarm. - **Pick Dokku if** you're leaving Heroku with a Procfile app, live in a terminal, and one server is enough. - **Pick CapRover if** you want a simple dashboard over a Docker Swarm cluster and will back up databases yourself. - **Pick Kamal if** your deploy should be a config file in your repo, with nothing running on the server but your app. A self-hosted PaaS is software you install on a server you rent, so you get Heroku- or Vercel-style deploys without paying a platform for compute. You push code, it builds a container, puts it behind HTTPS and restarts it when you push again. If you're moving after a possible credential exposure, use the [PaaS migration and secret rotation checklist](https://ployz.dev/blog/railway-migration-secrets) before copying any environment variables. ## How do the six compare? "Multi-server" here means your apps can run across more than one machine, not only that one dashboard can see several servers. Stars and latest release are from GitHub on 21 October 2026. | | Best for | License | Price on your server | Web UI | Multi-server | Compose files | Database backups | PR previews | GitHub | |---|---|---|---|---|---|---|---|---|---| | [Coolify](https://coolify.io) | Compose apps on one or two servers | Apache-2.0 | Free; Cloud $5/month | Yes | Yes, but no traffic spreading, and not for Compose apps or volumes | Yes | Yes, to S3 | Yes (GitHub, GitLab, Bitbucket, Gitea) | [63.3k stars, v4.4.6, 9 Oct](https://github.com/coollabsio/coolify/releases) | | [Dokploy](https://dokploy.com) | Compose apps across servers with Swarm | Apache-2.0 core, plus a source-available folder | Free; Cloud $4.50/server | Yes | Yes, through Docker Swarm | Yes | Yes, to S3 | Yes, GitHub only | [37.9k stars, v0.30.8, 29 Sep](https://github.com/Dokploy/dokploy/releases) | | [Dokku](https://dokku.com) | Leaving Heroku, one server, a terminal | MIT | Free; Dokku Pro UI $849 once | Paid (Dokku Pro) | Only through its k3s scheduler | No | Through plugins, to S3 | Through its GitHub Action | [32.2k stars, v0.38.31, 27 Sep](https://github.com/dokku/dokku/releases) | | [CapRover](https://caprover.com) | A simple dashboard over Swarm | Apache-2.0 with an appendix | Free | Yes | Yes, Docker Swarm | Partial, experimental | No, settings only | No | [15.2k stars, v1.15.4, 30 Aug](https://github.com/caprover/caprover/releases) | | [Kamal](https://kamal-deploy.org) | A config file in your repo, nothing else | MIT | Free | No | Yes, servers listed in a config file | No | No | No | [14.7k stars, v2.12.0, 18 Jun](https://github.com/basecamp/kamal/releases) | | [Ployz](https://ployz.dev) | GitHub deploys to several servers, run by your agent | CLI and server software Apache-2.0, dashboard AGPL-3.0 | Free on any number of servers | Yes | Yes, private network and a load balancer on every server | Your agent turns each container into a service | Yes, a restore point for every database | Yes, GitHub only | [v0.2.4, 11 Oct](https://github.com/getployz/ployz/releases), new | All six are actively maintained. The oldest latest release is Kamal's from June, and Kamal is also the smallest, so there's less to change. ## Coolify Coolify is the most-starred of the six: a free web dashboard for apps, databases, backups, logs and templates. It needs 2 GB of RAM ([install](https://coolify.io/docs/get-started/installation)). - **Multi-server:** Coolify runs copies on several servers, but "adding deployment servers does not distribute traffic by itself," and it "does not create a complete highly available system." Multi-server doesn't support Compose apps, and Coolify blocks a second server when an app has persistent storage ([multiple servers](https://coolify.io/docs/knowledge-base/server/multiple-servers)). You rent or build the load balancer. - **Compose:** full Compose files, from Git or pasted in, with proxy labels added for you. But "Rolling updates are not supported for Docker Compose applications" ([rolling updates](https://coolify.io/docs/knowledge-base/rolling-updates)), so Compose apps restart on deploy. - **Templates:** 386 Compose templates on 21 October ([templates](https://github.com/coollabsio/coolify/tree/main/templates/compose)). - **Backups:** scheduled S3 backups for Postgres, MySQL, MariaDB, MongoDB and ClickHouse, not Redis ([backups](https://coolify.io/docs/databases/backups)). Volume backups arrived in [4.3.0](https://github.com/coollabsio/coolify/releases/tag/v4.3.0). - **Previews:** one per pull request on GitHub, GitLab, Bitbucket or Gitea, with the address posted back on the pull request ([previews](https://coolify.io/docs/applications/ci-cd/github/preview-deploy)). - **Zero-downtime:** waits for a health check, except for Compose apps and previews. - **Teams:** free team roles, including a read-only Member role ([4.3.0](https://github.com/coollabsio/coolify/releases/tag/v4.3.0)), and OpenID Connect single sign-on and a team audit log since [4.4.0](https://github.com/coollabsio/coolify/releases/tag/v4.4.0). - **Upkeep:** 70 published security advisories, 21 of them critical ([advisories](https://github.com/coollabsio/coolify/security/advisories)). 4.3.0 shipped breaking changes to roles and the API, and 4.4.0 changed how multi-server setups work, so read changelogs before you update. - **Price:** free self-hosted with "full access to all features"; Coolify Cloud is optional ([pricing](https://coolify.io/pricing)). Where it falls short: traffic spreading across servers is your job, and Compose apps restart on every deploy. My full review is in [Coolify review](https://ployz.dev/blog/coolify), and how it lines up against Ployz is in [Coolify vs Ployz](https://ployz.dev/vs/coolify). ## Ployz Ployz is built for coding agents on your own servers: a dashboard, CLI and `ployz mcp` that deploy from GitHub to servers you rent, where every deploy, restart or delete your agent asks for waits for you to approve. It grows from one server to several without Kubernetes. It needs 2 GB of RAM on the server, because builds run there. ```sh ployz up --server root@your-server ``` That installs Ployz on a Linux server with systemd, builds the current directory and gives it an HTTPS address. - **Multi-server:** add a server with one command. It joins an encrypted WireGuard network, services reach each other at `NAME.internal`, and every server runs its own Caddy load balancer, so there's none to rent. A service can run up to 50 replicas, and a database moves to another server with seconds of downtime. - **Compose:** Ployz doesn't run the file itself. Your coding agent reads it and adds each container as its own service, databases as one-click Ployz databases. - **Templates:** one-click Postgres, MySQL, Redis and MongoDB, plus any Docker image. - **Backups:** a restore point for every database. Restore it, or move the database to a bigger server. - **Previews:** one per pull request at its own HTTPS address, GitHub only, unlimited on your own servers. Save a preview's settings and they go live with the merge. - **Zero-downtime:** once you set a health check, the new version must pass it before the old one stops. Services with a volume (databases) have a short gap instead. - **UI:** your whole app on one canvas with live status. Dashboard edits are staged and reviewed before they deploy, and an AI agent in the dashboard answers questions and can restart or change services. - **Monitoring:** metrics for every service and server, searchable logs and crash emails, with nothing to install. - **Teams:** unlimited members with Owner, Admin and Member roles. - **Outside dependency:** deploys go through Ployz Cloud. You can [self-host Ployz Cloud](https://ployz.dev/docs/self-hosting), but it still uses Ployz's relay and hosted DNS. - **Coding agents:** `ployz mcp` gives Claude Code, Codex or Cursor 55 tools, and anything risky waits for you. - **Price:** free on any number of servers, with custom domains and the hosted dashboard included. ## Dokploy Dokploy is the closest rival to Coolify: a similar free dashboard with a larger template catalog and a real cluster mode. It needs 2 GB of RAM ([install](https://docs.dokploy.com/docs/core/installation)). - **Multi-server:** remote servers each run apps on their own. To spread one app, the cluster mode is Docker Swarm with managers, workers and a registry for images ([cluster](https://docs.dokploy.com/docs/core/cluster)). - **Compose:** full Compose files, from Git or pasted in. - **Templates:** 586 blueprints on 21 October ([templates](https://github.com/Dokploy/templates/tree/main/blueprints)). - **Backups:** databases and named volumes to S3 ([backups](https://docs.dokploy.com/docs/core/databases/backups)), and it can back up itself. - **Previews:** GitHub only and off by default. Dokploy warns against them on public repos "since external people can execute builds and deployments in your server" ([previews](https://docs.dokploy.com/docs/core/applications/preview-deployments)). - **Zero-downtime:** needs a Swarm health check you add per app. - **Extras:** scheduled jobs and rollbacks. - **Teams:** SSO, custom roles and audit logs sit in a `/proprietary` folder that needs a paid agreement in production ([license](https://github.com/Dokploy/dokploy/blob/canary/LICENSE.MD), [pricing](https://dokploy.com/pricing)). - **Upkeep:** 60 published security advisories, 34 of them critical ([advisories](https://github.com/Dokploy/dokploy/security/advisories)). Where it falls short: spreading across servers means running Swarm and a registry, and team features cost money. More in [Dokploy review](https://ployz.dev/blog/dokploy) and [Coolify vs Dokploy](https://ployz.dev/blog/coolify-vs-dokploy). ## Dokku Dokku is the closest copy of Heroku: `git push`, a Procfile and buildpacks, driven from the command line. It needs 1 GB of RAM ([install](https://dokku.com/docs/getting-started/installation/)). - **Multi-server:** Dokku "runs on a single server of your choice" ([docs](https://dokku.com/docs/getting-started/installation/)). Its [k3s scheduler](https://dokku.com/docs/deployment/schedulers/k3s/) joins more nodes, at 2 GB per node, which means you're now running Kubernetes. - **Compose:** no. - **Backups:** through plugins; the official [Postgres plugin](https://github.com/dokku/dokku-postgres) schedules S3 backups. - **Previews:** its [GitHub Action](https://github.com/dokku/github-action) creates and destroys review apps. - **Extras:** cron built in. - **UI:** none for free. Dokku Pro is $849 once and covers 1 production server plus 2 pre-production servers ([pro.dokku.com](https://pro.dokku.com/)). - **License:** MIT. Where it falls short: one server unless you take on Kubernetes, and a teammate needs a terminal and server access to help. More in [Dokku review](https://ployz.dev/blog/dokku), and the costs of leaving Heroku are in [Heroku alternatives](https://ployz.dev/alternatives/heroku). ## CapRover CapRover is a simple web dashboard on top of Docker Swarm, with "dozens" of one-click apps. - **Multi-server:** "Add nodes to your Docker Swarm cluster and let CapRover handle load balancing" ([caprover.com](https://caprover.com/)). - **Compose:** partial and experimental. It "does not implement the complete Compose specification" and ignores fields like `build`, `networks` and `deploy` ([docs](https://caprover.com/docs/docker-compose.html)). - **Backups:** it backs up its own settings in `/captain/data/`. For databases it says to use "the proper method of backup for your specific database, like `mongodump`" ([backup docs](https://caprover.com/docs/backup-and-restore.html)). - **Previews:** no. - **License:** Apache-2.0 with an appendix asking that changes to free features stay open ([LICENSE](https://github.com/caprover/caprover/blob/master/LICENSE)). Where it falls short: no database backups, no previews, and Compose files only half work. ## Kamal Kamal is a deploy tool from Basecamp, not a dashboard: a `deploy.yml` in your repo and a CLI on your laptop. - **Multi-server:** you list server IPs in `deploy.yml` and it deploys to all of them. - **Compose:** no. - **Backups:** no. Databases run as accessories, which "are not updated when you deploy, and they do not have zero-downtime deployments" ([accessories](https://kamal-deploy.org/docs/configuration/accessories/)). - **Previews:** no. - **Zero-downtime:** out of the box for your app. - **UI:** none, by design. - **License:** MIT. Where it falls short: everything beyond deploying is yours, and nobody without a terminal can help. In return it leaves the least running on your server. ## What does a self-hosted PaaS cost? The tools cost nothing on one server of your own, so the bill is the server. Start on **4 GB** so builds and databases have room. | Server | Specs | Monthly price | Source | |---|---|---|---| | Netcup VPS 500 | 2 vCPU, 4 GB RAM, 64 GB SSD, traffic included | €8.26 incl. VAT (12-month term) | [netcup VPS](https://www.netcup.com/en/server/vps) | | Netcup VPS 1000 | 4 vCPU, 8 GB RAM, 128 GB SSD | €14.50 incl. VAT (12-month term) | [netcup VPS](https://www.netcup.com/en/server/vps) | | Hetzner CX23 (Germany, Finland only) | 2 vCPU, 4 GB RAM, 40 GB | $6.49 + about $0.60 IPv4 | [Hetzner price list](https://docs.hetzner.com/general/infrastructure-and-availability/price-adjustment/) | | Hetzner CX33 (Germany, Finland only) | 4 vCPU, 8 GB RAM, 80 GB | $9.99 + about $0.60 IPv4 | [Hetzner price list](https://docs.hetzner.com/general/infrastructure-and-availability/price-adjustment/) | In the US, Netcup's Manassas datacenter costs about €1 more a month. The hosted dashboards are optional, on monthly billing: | Tool | 1 server | 3 servers | 5 servers | Source | |---|---|---|---|---| | Coolify, self-hosted | $0 | $0 | $0 | "Full access to all features" ([pricing](https://coolify.io/pricing)) | | Coolify Cloud | $5 | $8 | $14 | $5 covers 2 servers, then $3 each ([pricing](https://coolify.io/pricing)) | | Dokploy, self-hosted | $0 | $0 | $0 | [License](https://github.com/Dokploy/dokploy/blob/canary/LICENSE.MD) | | Dokploy Cloud | $4.50 (Hobby, 1 user) | $15 (Startup) | $24 (Startup) | Startup includes 3 servers, then $4.50 each ([pricing](https://dokploy.com/pricing)) | | Dokku | $0 | $0 | $0 | Dokku Pro UI: $849 once, covers 1 production and 2 pre-production servers ([pro.dokku.com](https://pro.dokku.com/)) | | CapRover, Kamal | $0 | $0 | $0 | Open source, no paid tier | | Ployz | $0 | $0 | $0 | Free on any number of servers ([pricing](https://ployz.dev/pricing)) | Coolify's and Dokploy's clouds take 20% off for yearly billing. Ployz's hosted dashboard is free on any number of servers. Compare that with a hosted platform, where you pay for each service, seat and gigabyte; I broke that down fee by fee in [the hidden costs of PaaS](https://ployz.dev/blog/paas-pricing). My first month on Laravel Cloud was about $600. Railway was $500+ a month and climbing, mostly from one busy database. Today one dedicated server at €80 a month runs more than I ever ran on Railway. Check what your platform charges in [Railway pricing](https://ployz.dev/blog/railway-pricing), [Render pricing](https://ployz.dev/blog/render-pricing) or [Vercel pricing](https://ployz.dev/blog/vercel-pricing). ## Which self-hosted PaaS should you pick? Pick by the one thing you can't work around: | If you need… | Pick | |---|---| | A Compose file run unchanged, and templates | Coolify or Dokploy | | Scheduled database backups to S3 | Coolify or Dokploy | | Single sign-on, an audit log, or GitLab, Bitbucket or Gitea | Coolify | | One app spread across servers, with a full dashboard | Dokploy (Swarm) or Ployz (no Swarm) | | A Heroku-style `git push` from the terminal | Dokku | | A simple dashboard over Swarm | CapRover | | A config file and nothing else on the server | Kamal | | Previews for every pull request plus multi-server without Kubernetes | Ployz | | A coding agent that runs your servers, with every risky action waiting for your approval | Ployz | **Pick a hosted platform instead if** you never want to own a server and your app is small enough that the bill stays low. I compared those on the same app in [the best Vercel alternatives](https://ployz.dev/blog/vercel-alternatives). ## Where Ployz fits I build Ployz because I wanted a self-hosted PaaS that grows past one server without Kubernetes or Swarm. [Adding a server is one command](https://ployz.dev/features/multiple-servers). Your servers share a private network, and each one serves https itself. You don't rent a load balancer. It's built for your coding agent. Paste `Read ployz.dev/agents.md and deploy this repo to my server.` into Claude Code, Codex or Cursor. Every deploy, restart or delete your agent asks for waits for you to approve. Every pull request gets a preview at its own https address. Ployz is free on any number of servers, hosted dashboard included. [Connect your agent and deploy on your own server](https://ployz.dev/auth/github). ## FAQ ### Which self-hosted PaaS works with Claude Code or Codex? Ployz, if you want your coding agent to run your servers without being able to delete them. `ployz mcp` gives Claude Code, Codex or Cursor 55 tools, and every deploy, restart or delete your agent asks for waits for you to approve to approve it. Coolify and Dokploy have official MCP servers too, but a delete is decided by the API token: Coolify grants it with a `delete` permission ([MCP setup](https://coolify.io/docs/mcp/setup)), and Dokploy's 508 tools run on whatever its API key allows ([Dokploy MCP](https://github.com/Dokploy/mcp)). ### Is a self-hosted PaaS a real Heroku or Vercel replacement? For the deploy workflow, yes: push to Git, get a build, HTTPS and previews. You won't get a global edge network or managed databases with point-in-time restore. If your app is a few services and a database, you gain far more in price than you lose. Dokku is the closest to Heroku; Coolify, Dokploy and Ployz are closest to Vercel's preview-per-pull-request workflow. ### Which self-hosted PaaS replaces Heroku without Kubernetes? Dokku, if one server is enough: it keeps Heroku's `git push`, Procfile and buildpacks. If you need more than one server, Ployz and Kamal spread an app across them without Kubernetes, while Dokploy and CapRover use Docker Swarm and Dokku's own multi-server mode is k3s. What the move saves you, and the steps, are in [Heroku alternatives](https://ployz.dev/alternatives/heroku). ### Coolify or Dokploy: which should you choose? Coolify, if your app runs on one or two servers and you want single sign-on, an audit log or GitLab support for free. Dokploy, if you want one app spread across servers through Docker Swarm and a bigger template catalog. Both run Compose files and back up databases to S3. I compared them in detail in [Coolify vs Dokploy](https://ployz.dev/blog/coolify-vs-dokploy). ### Coolify or Easypanel? Coolify, unless you prefer Easypanel's interface and will pay for it. Self-hosted Coolify is free with "full access to all features" ([pricing](https://coolify.io/pricing)). Easypanel's free plan covers up to 3 projects; database backups need its Hobby plan at $10.90 per server a month, and multiple users need Growth at $16.90 ([pricing](https://easypanel.io/pricing)). Both need 2 GB of RAM, and Easypanel sets up Docker Swarm on install ([docs](https://easypanel.io/docs)). ### Who should use a self-hosted PaaS? I think it fits a solo developer or small team running a few web apps, workers and databases whose hosting bill has grown past the price of a server. It fits less well if you never want to SSH into anything, or run one tiny static site that a free tier covers. ### Which self-hosted PaaS runs Docker Compose files? Coolify and Dokploy run full Compose files as they are. CapRover's support is partial and experimental. On Ployz, your coding agent reads the Compose file and adds each container as a Ployz service, so the file doesn't have to run unchanged. Dokku and Kamal don't take Compose files. If a Compose app has outgrown one server, I compared the ways to spread it in [Docker Compose across multiple servers](https://ployz.dev/blog/docker-compose-multiple-servers). ### Which self-hosted PaaS backs up my database? Coolify and Dokploy back up databases to S3 on a schedule, and Dokku does through its database plugins. Ployz keeps a restore point for every database, and you can restore it in a click. CapRover and Kamal leave database backups to you. Whichever you pick, test a restore; as Coolify's own docs put it, "A successful backup only proves that Coolify created a file." ### How much maintenance does a self-hosted PaaS take? More than a hosted platform, less than a hand-built server. You update the PaaS itself. These tools hold root SSH access to your servers, so update promptly, keep the dashboard port firewalled and keep accounts few. ### Do I need anything outside my server? Self-hosted Coolify, Dokploy, CapRover, Dokku and Kamal need nothing outside your server. Ployz deploys through Ployz Cloud, even when you self-host it, so if a fully self-contained setup matters to you, that's a point for the others. ## How I checked I checked every fact on 1 October 2026 and again on 21 October against each project's own pricing page, docs, license and GitHub repo, linked next to each claim. Where a limit comes from a project's docs, I quote it. I haven't run these six side by side for this article, so there are no install times or idle RAM numbers here. Server prices come from Netcup's and Hetzner's own price pages. I didn't test Coolify's or Dokploy's MCP servers; the agent answers come from their docs. Let your coding agent deploy to your own server with Ployz, free: [get started](https://ployz.dev/auth/github).