Self-hosted PaaS
Run a deployment panel for apps, Docker Compose projects, databases, domains, redirects, and certificates on your own server.
Self-Hosted Dokploy
Your own app platform for Docker deployments, domains, and databases.
Dokploy is a self-hostable PaaS for deploying applications, databases, Docker Compose stacks, and services behind Traefik. On Kumo2 you can launch Dokploy on a dedicated cloud server in one click. We install it with Docker Swarm, Postgres, Redis, and Traefik following Dokploy's manual installation flow, then expose the dashboard on the server IP.
7-day money-back guarantee
Features
Swarm-based install
Kumo initializes Docker Swarm, creates the Dokploy overlay network, and starts Dokploy as a Docker service.
Traefik included
Traefik is installed on ports 80 and 443 so Dokploy can route domains and services once you point DNS at the server.
Private control data
Dokploy's application data runs with private Postgres and Redis services on the same VM, with persistent Docker volumes.
What you can do with it
- Run a personal or team deployment dashboard for side projects, APIs, bots, and internal tools.
- Deploy Docker Compose stacks without hand-editing reverse proxy configuration for every service.
- Keep app deployment metadata, domains, and infrastructure access on a server owned by your account.
System requirements
CPU
2 vCPU
Memory
2 GB
Storage
40 GB
Runtime
Docker Compose
Port
3000
Recommended sizes
Control Plane / Testing
2 vCPU / 2 GB RAM / 40 GB SSD
A compact Dokploy control plane for evaluation and a few light apps.
Dokploy Recommended
Default2 vCPU / 4 GB RAM / 60 GB SSD
A balanced default for running Dokploy plus small production services on the same server.
Multi-app Host
4 vCPU / 8 GB RAM / 120 GB SSD
More room for builds, databases, and several active app containers.
Busy App Platform
6 vCPU / 16 GB RAM / 240 GB SSD
For heavier workloads, more concurrent builds, and larger self-hosted stacks.
Resources & documentation
How deployment works
- 1
Pick a plan and a region close to you.
- 2
Choose how you'll sign in and confirm your order.
- 3
Kumo provisions a Linux server and starts the app with Docker — ready in minutes.
Frequently asked questions
What is self-hosted Dokploy?
It is Dokploy running on a cloud server that belongs to your Kumo2 account, rather than a shared hosted platform. You control the VM, Docker runtime, domains, and data.
How do I access it after deployment?
Open http://SERVER_IP:3000 in your browser and create the first Dokploy account. The deployment output shows the exact endpoint.
Why does it need ports 80, 443, and 3000?
Dokploy uses port 3000 for the dashboard. Traefik listens on 80 and 443 so Dokploy can route HTTP and HTTPS traffic for apps you deploy later.
What size should I choose?
Use Control Plane / Testing for evaluation. Dokploy Recommended (2 vCPU / 4 GB RAM) is the normal default if you plan to run small services on the same server.
Can I use my own domain and HTTPS?
Yes. Point DNS records to the server IP, then configure domains inside Dokploy. Traefik is already listening on 80 and 443.
Ready to deploy your own Dokploy?
Spin it up on a server you control. We handle provisioning and Docker — you keep the keys.
Deploy Dokploy7-day money-back guarantee
Not happy within 7 days of deploying? Get a full refund — just ask.