Dokploy

What is Dokploy?

Dokploy is an open-source deployment platform that manages applications, databases and Docker Compose stacks on your own servers. It includes templates, automatic SSL, and monitoring, aimed at replacing paid PaaS subscriptions.

Best for

Small teams self-hosting many applications on one server

Why choose Dokploy

Dokploy is the dashboard-first answer to self-hosted PaaS. Where Dokku is all terminal and Coolify is opinionated about its own way of doing things, Dokploy gives you a clean web interface for deploying applications, databases and Compose stacks without leaving the browser. It handles the tedious parts — reverse proxy, certificates, domains, backups — and lets you keep the Git-based workflow that modern deployment expects. For someone who wants managed-platform ergonomics on a rented box, it is the shortest path there.

Replaces

• Vercel
• Heroku
• Railway

Key features

• Application and database management
• Docker Compose support
• Automatic SSL and domains
• Built-in monitoring and backups

What to watch out for

Young projects carry young-project risk, and Dokploy is a relatively new entrant competing in a crowded space. Expect the occasional rough edge, and expect to read documentation that has not caught up with a recent release. Like every self-hosted PaaS, it adds a control layer that itself needs backing up and updating; if the control plane breaks, you are debugging Docker by hand. It also assumes a fairly conventional stack — apps, databases, Compose — and an unusual deployment will fight the abstraction.

How to deploy

• Install script

Getting started

Run the installer on a clean server and note the port and initial admin credentials it prints, since the setup wizard only appears once. Configure the server in the interface and let it manage the reverse proxy rather than layering your own on top; two proxies fighting over ports is the most common self-inflicted wound. Deploy a database first and confirm you can reach it, then an application, so you learn the networking model on something simple. Turn on scheduled backups before you create anything you would miss.

Typical setup

The common shape is a single VPS running Dokploy and the applications it manages, with an external managed database or a containerised one for anything important. Users typically connect a Git repository, deploy an application, then add databases and Compose stacks from the same interface. Because it handles certificates and domains itself, it replaces the manual reverse-proxy setup many people were maintaining by hand, which is the main reason they choose it.

Who should look elsewhere

Being a young project, it is a risky foundation for anything where a broken control plane means a broken business. If you need guaranteed support contracts, long-term stability promises or an audit trail for compliance, a commercial platform is the honest recommendation. It is also less appropriate for teams that prefer managing their stack entirely from configuration files in version control.

Project health

• GitHub stars: 37,599
• Last code push: 2026-09-29
• Open issues: 733
• Status: actively developed

Figures pulled from the GitHub API and refreshed periodically.