Dokploy: minimum requirements, install and pricing

Dokploy's installation guide asks for at least 2 GB of RAM and 30 GB of disk, and ports 80, 443 and 3000 must be free before you run the installer. The docs say the specification is there to cover Docker's resource use during builds and to prevent system freezes. That's why the disk figure is three times Coolify's.

Below: what the installer puts on your server, what Dokploy does, how the licence splits, and what the hosted version costs.

#What Dokploy is

Dokploy is a self-hosted deployment platform built on Docker and Traefik, and it installs Docker Swarm. You point it at a Git repo, a Docker image or a Compose file. It builds, deploys, routes a domain and gets a certificate. You manage all of it from a web panel on port 3000 until you put it behind your own domain.

The Dokploy Cloud docs spell out what self-hosting means: everything runs on one server. The UI, its PostgreSQL database, Redis, Traefik and your applications all live on the same machine. That's fine for small setups. As you grow, the management layer competes with your workloads for RAM. The two ways out are to add remote servers or to move the control plane to Dokploy Cloud.

#Requirements in detail

Distros Dokploy says it has tested: Ubuntu 24.04, 23.10, 22.04, 20.04 and 18.04; Debian 12, 11 and 10; Fedora 40; CentOS 9 and 8.

The installer also handles a few awkward setups, per the docs:

• Proxmox LXC containers are detected automatically, and the installer switches Swarm to dnsrr endpoint mode.
• Minimal kernels without IPVS (the docs name ZimaOS and other Buildroot-based images) need ENDPOINT_MODE=dnsrr set by hand.
• CIDR clashes with a cloud VPC can be avoided by passing DOCKER_SWARM_INIT_ARGS with a different address pool.
• Multiple network interfaces: set ADVERTISE_ADDR to pick which IP Swarm uses, for example a WireGuard address.

The docs don't state a CPU minimum or an architecture list on the install page, so this profile doesn't claim one.

#Installing it

The standard install is one line:

curl -sSL https://dokploy.com/install.sh | sh

Then open http://your-server-ip:3000 and create the admin account. A few things from the guide:

• Updating uses the same script: curl -sSL https://dokploy.com/install.sh | sh -s update.
• Pinning a version: don't set DOKPLOY_VERSION to an old release. Use the install.sh attached to that GitHub release instead, because the main script always targets the latest setup.
• With sudo, pass variables inline. sudo resets the environment, so a variable you exported in your own shell never reaches the script.
• Lock it down afterwards. Once your panel domain has working HTTPS, the docs recommend removing the port 3000 publish with docker service update --publish-rm "published=3000,target=3000,mode=host" dokploy. Do it only after HTTPS works, or you'll lock yourself out.

#Features

From the features page and the plan comparison:

• Build types: Nixpacks, Railpack (marked new in the docs, described as Nixpacks' successor), Dockerfile, Heroku Buildpacks, Paketo Buildpacks and Static. The Heroku Buildpacks option is handy if you're moving off Heroku.
• Sources: GitHub, plain Git or a Docker image for apps. GitHub, Git or raw YAML for Compose.
• Docker Compose as either plain Compose or a Swarm stack.
• Databases: MySQL, PostgreSQL, MongoDB, Redis and MariaDB, with manual and scheduled backups.
• Per-app monitoring: CPU, memory, disk and network graphs, real-time logs and deployment logs.
• Traefik controls: domains, redirects, security headers and raw Traefik config.
• Also listed: preview deployments, one-click templates, watch paths, multi-server support, build servers, zero-downtime deployments, registry-based rollbacks and scheduled jobs.

#Licence: mostly Apache-2.0, with an asterisk

The repository's LICENSE.MD puts everything under Apache-2.0, except code in a /proprietary directory. That code falls under LICENSE_PROPRIETARY.md, the Dokploy Source Available License 1.0, which allows production use only with a commercial agreement.

In practice, the Enterprise docs list SSO (OIDC/SAML), SCIM provisioning, application authentication, custom roles, audit logs and whitelabeling as Enterprise features, enabled by a licence key. The core deploy-and-run features are open source. Keep the split in mind if you're comparing it with a tool whose whole codebase is under one licence.

The latest release from the GitHub API is v0.30.7, published 2026-09-18. The repo had 37,556 stars as of 2026-09-29 and is written mainly in TypeScript.

#Pricing (Dokploy Cloud)

Self-hosted Dokploy costs nothing. The pricing page (2026-09-29) covers Dokploy Cloud, where Dokploy hosts the control plane and you connect your own servers:

The page shows a 20% discount for yearly billing and a 7-day free trial with no card required. The Cloud docs say your code and data stay on your servers, and Dokploy only runs the orchestration.

#Who should pick Dokploy

Dokploy suits you if you like Swarm as the foundation, want Heroku-style buildpacks alongside Nixpacks, and want resource graphs in the panel without bolting on a separate tool. It's a weaker fit on a tiny 1 GB VPS, since the docs' own floor is 2 GB and 30 GB of disk. It's also a weaker fit if you need SSO without paying for Enterprise.

For the direct comparison, see /compare/coolify-vs-dokploy. The Coolify profile is at /software/coolify, and the wider shortlist is at /best/self-hosted-paas.

This is a profile built from Dokploy's documentation and repository. It is not a hands-on review.