Dokploy alternatives

The best Dokploy alternatives for deploying apps and databases to a VPS in 2026

Dokploy, Coolify, CapRover, Dokku, and Kamal all get an app onto a VPS. They differ in what you have to keep running afterwards. This comparison covers server requirements, databases, backups, and the alternative nobody lists: not self-hosting the PaaS at all.

Nouva Team 11 min read

If you are searching for a Dokploy alternative, you have probably already decided against renting compute from Railway, Render, or Vercel. You want your apps and databases on a $5 VPS you control. The open question is which tool sits between your GitHub repository and that server, and how much of that tool becomes your job.

Dokploy, Coolify, and CapRover answer it the same way: install the whole platform on the server, open a dashboard on port 3000, and keep it patched. Dokku and Kamal drop the dashboard and give you a CLI. Nouva takes a third route. The control plane is hosted, your server runs a small open-source agent, and everything it creates is plain Docker on hardware you own.

The quick answer

Pick the tool by what you want to maintain

Use Nouva when you have one server and want GitHub deploys, managed databases, scheduled backups, logs, and metrics without running a PaaS on that server. Pick Dokploy for Docker Compose and Swarm, Coolify for its one-click catalog and ARM64 support, CapRover for a proven app store on a tiny box, Dokku when you prefer the terminal, and Kamal when deployment should be a config file in your repo.

Connect your Linux server to Nouva
$ curl -fsSL 'https://api.nouva.sh/install-agent.sh' | sh -s -- --api-url 'https://api.nouva.sh' --server-id '<server-id>' --token '<one-time-token>'

The dashboard generates this command with a real server id and a one-time token. It installs Docker if needed and starts the agent container. Nothing else is installed until you deploy something.

Connect your server free Read the getting started guide

Side-by-side

Dokploy alternatives compared

Checked against each project's official documentation on September 3, 2026. Requirements and pricing change, so every competitor name links to its source.

Nouva

Where the PaaS runs
Hosted by Nouva; only the agent, Traefik, and BuildKit run on your server
Minimum server
2 GB RAM, any Linux server
Managed databases
PostgreSQL, MySQL, MongoDB, Redis
Backups
pgBackRest with PITR for Postgres; scheduled MySQL, MongoDB, and Redis archives
Price
Free, one server per workspace

Dokploy

Where the PaaS runs
Self-hosted on the same server (port 3000), or Dokploy Cloud
Minimum server
2 GB RAM, 30 GB disk
Managed databases
PostgreSQL, MySQL, MariaDB, MongoDB, Redis, libsql
Backups
Database backups to S3-compatible destinations
Price
Free self-hosted; Cloud from $4.50/mo per server

Coolify

Where the PaaS runs
Self-hosted on the same server, or Coolify Cloud
Minimum server
2 cores, 2 GB RAM, 30 GB disk
Managed databases
PostgreSQL, MySQL, MariaDB, MongoDB, Redis, and more
Backups
Scheduled database backups to S3-compatible storage
Price
Free self-hosted; Cloud $5/mo for 2 servers

CapRover

Where the PaaS runs
Self-hosted container on the same server (port 3000)
Minimum server
1 GB RAM recommended; 512 MB may fail builds
Managed databases
Via one-click apps
Backups
Manual, per app
Price
Free, open source

Dokku

Where the PaaS runs
CLI on the server; no web UI
Minimum server
1 GB RAM, Ubuntu 22.04/24.04 or Debian 11+
Managed databases
Via official plugins
Backups
Plugin export commands you schedule yourself
Price
Free, open source

Kamal

Where the PaaS runs
Runs from your laptop or CI over SSH; no dashboard
Minimum server
Any Docker host reachable over SSH
Managed databases
Accessories you define in a config file
Backups
Not included
Price
Free, open source

The part the install script hides

Self-hosting the PaaS is a second workload

Every self-hosted PaaS starts the same way: a login page after one curl | sh. Dokploy's installer, for example, sets up Docker, initializes Docker Swarm, starts Traefik, and opens the dashboard on port 3000.

Dokploy self-hosted install
$ curl -sSL https://dokploy.com/install.sh | sh

That is a great first hour. The cost arrives later, as a list of things that now live on your production server and depend on you:

  • Memory before your first app. Dokploy and Coolify both publish a 2 GB minimum, and the dashboard, its database, and the proxy consume part of it permanently. Community sizing guides for both tools recommend 4 GB or more for real workloads.
  • An admin surface on the public internet. Port 3000 is the way in for you and for anyone scanning for it. Locking it behind a firewall, VPN, or the proxy is your task.
  • Upgrades of the tool itself. A PaaS release that breaks the dashboard breaks your ability to deploy fixes, on the same machine that serves customers.
  • Backing up the platform, not just the data. Your app databases are one backup job. The PaaS configuration is another one you have to remember to write.

Both Dokploy and Coolify sell hosted control planes for exactly this reason. Dokploy Cloud starts at $4.50 per month per server, and Coolify Cloud is $5 per month for two servers. Nouva was built hosted from day one, and it is free.

Why Nouva is different

A hosted control plane for one server you own

Nouva is deliberately narrower than a cluster manager. It connects one customer-owned server per workspace and runs as many projects, apps, and databases on it as that server can hold. That constraint is what lets the rest stay simple.

  • Nothing to self-host except your apps

    The dashboard, API, job queue, and control-plane database run on Nouva's infrastructure. Your server runs the open-source agent, Traefik, and BuildKit. There is no PaaS to upgrade, back up, or expose on port 3000.

  • GitHub push to production

    Link a repository and branch. Nouva detects Node.js, Python, Go, or a Dockerfile, builds the image on your server, and releases once health checks pass. Every deployment keeps its build log, and rollbacks come straight from the history.

  • Managed PostgreSQL, MySQL, MongoDB, and Redis

    Pick a version, reserve storage, and cap CPU or memory only if you want to. Connection strings are injected into your services as environment variables, with private URLs inside the project and public URLs for external clients.

  • Backups you do not have to script

    PostgreSQL uses pgBackRest with WAL archiving for point-in-time recovery. MySQL, MongoDB, and Redis get scheduled verified archives. Restores are staged first and applied on purpose, and none of it counts against your 10 GB of object storage.

  • An HTTPS URL before you touch DNS

    Every app gets a hostname under up.nouva.cloud through the hosted edge the moment it deploys. Custom domains point straight at your server IP, and the Traefik runtime on your server issues Let's Encrypt certificates over HTTP-01.

Nouva at a glance

2 GB

smallest supported server

4

managed database engines

7 / 30

days of logs / metrics

10 GB

object storage per workspace

Runtime logs are kept for 7 days and metrics for 30. Backups keep their own retention and do not count against the 10 GB of customer-created buckets. There is no paid tier. Read the getting started guide for the full setup.

Walkthrough

Deploy an app and a database to a VPS in four steps

  1. 01

    Create a server record

    Sign in with GitHub, add a server, and copy the generated install command. The one-time registration token expires, so the command is safe to paste once and forget.

  2. 02

    Run one command on your Linux server

    The script installs Docker if it is missing, raises the file-watch limits Traefik and BuildKit need, and starts the agent container. The agent then reconciles Traefik on your server after its first heartbeat.

  3. 03

    Add an app and a database

    Create a project, link a GitHub repository, and add a PostgreSQL service next to it. The database credentials land in your app's environment automatically.

  4. 04

    Push and watch it go live

    Every push to the branch builds and deploys. Open the generated up.nouva.cloud URL, stream the runtime logs, then attach a custom domain when you are ready.

Environments separate dev, staging, and production inside a project, each with its own services, variables, and deployments. Preview deployments get isolated variables and domains and are cleaned up when they are no longer needed. The deployments guide covers build detection, health checks, and rollbacks in detail.

The established options

Where each Dokploy alternative earns its place

Dokploy: Compose-first, Swarm-ready

Dokploy describes itself as a free, self-hostable PaaS for applications and databases. It leans on native Docker Compose, manages PostgreSQL, MySQL, MariaDB, MongoDB, Redis, and libsql, and can scale across nodes with Docker Swarm. The installation docs ask for at least 2 GB of RAM and 30 GB of disk, Ubuntu, Debian, Fedora, or CentOS, and free ports 80, 443, and 3000. If you want Compose files as the unit of deployment and a self-hosted UI, Dokploy is a strong choice. If you do not want to run the UI, Dokploy Cloud charges per server.

Coolify: the biggest catalog

Coolify is the most widely deployed open-source Dokploy alternative, and it is Apache-2.0 licensed. Its README leads with static sites, databases, full-stack apps, and 280+ one-click services. The installation requirements are 2 cores, 2 GB of RAM, and 30 GB of free disk on AMD64 or ARM64, across Debian, Red Hat, SUSE, Arch, Alpine, and Raspberry Pi OS. Choose Coolify when the catalog and distribution coverage matter more than a light footprint. Coolify Cloud exists for people who would rather not host the panel.

CapRover: small, stable, dated

CapRover has been around since 2018 and still runs happily on a 1 GB instance, with the getting started guide warning that 512 MB may not survive builds. It needs ports 80, 443, and 3000, and a wildcard DNS record pointed at your server before HTTPS works. Its one-click app store is mature, but database backups are something you arrange per app, and the interface shows its age.

Dokku: git push, no dashboard

Dokku is the original single-server Heroku clone. The install docs list Ubuntu 22.04 or 24.04 or Debian 11+ with 1 GB of RAM on the Docker scheduler. Databases come from official plugins, backups are export commands you schedule, and there is no web UI. That is a feature for some teams and a dealbreaker for others.

Kamal: deployment as a config file

Kamal, from 37signals, is not a PaaS at all. It is a CLI that SSHes into any Docker host, pulls your image, and swaps containers with zero downtime. Databases are accessories you declare, there is no dashboard, and there are no backups. It is the right pick when the team wants everything in the repository and already has a build pipeline.

Honest constraints

When Nouva is not the right Dokploy alternative

  • You need more than one server per workspace, Docker Swarm, or any multi-node clustering.
  • You want the control plane itself on hardware you own, fully air-gapped from any vendor.
  • You need wildcard custom domains, MongoDB restores, or a one-click catalog of hundreds of prebuilt services today.

None of these are hidden. Nouva connects one server per workspace on purpose, and the control plane is hosted rather than self-hostable. If your requirement is a fully self-hosted panel or a multi-node cluster, Dokploy or Coolify is the better fit.

Bottom line

Which Dokploy alternative should you choose?

  • Choose Nouva for one VPS, GitHub deploys, managed databases with real backups, and no PaaS to maintain on the box.
  • Choose Dokploy for Docker Compose stacks, Swarm multi-node, and a self-hosted UI you are happy to run and upgrade.
  • Choose Coolify for the biggest one-click service catalog, ARM64 support, and the widest distribution coverage.
  • Choose CapRover for a proven, lightweight app store on a 1 GB server where a dated UI is acceptable.
  • Choose Dokku for git push deploys with no web UI and full control from the terminal.
  • Choose Kamal for a team that wants deployments described in a config file and driven from CI or a laptop.

FAQ

Questions developers ask about self-hosted PaaS tools

What is the best alternative to Dokploy?+

It depends on what you want to maintain. Coolify is the closest self-hosted alternative with a larger service catalog. CapRover and Dokku are lighter and older. Kamal is a CLI for teams who prefer configuration files. Nouva is the option when you want the dashboard, GitHub deploys, managed databases, and backups without hosting the PaaS on the server yourself.

Is Dokploy free?+

Yes. Dokploy is free to self-host. Dokploy Cloud, where Dokploy runs the control plane for you, starts at $4.50 per month per server on the Hobby plan.

Dokploy vs Coolify: which should I choose?+

Both install on the same server, need at least 2 GB of RAM and 30 GB of disk, and use Traefik for routing. Coolify has the bigger one-click catalog and supports more Linux distributions and ARM64. Dokploy is younger, leans on Docker Compose and Docker Swarm, and has a simpler interface. Either way you are responsible for upgrading and securing the PaaS itself.

How much RAM does a self-hosted PaaS need?+

Dokploy and Coolify both publish a 2 GB minimum, but the dashboard, database, and proxy they install consume part of that before your first deployment. CapRover and Dokku run on 1 GB. Nouva keeps the control plane off your server, so a nominal 2 GB VPS keeps about 1.25 GiB for one app plus one managed database.

Can I deploy apps and databases to a VPS without managing a PaaS?+

Yes. Nouva runs the dashboard, API, and job queue on its own infrastructure. You run one command on your Linux server, which installs Docker if needed and starts the open-source agent. The agent then builds from GitHub, provisions PostgreSQL, MySQL, MongoDB, or Redis, and runs backups on your server.

Does Nouva lock me into its platform?+

Your apps, databases, volumes, and Traefik routes are ordinary Docker resources on your own server. Custom domains point directly at your server IP, so Nouva is not in the request path. If you stop using Nouva, the containers keep running where they are.

Which databases do these tools manage?+

Dokploy manages PostgreSQL, MySQL, MariaDB, MongoDB, Redis, and libsql. Coolify manages a similar set plus more through its catalog. Nouva provisions PostgreSQL 15 to 18, MySQL 8.0 and 8.4, MongoDB 7 and 8, and Redis 7.0 to 7.4, and injects the connection strings into your services as environment variables.

Which option has the best database backups?+

For PostgreSQL, look for point-in-time recovery rather than nightly dumps. Nouva uses pgBackRest with WAL archiving for PostgreSQL PITR, plus scheduled logical archives for MySQL, MongoDB, and Redis, with staged restores you apply on purpose. Dokploy and Coolify schedule database dumps to S3-compatible storage.

What are the limits of Nouva compared with a self-hosted PaaS?+

Nouva connects one server per workspace and does not do multi-node clustering. Wildcard custom domains and MongoDB restores are not available yet, and the control plane itself is hosted rather than self-hostable.

Your VPS can be running an app and a database tonight.

One command on any Linux server, one GitHub repository, and nothing new to maintain. Free, with no paid tier waiting behind it.

Connect your server free Read the getting started guide