NewOut Plane raises funding, backed by Maza VenturesRead the announcement
Back to Blog
Comparison

Coolify vs Dokploy (2026): Which Should You Self-Host?

Recep Erdoğan••12 min read
Coolify vs Dokploy (2026): Which Should You Self-Host?

Coolify vs Dokploy in short: pick Coolify if you want the older, larger project. It started in 2021, has about 66,000 GitHub stars, runs more one-click database engines and lets you choose Traefik or Caddy as its proxy. Pick Dokploy if you want to spread apps across several servers: its installer sets up Docker Swarm and its cluster mode is part of the current product, while Coolify now marks Swarm as deprecated. Both are free, open source and self-hosted, so you run the servers either way. If neither fits, compare the wider list of Coolify alternatives, self-hosted and managed.

Coolify and Dokploy answer the same question: how do you get a Heroku-style deploy experience on a server you rent? Both are open source, both install onto your own Linux machine with one command, and both let you deploy from Git or a container image and get a running app behind HTTPS. If you are shopping for a self-hosted Docker PaaS in 2026, these two names come up first.

They are not identical, though. They differ in age, architecture, build options, database coverage and how they handle more than one server. And there is a cost neither project puts on its landing page: the hours you spend keeping the platform itself alive. This guide compares Coolify and Dokploy across setup, features and maintenance, then lists the other self-hosted tools people weigh against them.

What Coolify and Dokploy Actually Are

Coolify and Dokploy are self-hosted platform-as-a-service tools. You install one of them on a Linux server you already rent, and it gives you a web dashboard for deploying applications, provisioning databases, and managing domains and TLS certificates on top of Docker. In the NIST definition of cloud service models, a PaaS lets you deploy your own applications onto managed infrastructure without provisioning servers yourself. The twist with these two is that you are the one providing and managing that infrastructure. The software gives you the PaaS interface; you supply and maintain everything below it.

Coolify is the older and larger project. Its repository dates from January 2021, it is written in PHP on Laravel, and it is licensed Apache-2.0. Traefik is its default reverse proxy, and Caddy is a built-in option. Dokploy started in April 2024. It is written in TypeScript with a Next.js interface, and it is licensed Apache-2.0 except for files in a /proprietary folder, which have their own license. Its installer initializes Docker Swarm on the server and runs Traefik for routing.

Why Teams Compare These Two

Most people arrive at this comparison after the same realization: managed platforms are convenient but the bill grows, and a plain VPS is cheap but gives you nothing but an empty Linux box. Coolify and Dokploy sit in the middle. You rent a server, install the tool once, and get push-to-deploy, one-click databases, automatic certificates and a dashboard, all for the price of the server plus your time.

The comparison usually comes down to four questions. Which is easier to install and keep running? Which supports the languages, databases and workflows I use? Which handles more than one server? And what does it actually cost me over a year, once I count the maintenance? The sections below answer each in turn.

Quick Comparison: Coolify vs Dokploy

FactorCoolifyDokploy
Project start20212024
GitHub starsAbout 66,000About 38,000
Latest releasev4.7.5 (November 10, 2026)v0.31.0 (November 5, 2026)
Core stackPHP / LaravelTypeScript / Next.js
LicenseApache-2.0Apache-2.0, plus a separately licensed /proprietary folder
Reverse proxyTraefik (default) or CaddyTraefik
Build methodsNixpacks, Railpack (beta), Dockerfile, Docker Compose, StaticNixpacks, Railpack, Buildpacks, Dockerfile, Static, plus Docker Compose
One-click catalog (self-reported)360+ services600+ templates
DatabasesPostgreSQL, MySQL, MariaDB, MongoDB, Redis, Dragonfly, KeyDB, ClickHouse, SQLite (experimental)Postgres, MySQL, MariaDB, MongoDB, Redis
Scheduled database backupsTo S3, SFTP, FTPS or WebDAV; not for Redis, Dragonfly or KeyDBTo an S3 destination
More than one serverSeveral servers behind your own load balancer; Docker Swarm is experimental, deprecated and set for removal in v5Swarm cluster mode; needs a Docker registry and nodes of the same architecture
Minimum server2 CPU cores, 2 GB RAM, 10 GB disk2 GB RAM, 30 GB disk
Hosted control planeCoolify Cloud: $5/month for 2 servers, $3/month per extra serverDokploy Cloud: from $4.50/month per server, 7 day free trial
Who runs and patches the serversYouYou

Facts checked on 11 November 2026 against Coolify pricing, the Coolify docs, Coolify on GitHub, Dokploy pricing, the Dokploy docs and Dokploy on GitHub. Star counts and catalog sizes are the projects' own numbers and are not counted the same way.

The most important row is the last one, and it is the same for both: the servers are yours. Even with the hosted control plane, Coolify's Cloud docs say you still handle operating system updates, firewall policy, application data and backups, and Dokploy Cloud likewise deploys to servers you bring. Whichever you pick, you become the operator of a Linux host, a Docker engine and the PaaS software on top.

Setup and Installation

Both tools install with a single shell command on a fresh Linux server:

bash
# Coolify (needs root or sudo)
curl -fsSL https://cdn.coollabs.io/coolify/install.sh | bash

# Dokploy (installs Docker if missing and initializes Docker Swarm)
curl -sSL https://dokploy.com/install.sh | sh

# Afterward, for either tool:
#   1. Point a wildcard DNS record at the server's IP
#   2. Open the dashboard and create the first admin user
#   3. Connect a Git source and add SSH keys
#   4. Harden the box: firewall, SSH, unattended upgrades

Coolify asks for at least 2 CPU cores, 2 GB of RAM and 10 GB of free disk on amd64 or arm64 Linux, and supports a wide range of distributions. Dokploy asks for at least 2 GB of RAM and 30 GB of disk, has been tested on Ubuntu, Debian, Fedora and CentOS, and needs ports 80, 443 and 3000 free before it installs. In both cases installation is the easy part. Wiring DNS, hardening SSH, configuring backups and keeping the host patched is where the real time goes, and that work is the same whichever project you chose.

One thing worth stating plainly: running an installer as root and exposing a control panel to the internet means the security of your whole platform depends on how diligently you patch it. That is true for Coolify and true for Dokploy. It is the price of self-hosting, not a flaw in either tool.

Features Compared

Builds. Both deploy from a Git repository or a prebuilt container image. Coolify builds with Nixpacks, Railpack (in beta), a Dockerfile, a Docker Compose file or as a static site. Dokploy offers Nixpacks, Railpack, Buildpacks, a Dockerfile or a static build, and handles Docker Compose stacks as their own resource. If your app already has a Dockerfile, either tool builds it the same way.

Docker Compose. Both run multi-service Compose stacks. Dokploy lists native Compose support among its headline features, and Coolify treats a Compose file as one of its build packs. Teams that think in docker-compose.yml files will be at home in either.

Databases. Coolify runs more engines from its dashboard: PostgreSQL, MySQL, MariaDB, MongoDB, Redis, Dragonfly, KeyDB, ClickHouse and SQLite (experimental). Dokploy covers Postgres, MySQL, MariaDB, MongoDB and Redis. In both, the database is a container on your own server, so upgrades, restores and capacity planning stay with you.

Backups. Coolify schedules engine-aware backups for PostgreSQL, MySQL, MariaDB, MongoDB, ClickHouse and SQLite, and uploads them to S3 compatible storage, SFTP, FTPS or WebDAV. Redis, Dragonfly and KeyDB are not covered, so you use each engine's own persistence for those. Dokploy runs automated database backups to an S3 destination you configure. In both cases, testing a restore is your job.

One-click services. Coolify advertises 360+ one-click services and Dokploy 600+ templates. The counts are self-reported and include different kinds of entries, so treat them as "large catalog" for both and check that the apps you need are there.

More than one server. This is the clearest difference today. Coolify's docs label Docker Swarm support experimental and deprecated, say it will be removed in Coolify v5, and recommend multi-server deployments behind an external load balancer for new setups. Dokploy initializes Swarm at install time and offers a cluster mode with manager and worker nodes. It needs a Docker registry, extra servers of the same architecture, and its own cleanup jobs on workers, and its docs suggest scaling vertically first.

Monitoring. Coolify's Sentinel agent reports container state and disk use, and collects CPU and memory history when metrics are turned on. Dokploy shows CPU, memory, storage and network use per resource and can alert on server CPU and memory thresholds; its monitoring docs mark parts of this as Cloud only. For request tracing or long-term metrics, you add your own stack on top of either.

Hosted control plane. Coolify Cloud hosts the Coolify control plane for $5/month with 2 server slots and $3/month per extra server, and each extra team needs its own subscription. Dokploy Cloud Hobby is $4.50/month per server for 1 server, 1 user and 2 environments; Startup starts at $15/month for up to 3 servers and unlimited users; Enterprise adds SSO and SAML, SCIM and audit logs. Dokploy Cloud has a 7 day free trial without a credit card, and both offer 20% off yearly billing.

The Maintenance Cost Nobody Prices In

The headline appeal of Coolify and Dokploy is that the software is free. The software is free. The infrastructure and the operating are not. This is the line item that decides whether self-hosting actually saves you money, and it is the one both projects are quietest about.

Here is the honest total cost of ownership for either tool over a year:

  • The server. A production-capable VPS runs from a low monthly fee upward, and you need more than one if you want the platform separate from your workloads or any redundancy.
  • Security patching. The host OS, the Docker engine, the reverse proxy and the PaaS software itself all receive security updates. Applying them, and reacting when a vulnerability in the control panel is disclosed, is manual work with real urgency because the panel is internet-facing.
  • Upgrades. Both projects ship often. Coolify released v4.6.0 and v4.7.0 a week apart in November 2026, each with a breaking changes section, and Dokploy is still before 1.0. Reading release notes before you upgrade is part of the job.
  • Backups and recovery. Scheduled dumps are built in, but a backup you have never restored is a guess. Testing restores, and recovering when a disk fails, are on you.
  • Your time. This is the big one. For an engineer whose time is worth a meaningful hourly rate, even a few hours a month of infrastructure work is hundreds of dollars of opportunity cost, every month, indefinitely.

A tool that costs zero in license fees can cost more per year than a paid platform once you price the server and the hours honestly. Self-hosting wins on cost when you already have the servers, already have the operational muscle, and have a strict reason to keep data on hardware you control. It loses when the free software quietly turns a developer into a part-time sysadmin. Our self-hosted apps in Docker guide walks through the same reasoning for individual apps.

Other Self-Hosted Options

Coolify and Dokploy are the best known, but five other self-hosted tools come up in the same searches. Each takes a different approach:

  • Komodo. A GPL-3.0 web app for managing servers, builds, deployments and Docker Compose stacks, with a small agent on each host and no limit on how many servers you connect. It does not present itself as a PaaS, so it suits people who already write Compose files and want one place to run them across many machines.
  • Easypanel. A self-hosted PaaS panel on Docker Swarm with 845 one-click installers. It is free for up to 3 projects; paid licenses are per server, from $10.90/month on annual billing, and database backups start on the paid Hobby plan.
  • Kamal. An MIT licensed CLI from 37signals that deploys containers to your servers over SSH, with zero-downtime switches through kamal-proxy. There is no dashboard and no control plane to keep running.
  • CapRover. A free PaaS built on Docker, nginx, Let's Encrypt and Docker Swarm that runs on as little as 1 GiB of RAM. Our CapRover alternative guide covers when to move off it.
  • Dokku. MIT licensed, Heroku-style git push on a single server, with official plugins for Postgres, MySQL, Redis and many other datastores, and an optional $849 Dokku Pro license for a web UI. See the Dokku alternative guide.

Prices, trade-offs and a "choose it if" for each, along with managed platforms, are in our guide to self-hosted and managed Coolify alternatives.

If You Would Rather Not Run Servers

Every tool above leaves you as the operator of the host. A managed platform removes that layer. With Out Plane, you deploy from a Git push on GitHub or a Docker image, and the platform runs the servers. Managed PostgreSQL 14 to 18 comes with automated backups, point-in-time recovery, read replicas and connection pooling, in 8 regions with Frankfurt as the default, for $6 per database. Redis, MySQL and MongoDB run as one-click templates that you operate.

The trade-offs are real. Apps run in one region in Germany, you set the instance count yourself with no autoscaling, and there is no free plan. Starter is $9/month and Pro is $29/month, both with a 14 day free trial, and compute is billed per minute. See /pricing for current numbers.

When to Choose Which

Choose Coolify when you want the longer track record and the larger community, need engines such as Dragonfly, KeyDB or ClickHouse, prefer Caddy to Traefik, or want backups sent to SFTP or WebDAV as well as S3.

Choose Dokploy when you want Swarm clustering as part of the current product, like building with Buildpacks, or want a hosted control plane with per-server pricing, a free trial and enterprise options such as SSO and SCIM.

Choose neither when you do not want to be the operator at all, or when a lighter tool from the list above fits better. If patching a control panel, testing database restores and hardening a Linux host are work you would rather not do, a managed platform is the better trade.

Frequently Asked Questions

Is Coolify or Dokploy better for beginners?

Coolify has the edge for beginners because of its larger community, about 66,000 GitHub stars against Dokploy's 38,000, which means more answered questions when you hit a problem. Both install with one command, and Dokploy is approachable too, especially if you already think in Docker Compose.

Is Dokploy a fork of Coolify?

No. They are independent projects with different codebases: Coolify is built on PHP and Laravel and started in 2021, while Dokploy is written in TypeScript and started in 2024. They solve the same problem and both use Docker and Traefik, but they share no code lineage.

Do Coolify and Dokploy give you managed databases?

Not in the fully managed sense. Both create database containers on your own server from the dashboard, and both can schedule backups to S3 compatible storage, though Coolify's scheduled backups skip Redis, Dragonfly and KeyDB. Upgrades, restore testing and recovery after a failure remain your responsibility.

Which one scales better across servers?

Dokploy, for now. Its installer sets up Docker Swarm and its cluster mode is part of the current product, though it needs a registry and same-architecture nodes. Coolify marks Swarm as experimental and deprecated, plans to remove it in v5, and recommends several servers behind an external load balancer instead.

Are Coolify and Dokploy free?

The software is free and open source for both. The hosted control planes are paid: Coolify Cloud is $5/month for 2 servers and Dokploy Cloud starts at $4.50/month per server. Either way you also pay for the servers and the time to patch, back up and operate them.

Can I move off self-hosting later without rewriting my app?

Yes. Because both tools deploy standard container images and Dockerfiles, an app that runs on Coolify or Dokploy runs on any platform that accepts a container. Moving means pointing the same Dockerfile or Git repository at the new platform and reconnecting your environment variables and database, not rewriting the application.

What is the biggest hidden cost of Coolify or Dokploy?

Your own time. Security patching, upgrades with breaking changes, backup verification and incident response are recurring monthly work, and for an engineer that is real opportunity cost every month. A tool with a free license can still cost more per year than a paid plan once you price those hours honestly.

The Verdict

Coolify and Dokploy are both good tools that do what they claim. Coolify is the more mature choice, with a bigger community, more database engines and a choice of proxy. Dokploy is the younger, fast-moving project with Swarm clustering built in, Buildpack support and a hosted control plane priced per server. Between the two, the decision comes down to track record and database coverage versus multi-server support.

The bigger decision is one step up: do you want to own the server at all? Both tools make you the operator of a Linux host, and that operating cost, in time and in risk, is the real price of self-hosting. When that cost is worth it, Coolify or Dokploy is a legitimate choice. When it is not, a managed platform gives you push-to-deploy without the maintenance.

Ready to skip the server entirely? Get started with Out Plane and start a 14 day free trial on Starter or Pro. See /pricing for plan details.


Tags

coolify
dokploy
paas
comparison
self-hosted
docker

Next steps


Related reading


Start deploying in minutes

Connect your GitHub repository and deploy your first application today. Start with a 14-day free trial.

Start 14-day free trial