Coolify and Dokploy are free, open-source, Docker-based control panels that turn your VPS into your own Heroku, Vercel or Netlify. Both install with a single curl command, deploy from Git, handle Docker Compose, support multi-server setups, and include database backups and notifications out of the box. But the choice is shape, not quality. Coolify puts every feature on every tier (with no paywalls anywhere) alongside the larger one-click catalogue. Dokploy starts with Docker Swarm clustering, and uses an open-core model where an Enterprise layer sits on top of an open base. We cover Coolify in detail in What Is Coolify?, so this comparison sticks to licensing, pricing, builds, databases, clustering and ops, side by side, then ends with HostList's verdict.
What is Dokploy, and how does it differ from Coolify?
Dokploy is a self-hostable deployment platform built on Docker Swarm and Traefik. You install it on your own server, connect a Git repository or Docker Compose file, and Dokploy builds and runs your app as a container, with built-in databases, backups and clustering across multiple servers. And Coolify does the same core job: it deploys apps and databases as Docker containers on servers you control. It connects to each server over SSH rather than Swarm, and ships with a much larger one-click catalogue. So both suit teams moving off a managed PaaS; the difference sits in the architecture and licensing (which the rest of this article covers).
| Dimension | Coolify | Dokploy |
|---|---|---|
| Licence | Apache-2.0, fully open source | Apache-2.0, except a /proprietary directory under its own licence (open-core) |
| Self-hosted cost | Free forever, no feature gating | Free base; self-hosted Enterprise tier is custom-priced |
| Cloud pricing | $5/month base (2 servers), +$3/month per extra server | Hobby $4.50/month per server (1 server); Startup from $15/month (up to 3 servers), +$4.50/month per extra |
| Minimum server | 2 CPU cores, 2GB RAM, 10GB disk | 2GB RAM, 30GB disk |
| Dashboard port | 8000 | 3000 (plus 80/443 for Traefik) |
| Build options | Nixpacks, Railpack, Dockerfile, Compose, static sites, prebuilt images | Nixpacks, Heroku Buildpacks, Dockerfile, native Compose (stack and compose modes) |
| Databases (one-click) | PostgreSQL, MySQL, MariaDB, MongoDB, Redis, KeyDB, Dragonfly, ClickHouse (8) | MySQL, PostgreSQL, MongoDB, MariaDB, libsql, Redis (6) |
| One-click catalogue | 360+ services (WordPress, Ghost, Supabase, n8n, Umami, Uptime Kuma, Ollama, Open WebUI) | Open-source templates incl. Supabase, Cal.com, PocketBase, Plausible (no published count) |
| Clustering | Multi-server via SSH; no Swarm-style cluster described | Docker Swarm cluster with worker/manager nodes |
| Log and metrics shipping | Axiom, New Relic, Highlight | Grafana (Loki/Prometheus/Mimir), Datadog, New Relic, InfluxDB, VictoriaMetrics, Better Stack, Elasticsearch/OpenSearch, Splunk, CloudWatch |
| GitHub stars (10 Nov 2026) | 65.7k stars, 5.9k forks | 38.2k stars, 3.1k forks |
How does the licensing and business model actually differ?
Coolify is Apache-2.0, full stop. The project describes itself as "open source and free forever," says there are no paywalled features and no investors, and says sponsors fund it. You get the whole self-hosted product with no limits (every feature unlocked), as confirmed on the Coolify homepage. Dokploy, copyright Dokploy Technology, Inc., is open-core. Its LICENSE file states that anything outside a /proprietary directory is Apache-2.0, and anything under /proprietary, if that directory exists in the repository, carries a separate proprietary licence. Dokploy's docs still call the project free and open source, and that fits the base product. But the distinction matters at the Enterprise tier, where Dokploy adds SSO/SAML, SCIM, audit logs, fine-grained RBAC and white labelling, and that tier can be self-hosted on-prem on a custom-priced plan. We won't guess which exact features live in that proprietary directory beyond what Dokploy states, because the docs don't list it line by line.
What does Coolify pricing look like next to Dokploy pricing?
Self-hosting both is free. But the optional cloud control plane is where the pricing splits, because both projects let you bring your own servers and pay only for the panel. Coolify Cloud is $5 a month including 2 servers, then $3 a month for each additional server, with unlimited deployments, teams and members (and nothing held back). Dokploy Cloud runs Hobby at $4.50 a month per server for a single-server setup with 1 user, 1 organisation, 2 environments, and one backup per database, then Startup from $15 a month for up to 3 servers plus $4.50 a month per extra server, adding unlimited users, environments and backups, basic RBAC with admin and developer roles, and 2FA.
The small-scale maths is clear. For 2 servers, Coolify Cloud comes to $5 a month; Dokploy Hobby comes to $9 a month for the same footprint. And for 3 servers, Coolify Cloud is $8 a month against Dokploy Startup at $15 a month. But that is not a pure server-count comparison, because Dokploy's Startup tier also includes team features that Hobby doesn't have (meaning you pay for team tooling alongside compute capacity). For a solo developer or a two-person agency running a couple of boxes, Coolify Cloud gets you comparable core features for less each month. Dokploy offers a 7-day free trial with no card required if you want to run the figures yourself.
What do the install and server requirements look like?
Both install with one command, and both expect you to lock down the dashboard quickly. Coolify's self-hosted install docs list a minimum of 2 CPU cores, 2GB RAM and 10GB free disk, on amd64 or arm64, with support for Debian, Ubuntu LTS, the Red Hat family, SUSE, Arch, Alpine and 64-bit Raspberry Pi OS. And the dashboard lands on port 8000, where the docs make one point plainly: create the admin account as soon as install finishes (because whoever registers first on that instance gets root on the server).
curl -fsSL https://cdn.coollabs.io/coolify/install.sh | bash
Dokploy's installation docs ask for at least 2GB RAM and 30GB disk (specifically so Docker builds don't freeze the box), and list testing on Ubuntu 18.04 through 24.04, Debian 10 through 12, Fedora 40, and CentOS 8 and 9. It needs ports 80 and 443 free for Traefik and port 3000 free for the dashboard, or the install fails. So Dokploy's own advice is to put a domain with HTTPS in front of it and then close direct IP:3000 access.
curl -sSL https://dokploy.com/install.sh | sh
Plain disclosure: both projects' docs recommend Hetzner as a hosting provider, and both publish referral links and list sponsors including Hetzner and Hostinger. But that is disclosure, not a performance claim (we are not citing either as faster or cheaper than the other, only noting the commercial relationship). If you're choosing a VPS to run either panel on, start with our VPS hosting rankings and the Hetzner provider profile alongside each project's recommendation.
How do build options and deployments compare?
Coolify supports Nixpacks, Railpack, Dockerfile, Docker Compose, static sites and prebuilt images. Dokploy supports Nixpacks, Heroku Buildpacks, Dockerfile and native Docker Compose, with both stack and compose modes. And both do preview deployments for pull requests (the feature many teams miss most when leaving Vercel or Netlify). Dokploy's docs specifically call out zero-downtime deployments and registry-based rollbacks. Coolify's docs describe instant rollbacks to previous builds. In practice, both aim at the exact same operational need: get a broken release out of the way before users notice. The projects describe it differently in their own docs, and we won't present one as quicker without a number to support that.
Which has more databases and one-click apps?
Coolify ships one-click PostgreSQL, MySQL, MariaDB, MongoDB, Redis, KeyDB, Dragonfly and ClickHouse, eight databases (with backups to any S3-compatible storage). Dokploy covers MySQL, PostgreSQL, MongoDB, MariaDB, libsql and Redis, six databases, with backups to external storage. On the wider catalogue, Coolify publishes a one-click service catalogue of more than 360 apps and templates, spanning WordPress, Ghost and Supabase through to automation and monitoring tools like n8n, Umami-style analytics, Uptime Kuma, Ollama and Open WebUI. So if you're considering self-hosting an automation tool like n8n on either panel, read our separate breakdowns on n8n pricing for self-hosted vs cloud and n8n vs Make vs Zapier before you allocate server capacity to it. Dokploy also offers open-source templates, including Supabase, Cal.com, PocketBase and Plausible, but its docs don't publish a total count, so we won't invent one for a tidier comparison.
Does Dokploy's Docker Swarm clustering actually matter for you?
This is where the tools split most clearly, more than pricing or catalogue size. Dokploy is built directly on Docker Swarm and Traefik, and its cluster documentation describes adding worker and manager nodes to scale horizontally. But that requires an extra server on the same CPU architecture and a Docker registry (Docker Hub, GHCR, DigitalOcean and ECR are all supported). Dokploy's own docs recommend vertical scaling, a bigger single server, before clustering, calling it faster and simpler, and they note that Dokploy does not automatically clean up storage on worker nodes, so you'll want to manage that yourself.
Coolify connects to each server over SSH and can deploy to one server or many, with the recommended layout being one dedicated Coolify server plus one or more workload servers. But Coolify's documentation does not describe a Swarm-style cluster with manager and worker roles. It is multi-server, not clustered (a different architectural design rather than a missing feature). If horizontal scaling across a real cluster is a near-term requirement, Dokploy's Swarm base is the more direct route. And if you expect to run one or two large boxes for the foreseeable future, Coolify's SSH-based multi-server model fits without the extra Swarm operating surface.
How do monitoring, logs and notifications compare?
Coolify covers monitoring, notifications to Discord, Telegram and email, log drains to Axiom, New Relic and Highlight, scheduled tasks, Cloudflare Tunnels, a browser terminal, 2FA, and SSO through GitHub, GitLab, Google, Azure and Authentik, all on the free self-hosted tier. Dokploy covers real-time CPU, memory, storage and network monitoring, ships logs and metrics to a longer list (Grafana via Loki, Prometheus or Mimir, Datadog, New Relic, InfluxDB, VictoriaMetrics, Better Stack, Elasticsearch or OpenSearch, Splunk and AWS CloudWatch), notifications to Slack, Discord, Telegram, email, webhooks, Lark, Gotify and Ntfy, plus a Traefik file editor for teams that want to hand-tune routing. So if your team already lives inside Grafana or Datadog dashboards, Dokploy's shipping options plug straight in without custom glue.
Which should you pick, Coolify or Dokploy?
Solo developer or small agency running one to a few servers who wants everything unlocked with no asterisks: go with Coolify. It costs less on Coolify Cloud at low server counts, gates nothing behind a higher tier, has the bigger catalogue, and needs less disk at the minimum spec (ideal for keeping budget VPS bills lean).
Team that expects to outgrow a single box and wants Swarm clustering with Traefik baked in, or needs metrics flowing into Grafana or Datadog: go with Dokploy. But keep a clear view of the open-core licence (specifically the Enterprise boundary) and the per-server cloud pricing once you scale past a single server.
Either way, the VPS underneath matters far more than the panel running on top of it. Size the server for your real build workload, not the control panel's minimum spec, and where you can, keep the panel off the box doing the heavy Docker builds (your deployment reliability will thank you). So compare providers on our VPS hosting rankings and Docker hosting rankings, check the Hetzner profile if either project's own recommendation caught your eye, and if you're still deciding whether to leave a managed PaaS at all, read Vercel alternatives for the wider market before you commit to self-hosting either tool.
Frequently asked questions
What is Dokploy, in plain terms?
Dokploy is a self-hostable, open-source deployment platform that runs on Docker Swarm and Traefik. You install it on your own server with a single curl command, then deploy apps, databases and templates as containers. And it includes built-in support for clustering across multiple servers (ready when your workloads need that extra headroom).
Which is the better Vercel or Heroku replacement, Coolify or Dokploy?
Both replace the core job those platforms do: Git push deploys, preview environments and one-click databases on servers you own. Coolify's edge is a bigger one-click catalogue and no feature gating at any tier. And Dokploy's edge is native Docker Swarm clustering and a wider range of metrics destinations. So the decision comes down to your operating model: pick Dokploy if multi-node clustering is on your immediate roadmap (with Traefik routing included), or Coolify if you want every feature and one-click template ready to deploy from day one.
Can I switch from Coolify to Dokploy, or the reverse, without rebuilding everything?
Both run standard Docker containers underneath, so neither creates hard technical lock-in. Coolify states explicitly that running resources keep working if the Coolify instance itself goes down (because they remain ordinary containers). And Dokploy states the same principle, no vendor lock-in, since what it deploys is also just Docker. Moving between panels still means recreating your app, database and domain settings in the new panel and restoring data from backups, but your application code does not change.
Is Dokploy's Enterprise tier worth it over the free self-hosted version?
It depends on whether you need SSO/SAML, SCIM, audit logs, fine-grained RBAC or white labelling. Those come with Dokploy's custom-priced Enterprise tier, which can also be self-hosted on-prem. But if you're a solo developer or small team, the free self-hosted base already covers Git deploys, Compose, clustering and database backups. Enterprise only earns its keep once strict corporate compliance or client-facing multi-tenancy enters the picture.
Follow HostList for new rankings, original research, and changes across the hosting industry.



