Coolify and Dokploy: Self-Hosted PaaS on Your VPS

Published on | Updated

How to run your own Heroku-like platform on a VPS. Covers Coolify and Dokploy setup, deploying applications, and why self-hosted PaaS saves money.

A technician with a tablet in a data center aisle between rows of server racks

Heroku bills each app by its dynos: $7 a month for a Basic dyno and $25 for a Standard-1X (Heroku pricing, checked 31 October 2026). Vercel Pro costs $20 a month for one deploying seat with $20 of usage credit, plus on-demand usage beyond that credit and $20 for each extra seat that deploys (Vercel Pro plan, checked 31 October 2026). Or you can run your own platform on a VPS. Coolify and Dokploy put no licence cap on the number of apps you deploy: the CPU, RAM, disk and network of the server set the limit.

What is Self-Hosted PaaS?

Platform as a Service (PaaS) handles deployments, SSL, domains, and process management. Self-hosted PaaS gives you the same convenience on your own server.

FeatureHerokuVercelSelf-Hosted PaaS
Price (5 apps)$35 on Basic dynos, $125 on Standard-1X$20 platform fee, plus usage beyond the $20 creditOne VPS plan
Deploy from GitYesYesYes
Auto SSLYesYesYes
Custom domainsYesYesYes
DatabasesAdd-on, Heroku Postgres from $5Marketplace providers such as Neon, Upstash and SupabaseOn the same server
Docker supportYes, through Container RegistryBeta: a Dockerfile runs as a Vercel FunctionYes
Full server accessNoNoYes

Prices checked on 31 October 2026 on Heroku's pricing page and in Vercel's Pro plan docs. Heroku runs Docker images through its Container Registry. Vercel runs container images as Vercel Functions and says "The Container runtime is in beta on all plans" (Vercel KB); its databases come from providers in the Vercel Marketplace.

The trade-off is that you run the platform. For a self-hosted install, Coolify's docs are explicit: you install, update, back up, monitor and restore Coolify yourself, you secure the operating system, SSH access, firewall and network, and your apps, databases, volumes and secrets stay your responsibility. The same split applies to any PaaS you run on your own VPS, Dokploy included. Our Coolify backup guide shows what Coolify's built-in backups cover and how to restore them.

Coolify

Open-source, self-hosted Heroku alternative, under the Apache 2.0 licence (GitHub).

Installation

curl -fsSL https://cdn.coollabs.io/coolify/install.sh | bash

That's it. The installer sets up Docker Engine when your distribution supports it, then the web dashboard. Coolify needs 2 CPU cores, 2 GB RAM and 10 GB of disk to run, plus space for Docker images, volumes and backups. Create your admin account on port 8000 as soon as the installer finishes: Coolify's install docs warn that whoever reaches the registration page first becomes the instance admin with root access to your server. Then back up /data/coolify/source/.env, which you need to restore Coolify from a backup. Our Coolify migration guide shows what else to save when you move it to another server.

Features

FeatureIncluded
Git-based deploymentsYes (GitHub, GitLab, Bitbucket)
Docker supportYes
Database managementMySQL, PostgreSQL, MongoDB, Redis
SSL certificatesAutomatic (Let's Encrypt)
Custom domainsYes
Environment variablesYes
Deployment previewsYes
MonitoringBasic
BackupsDatabases, app volumes and directory mounts (4.3.0 and later), and Coolify's own data

Database backups cover PostgreSQL, MySQL, MariaDB, MongoDB, ClickHouse and SQLite, but not Redis, Dragonfly or KeyDB (database backups). Coolify 4.3.0 added scheduled backups of volumes and directory mounts (release notes, storage backups). The instance backup under Settings > Backup saves Coolify's own projects, resources, settings and deployment history, but not the APP_KEY in /data/coolify/source/.env that decrypts its stored secrets, so keep a copy of that file elsewhere.

Deploying an App

  1. Connect GitHub repository
  2. Select branch (main)
  3. Coolify detects the language (Node.js, Python, etc.) with the Nixpacks or Railpack build option
  4. Set environment variables
  5. Click Deploy

Coolify builds a Docker container, configures its proxy (Traefik by default, Caddy as an option), generates SSL, and your app is live.

Build Options

Coolify offers five ways to build an app (builds overview). Only Nixpacks and Railpack detect the project for you:

Build optionWhat it does
NixpacksDetects the language: Node, Python, PHP, Ruby, Go, Rust and the other language providers Nixpacks lists, including Staticfile
Railpack (Beta)"Railway's successor to Nixpacks", for Git-based apps only (Railpack)
StaticServes a repository that already holds the final HTML, CSS and JavaScript, without a build command (Static)
DockerfileBuilds an image from your Dockerfile, from a Git repository or stored in Coolify (Dockerfile)
Docker ComposeDeploys a Compose file from a Git repository or pasted into Coolify (Docker Compose)

Dokploy

A newer open-source alternative to Coolify, also built on Docker with Traefik in front.

Installation

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

Ports 80, 443 and 3000 must be free: Traefik takes 80 and 443, the dashboard opens on port 3000, and the installer fails if any of them is already in use (Dokploy installation).

Features

FeatureIncluded
Git deploymentsYes
Docker & Docker ComposeYes
Database managementYes
Auto SSLYes
Custom domainsYes
Monitoring dashboardBasic; the advanced dashboard comes only with Dokploy Cloud
Multi-server supportYes, remote servers (without monitoring on them)
Traefik reverse proxyBuilt-in

Dokploy's own comparison lists the self-hosted edition as free and puts its user, organization and backup caps on the Cloud plans only; SSO, audit logs and the other enterprise features need a licence, and the advanced monitoring dashboard is listed for the Cloud editions only (Dokploy editions). Remote servers run your apps on other machines, and remote server monitoring is "the only feature not supported" there (remote servers).

Dokploy vs Coolify

AspectCoolifyDokploy
GitHub repository sinceJanuary 2021April 2024
Latest release on 31 October 2026v4.5.3, 28 October 2026v0.30.10, 22 October 2026
Minimum server in its docs2 CPU cores, 2 GB RAM, 10 GB disk2 GB RAM, 30 GB disk
GitHub stars on 31 October 2026about 65,000about 38,000
Multi-serverYes, any server added over SSHYes, remote servers
LicenceApache 2.0Apache 2.0, plus paid enterprise features

Coolify connects to each extra server over SSH, after which "The server can then be selected as a deployment destination" (add a server). Release dates and stars come from each project's GitHub page (Coolify releases, Dokploy releases).

Cost Comparison

SetupMonthly costHow the bill grows
Heroku$7 per Basic dyno, $25 per Standard-1X dyno; Heroku Postgres from $5With every app and dyno
Vercel Pro$20 with one deploying seat and $20 of usage creditUsage beyond the credit on demand, plus $20 per extra deploying seat
Railway Hobby$5 including $5 of usage creditUsage beyond the credit per resource
VPS + Coolify/DokploySpace-Node Standard VPS-S €4.99 (3 vCores, 4 GB RAM, 60 GB NVMe)Only when you move to a bigger plan

Competitor prices were checked on 31 October 2026 on Heroku's pricing page, Vercel's Pro plan docs and Railway's pricing page; our VPS price is as of 31 October 2026. Those three list US dollars, and Vercel's prices exclude VAT, while ours is in euros including VAT, so convert before you compare. Standard VPS-S is the cheapest of our plans that meets the minimums of both Coolify and Dokploy (see Resource Requirements below).

For a Next.js app, our Vercel vs VPS comparison works out a Vercel Pro bill line by line, with extra seats, the CDN tier and usage beyond the $20 credit.

How the Bills Grow

Five small apps on Heroku come to 5 times $7, so $35 a month, on Basic dynos, or 5 times $25, so $125, on Standard-1X, before any database. On a VPS the five apps share one plan, and whether they fit depends on what each one uses, not on a price per app. That is where self-hosting saves money: the bill only grows when the server runs short and you move to a bigger plan. What you pay instead is your own time for the work in the trade-off section above.

Resource Requirements

PlatformMinimum from its docs
Coolify2 CPU cores, 2 GB RAM, 10 GB free disk, plus room for Docker images, volumes and backups
Dokploy2 GB RAM, 30 GB disk

There is no fixed number of apps per GB of RAM. A static site or a small API needs far less than a Next.js build or a busy database, and builds need extra headroom: Coolify's docs warn that high resource use from builds on the same server as Coolify can make the server unresponsive, and Dokploy sizes its minimum for the resources Docker uses during builds. Start at or above the minimum, watch CPU, RAM and disk use as you add apps, and move to a bigger plan when one of them runs short.

A Space-Node VPS is a KVM server with full root access, NVMe storage, dedicated RAM and shared vCores in an EU data center, so you can install Coolify or Dokploy yourself and run whatever your stack needs within the CPU, RAM and disk of your plan. Backups of the VPS are not part of the plan price (you can arrange them through a support ticket), which is one more reason to send Coolify's backups to S3.

Sources

All opened on 31 October 2026: