DokPloy Tutorial 2026: The Ultimate Self-Hosted PaaS for Docker & Apps

If you have spent any time deploying modern full-stack web applications, you already know the dilemma: managed cloud platforms like Heroku, Vercel, and Render provide an amazingly smooth “push-to-deploy” developer experience, but their pricing scales aggressively. Before you know it, what started as a simple side project costs hundreds of dollars a month in database provisioning and bandwidth fees.

For developers seeking complete infrastructure ownership without sacrificing convenience, self-hosted Platform-as-a-Service (PaaS) tools are the answer. While I have previously covered excellent solutions in our Coolify self-hosting guide and our Portainer Docker management guide, there is a newer, exceptionally fast player in the self-hosting ecosystem that has captured developer attention: DokPloy.

Built from the ground up with TypeScript, Next.js, and Docker Swarm, DokPloy turns any bare-metal server or cheap virtual machine into a self-contained, multi-tenant cloud application manager. Having migrated dozens of client workloads off managed PaaS platforms onto self-hosted DokPloy clusters, I can confidently say it strikes the perfect balance between raw power and developer ergonomics.

In this ultimate 2026 tutorial, I will walk you through everything you need to know about setting up, securing, and scaling DokPloy in production. Whether you want to host Node.js microservices, deploy complex Docker Compose stacks, manage self-hosted databases, or automate HTTPS routing with zero hassle, this guide covers it all from a hands-on sysadmin perspective.

What is DokPloy? Architecture & Core Concepts

DokPloy is a free, open-source, self-hosted PaaS designed to simplify application deployment and server management. Instead of forcing you to manually configure web servers, write complex bash deployment scripts, or manage raw container orchestration primitives, DokPloy provides an intuitive graphical interface that handles the entire application lifecycle.

Underneath its polished UI, DokPloy integrates several industry-standard open-source technologies:

• Docker & Docker Swarm Mode: Unlike traditional container managers that run stand-alone containers, DokPloy initializes your host as a Docker Swarm manager. This unlocks native zero-downtime rolling deployments, health checking, container restart policies, and multi-node cluster scaling.
• Traefik Proxy: DokPloy embeds Traefik as its primary ingress controller and reverse proxy. Traefik automatically discovers containers, routes incoming HTTP/HTTPS traffic, and handles automatic SSL certificate issuance.
• Nixpacks & Dockerfile Builders: To convert your raw source code into runnable container images without requiring you to write custom Dockerfiles, DokPloy utilizes Nixpacks. Nixpacks analyzes your code repository, detects if you are using Node.js, Python, Go, Rust, or PHP, installs the required system packages, and compiles an optimized OCI container image automatically.

By uniting these components into a single management pane, DokPloy offers the developer ergonomics of a premium cloud PaaS while running directly on your own infrastructure. If you understand what cloud computing is, you can think of DokPloy as building your own mini AWS cluster in under five minutes.

DokPloy vs. Coolify vs. CapRover vs. Heroku

Before installing a new PaaS on your servers, it helps to understand how DokPloy compares to other popular choices in the deployment landscape.

Key Architectural Differences

1. DokPloy vs. Coolify: Coolify is a mature, feature-rich PaaS that supports complex server topologies (including NixOS natively). However, DokPloy’s architecture feels notably lighter and faster. By relying strictly on Docker Swarm for all container deployments, DokPloy gets superior native load-balancing and zero-downtime rolling updates out of the box.
2. DokPloy vs. CapRover: CapRover pioneered Docker Swarm PaaS management, but its UI and build toolchain feel dated in 2026. DokPloy brings a modern React/Tailwind user experience, real-time build logs via WebSockets, and integrated Nixpacks auto-detection.
3. DokPloy vs. Dokku: Dokku is a fantastic CLI-driven PaaS. However, if your team requires a multi-user visual web dashboard, role-based controls, and graphical database management, DokPloy is infinitely easier to operate.

Server Sizing & System Prerequisites

Because DokPloy runs directly on top of Linux, you can install it on almost any server provider. For a high price-to-performance ratio, we recommend deploying on a VPS from Hetzner Cloud, DigitalOcean, or Linode. If you are experimenting in a homelab environment, DokPloy runs exceptionally well inside an Ubuntu virtual machine hosted on a Proxmox VE hypervisor.

Minimum Recommended Specs:

• Operating System: Ubuntu 22.04 LTS or 24.04 LTS, or Debian 12 (64-bit).
• CPU: 1 vCPU (2 vCPUs recommended for faster container builds).
• RAM: 2 GB minimum (4 GB+ recommended if building heavy Node.js or Rust applications). Read how Linux memory management works to understand how Node compilation devours memory.
• Disk Space: 20 GB SSD/NVMe storage.
• Architecture: x86_64 or ARM64 (Raspberry Pi and Ampere ARM instances are fully supported).

Before starting, ensure your server has a static public IP address. If you need a refresher on server hosting fundamentals, consult our guide on what is a VPS.

Step-by-Step: Installing DokPloy on Ubuntu Server

Let me guide you through the process of taking a fresh Ubuntu 24.04 server and converting it into a DokPloy deployment cluster.

Step 1: Connect to Your Server & Update Packages

Open your local terminal and connect to your remote server via SSH. If you haven’t hardened your SSH access yet, follow our stringent recommendations on how to secure SSH on Ubuntu.

ssh root@YOUR_SERVER_IP

Once logged in, refresh your system package repository indexes and upgrade existing packages to their latest stable releases:

sudo apt update && sudo apt upgrade -y

Step 2: Configure System Firewall Rules

To allow web traffic and management dashboard access, you must open HTTP (80), HTTPS (443), and the default DokPloy setup port (3000). If you are using Ubuntu’s built-in UFW firewall, check our detailed UFW firewall guide or execute:

sudo ufw allow 22/tcp
sudo ufw allow 80/tcp
sudo ufw allow 443/tcp
sudo ufw allow 3000/tcp
sudo ufw enable

Security Tip: Tools like Fail2ban and CrowdSec should be installed alongside UFW to automatically ban brute-force SSH attempts on your DokPloy host. Review our complete firewall security best practices.

Step 3: Run the Automated DokPloy Installer Script

DokPloy provides an official automated installation script that checks system dependencies, installs Docker Engine if missing, initializes Docker Swarm mode, sets up Traefik network bridges, and pulls the DokPloy container image. If you prefer to install Docker manually first, read our guide on installing Docker on Ubuntu.

Run the following command in your terminal:

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

During execution, the installer displays clear progress indicators in your terminal:

[INFO] Checking OS compatibility...
[INFO] Installing Docker Engine & Docker Compose plugin...
[INFO] Initializing Docker Swarm Mode on host...
[INFO] Creating Traefik overlay networks...
[INFO] Launching DokPloy Management Container...
[SUCCESS] DokPloy successfully installed!

If you need to inspect system service startup processes during failures, our guide on reading and analyzing Linux logs explains how to track daemon errors.

Initial Setup & Navigating the DokPloy Interface

Once the script finishes, open your browser and navigate to http://YOUR_SERVER_IP:3000.

Creating Your Administrator Account

On your initial visit, DokPloy presents an admin registration screen. Fill in your email address and a strong master password. Because this first account is assigned full super-user privileges across the platform, ensure you generate a cryptographically strong password and store it in a self-hosted password manager like Vaultwarden.

Setting Up Remote Servers & Docker Swarm Nodes

While DokPloy installs locally on your primary server (the Manager Node), it can control multiple worker nodes from a single dashboard.

Navigate to Settings > Servers inside the UI. Here, you can add additional remote VPS servers by providing their SSH connection details or Docker Swarm join tokens. By leveraging Docker Swarm under the hood, DokPloy allows you to manage distributed microservices across multiple cloud hosts without installing complex cluster management setups.

Deploying Applications on DokPloy

DokPloy makes deploying application source code remarkably flexible. You can deploy code directly from GitHub or GitLab repositories, build from custom Dockerfiles, or upload pre-compiled container images.

Let me demonstrate how to deploy a standard Node.js application.

Step 1: Create a New Project

1. Click on Projects in the left sidebar and select Create Project.
2. Name your project (e.g., production-api).
3. Inside the project view, click Create Application.

Step 2: Configure the Source Code Provider

Select your deployment provider:

• GitHub / GitLab: Authenticate your repository using a Personal Access Token or the GitHub App.
• Git Branch: Select the branch you wish to track (e.g., main). If you need to master Git workflows, read our Git and GitHub guide.
• Build Type:
  • Nixpacks (Automated): Recommended for standard frameworks (Next.js, Express, Django, Laravel, Go). Nixpacks automatically inspects your repository, installs build tools, and compiles your application.
  • Dockerfile: Best when your repository already contains a custom Dockerfile.
  • Docker Image: Select this if you wish to pull a pre-built image directly from Docker Hub.

If you are developing web services, check out our guides on building REST APIs with Node.js and Express or how to deploy a Node.js app on a Linux VPS.

Step 3: Configure Environment Variables & Port Mapping

Inside the application settings tab:

1. Navigate to Environment Variables. Paste your raw .env contents. DokPloy encrypts these variables securely on your server host.
2. Under Network, specify your container’s internal listening port (e.g., 3000 for Node apps).

Click Deploy. DokPloy streams real-time build logs directly to your dashboard as Nixpacks builds your image and launches the Docker Swarm service.

Managing Databases in DokPloy (One-Click Deployments)

Stateful databases require special persistence considerations. Running databases manually in raw containers without volumes risks catastrophic data loss (see Linux filesystem hierarchy for details on volume mounts). DokPloy solves this by featuring dedicated one-click database management for:

1. PostgreSQL: Ideal for relational data storage. Read our PostgreSQL vs MySQL comparison to choose the right database for your stack.
2. MySQL / MariaDB: Great for PHP applications and e-commerce setups.
3. MongoDB: Perfect for document-based NoSQL data models.
4. Redis: High-performance caching and session management.

Deploying a Managed PostgreSQL Instance

To spin up a database:

1. Open your DokPloy Project dashboard and select Create Database > PostgreSQL.
2. Enter a service name (e.g., app-db) and define your database name, user, and password.
3. DokPloy automatically configures persistent Docker volume mounts on your host filesystem.

Because your applications and databases run on the same internal Docker Swarm network, your web apps can connect to the database using its internal service name (e.g., postgres://user:pass@app-db:5432/dbname) without ever exposing database ports to the open internet. Secure design principles like this are covered extensively in our secure home server checklist.

Deploying Complex Multi-Container Stacks with Docker Compose

One of DokPloy’s strongest features is its native support for Docker Compose. If your infrastructure consists of multiple intertwined services, you can deploy them all using a single docker-compose.yml file.

For example, you can easily deploy complex open-source software like our guides on deploying n8n with Docker Compose, setting up an Immich photo management server, running Nextcloud personal cloud storage, or managing documents with Paperless-ngx.

In DokPloy, click Create Compose, select your raw Compose editor, and paste your YAML definition. When you click Deploy Compose, DokPloy translates the YAML structure into a Docker Swarm stack deployment, ensuring all volumes, networks, and services start in proper dependency order.

If you enjoy hosting your own applications, browse our tutorials on setting up Pi-hole DNS ad-blocking, running a Jellyfin media server, setting up Syncthing private file synchronization, hosting Stirling-PDF tools, or deploying local AI using our OpenWebUI setup guide and Ollama Linux installation guide.

Advanced Routing, Custom Domains, and Traefik Setup

Running applications in production requires routing domain names (e.g., api.yourdomain.com) to specific containers while securing all connections with HTTPS.

DokPloy makes domain attachment effortless by using Traefik Proxy behind the scenes. Unlike manual proxy configurations using Nginx Proxy Manager, Caddy, or raw Nginx, DokPloy automates Traefik label creation dynamically whenever you update domain settings in the UI.

Step 1: Configure Your DNS Records

Log in to your DNS provider (such as Cloudflare). If you need an overview of how domain routing resolves, check out our article on how DNS domain resolution works. Add an A record pointing your subdomain to your DokPloy server’s public IP address.

Step 2: Attach the Domain in DokPloy

1. Open your deployed Application dashboard in DokPloy.
2. Select the Domains tab.
3. Click Add Domain. Enter your domain name.
4. Set the internal container port.
5. Enable the HTTPS / SSL toggle.

Click Save. DokPloy automatically contacts Let’s Encrypt, completes the HTTP-01 challenge, issues an SSL certificate, and configures Traefik to serve your site securely over HTTPS. For more background on transport security, read our complete guide on how to enable free HTTPS with Let’s Encrypt and understand HTTP protocol basics.

Automated Database & Volume Backups via S3

Never run production infrastructure without automated off-site backups! If hardware fails or a container volume becomes corrupted, off-site backups are your only recovery line. We cover this extensively in our guide on backup strategies for self-hosted servers.

DokPloy includes built-in S3-compatible automated backup scheduling for all hosted databases and persistent storage volumes.

Configuring an S3 Backup Destination

1. In the DokPloy sidebar, go to Settings > Backups.
2. Click Add Backup Provider.
3. Select your preferred S3-compatible cloud storage provider (e.g., AWS S3, Cloudflare R2, DigitalOcean Spaces, or self-hosted MinIO).
4. Enter your S3 Endpoint URL, Access Key, Secret Key, and Target Bucket Name.

Navigate to your database instance in DokPloy, click on Backups, and create an automated backup rule using cron syntax (e.g., 0 2 * * * to run daily at 2:00 AM). DokPloy will automatically run pg_dump or mysqldump, compress the output, and upload the archive directly to your remote S3 bucket.

For file-level disaster recovery outside DokPloy, tools like Restic, BorgBackup, rsync, and scp remain essential sysadmin utilities.

Monitoring, Logs, and Scaling

DokPloy captures stdout and stderr from all running containers. By opening the Logs tab of any application or database, you can view streaming real-time output.

For comprehensive uptime tracking, we strongly recommend pairing DokPloy with an external monitoring tool like Uptime Kuma. Point Uptime Kuma at your DokPloy applications’ HTTP endpoints to receive instant alerts via Telegram or Discord if a service ever stops responding. You can also run Watchtower independently if you want automated base-image updates, though DokPloy handles redeployments natively.

Security Hardening Best Practices

Running your own PaaS means taking security responsibility into your own hands. Implement these critical hardening steps:

1. Disable Root Password SSH Login: Force SSH key-based authentication and disable root password access.
2. Restrict Port 3000 to VPN: Once your custom domain and SSL are configured for DokPloy’s admin dashboard (e.g., dokploy.yourdomain.com), block external direct public IP access to port 3000 using UFW. Connect to your admin panel securely over a VPN or Tailscale/WireGuard tunnel.
3. Enforce SSO/2FA: Configure single sign-on (SSO) if your team uses centralized identity providers.
4. Harden Container Security: Ensure containers do not run with unnecessary privileged permissions. Read our guide on securing Docker containers to understand container isolation.
5. OS Security Updates: Keep host Linux kernel packages updated automatically using unattended-upgrades. For file system integrity, review our guides on understanding Linux file permissions.

Conclusion

DokPloy provides an incredible middle ground between the terrifying complexity of raw Kubernetes clusters and the exorbitant costs of managed platforms like Heroku. By leveraging native Docker Swarm and Traefik routing under a beautifully designed web interface, DokPloy allows solo developers and small teams to host dozens of applications securely on extremely cheap infrastructure.

Once your deployment platform is stable, ensure you have proper monitoring in place. Check out our Uptime Kuma monitoring guide to track your new DokPloy endpoints.

Official Documentation

To stay updated with the latest features, releases, and documentation for DokPloy, refer to the official project links:

• Official DokPloy Documentation: https://docs.dokploy.com
• DokPloy GitHub Repository: https://github.com/Dokploy/dokploy
• Official Release Notes & Changelog: https://github.com/Dokploy/dokploy/releases
• DokPloy Community Discord: https://discord.gg/dokploy
• Traefik Documentation: https://doc.traefik.io/traefik/

Frequently Asked Questions (FAQ)

What hardware requirements are needed to run DokPloy?

DokPloy is extremely lightweight! You can run it on a budget VPS with 1 vCPU and 2GB RAM. However, 2 vCPUs and 4GB RAM are highly recommended for smoother multi-container application builds and stable database hosting without risking Out-Of-Memory (OOM) errors during Nixpacks compilation.

Is DokPloy completely free and open-source?

Yes, DokPloy is 100% open-source software published under the MIT license. You can host it on your own servers without subscription fees, usage limits, or vendor lock-in, forever.

How does DokPloy handle reverse proxying and SSL certificates?

DokPloy includes Traefik as its built-in reverse proxy controller. When you add a domain to an app or database via the UI, DokPloy automatically generates Traefik routing labels and provisions free HTTPS certificates using Let’s Encrypt via HTTP-01 challenges.

Can I deploy multi-container Docker Compose applications in DokPloy?

Absolutely. DokPloy features native support for Docker Compose YAML definitions. You can paste your compose syntax directly into the dashboard editor or link your deployment to a docker-compose.yml file stored in your Git repository.

How does DokPloy compare to Coolify or Heroku?

Unlike Heroku, DokPloy runs on your own infrastructure for a fraction of the cost. Compared to Coolify, DokPloy uses Docker Swarm mode for robust native clustering, features an ultra-responsive React dashboard, and has a lower RAM footprint, making it incredibly snappy.

Can DokPloy manage multiple servers in a cluster?

Yes. Because DokPloy relies on Docker Swarm, you can easily add multiple “Worker” nodes to your cluster via the DokPloy settings page. This allows you to distribute your application containers across multiple physical or virtual machines for high availability.

How do I back up my databases in DokPloy?

DokPloy has a built-in S3 backup utility. You can connect it to AWS S3, MinIO, Cloudflare R2, or DigitalOcean Spaces. Once connected, you can schedule automated daily/weekly cron jobs that dump your PostgreSQL, MySQL, or MongoDB data and upload it directly to your remote storage bucket.

What is Nixpacks and why does DokPloy use it?

Nixpacks is an open-source build tool created by Railway. Instead of forcing you to write a complex Dockerfile for every app, Nixpacks automatically analyzes your code repository (detecting Node.js, Python, Go, etc.), installs the correct system dependencies, and builds an optimized, production-ready container image automatically.

Is it safe to expose the DokPloy admin dashboard to the internet?

Exposing any management dashboard carries risk. While DokPloy supports authentication, it is best practice to place the port 3000 admin panel behind a firewall and access it exclusively via a secure VPN like Tailscale or WireGuard, ensuring only authenticated local network traffic can reach the login screen.

How do I update DokPloy to the latest version?

Updating DokPloy is incredibly simple. Log into your server via SSH and run the exact same installation script command you used to install it originally (curl -sSL https://dokploy.com/install.sh | sudo sh). The script will detect your existing installation, pull the latest image, and restart the manager container without destroying your data.