Summary: Coolify, Dokploy and CapRover are self-hosted PaaS dashboards; Dokku is a CLI-first, Heroku-style PaaS, and Kamal deploys from your own machine with no control plane on the server. Coolify has the broadest built-in feature set, Dokploy is stronger for Docker Swarm clustering and per-member permissions, and CapRover and Dokku run on less RAM.
Head-to-head pages
- Coolify vs Dokploy covers the two dashboard tools on their own: Swarm, permissions, Compose and cloud pricing.
- Coolify as a Vercel alternative: a server you administer, compared with Vercel's hosted platform.
- Coolify as a Heroku alternative: a dashboard on your VPS, compared with Heroku dynos and managed data.
- Coolify as a Netlify alternative: Docker apps on your server, compared with Netlify's CDN, functions and managed Postgres.
Which should you pick?
- You want one dashboard for apps, databases and ready-made services on one or a few servers → Coolify. It also fits if you want backups, previews and team access built in, or would rather not host the dashboard yourself (Coolify Cloud). New to this? See how to deploy apps on your own VPS.
- You want Docker Swarm clustering from a UI, or fine-grained permissions per member → Dokploy. Its free edition lets you grant Members specific permissions. Custom roles are in Dokploy Enterprise.
- You have a 1 GB server and want a simple UI with a single Swarm-based model → CapRover. It
documents a 1 GB minimum, deploys straight from your machine with
caprover deploy, and lets you edit the full NGINX config per app. - You like Heroku's
git pushworkflow and are happy in a terminal → Dokku. It runs on a single host by default and needs 1 GB. An optional k3s scheduler handles multiple nodes. - You want to deploy a containerized app from your laptop or CI to one or many servers, with nothing extra running on them → Kamal. It uses zero-downtime deploys behind kamal-proxy, and was built for Rails but works with any containerized web app.
Feature comparison
✅ built in · ◐ partial or paid add-on · ❌ not available. Details and sources are in the notes below the table.