Dokku has earned its reputation. It's been around for over a decade, it turns a cheap VPS into a git push deploy target, and it does it with a remarkably small footprint — Heroku-style buildpacks or a Dockerfile, an nginx proxy, a Let's Encrypt plugin, and official plugins for Postgres, MySQL, and Redis. For a solo developer with one server, it's genuinely hard to beat on cost: the software is free and the server is whatever you're willing to pay for.
So why do people leave? A few recurring reasons, none of them secrets:
- It's single-server at heart. Dokku runs your apps on the box it's installed on. There's a scheduler for k3s if you want to go multi-node, but at that point you're operating Kubernetes with extra steps.
- You own the server. OS patches, disk filling up with old images, Docker upgrades, and — the big one — database backups are your job. The Postgres plugin gives you a database; it doesn't give you tested restores.
- The open-source version is CLI-only. A web UI exists in the paid Dokku Pro. Fine for one person; harder when a teammate needs to check logs and doesn't have SSH access.
- No team model. There's no RBAC, no organizations, no audit trail out of the box.
If those don't bother you, keep running Dokku — it's mature software with excellent docs ([dokku.com/docs](https://dokku.com/docs/getting-started/installation/)). If they do, here's what's worth looking at in 2026, split into self-hosted and managed. Disclosure up front: PandaStack is our product, and it's in the list.
Self-hosted alternatives
Coolify — best for Dokku users who want a UI
[Coolify](https://coolify.io/docs) is the most direct "Dokku plus a dashboard" upgrade. It's open source, self-hosted, deploys from Git, and adds the things Dokku's OSS version lacks: a real web UI, one-click provisioning for a long list of services (Postgres, MySQL, Redis, and dozens of self-hostable apps), docker-compose support, and management of multiple servers from one control panel. Development pace is fast, and there's a paid cloud version if you want the control plane hosted for you while apps stay on your servers.
The honest counterpoint: it's a bigger, faster-moving system than Dokku, and fast-moving cuts both ways — more features, more surface area, more upgrades to keep on top of. You still own the servers and the backups.
Best for: self-hosters who want Dokku's economics with a dashboard and one-click databases.
CapRover — best for simple clustering on Docker Swarm
[CapRover](https://caprover.com/docs/get-started.html) has been around for years: a self-hosted PaaS built on Docker Swarm with a web UI, a one-click app marketplace, and Let's Encrypt built in. Because it's Swarm underneath, going from one server to a small cluster is genuinely easy — something Dokku can't say. It's stable and well-understood.
The counterpoint: Docker Swarm itself is a quiet corner of the ecosystem these days, and CapRover's development pace reflects a mature project rather than a fast-evolving one. If you're betting on it for years, that's worth weighing.
Best for: teams that want a self-hosted UI plus painless two-to-five-node clustering.
Kamal — best for teams that want deploys, not a platform
[Kamal](https://kamal-deploy.org/) is 37signals' answer, and it's philosophically different: it's not a PaaS at all. There's no daemon running on your servers making decisions — Kamal is a CLI that SSHes in, runs your containers, and does zero-downtime cutover through its own proxy. Your servers stay boring, plain Docker hosts you fully understand. Configuration is one YAML file in your repo, and it deploys the same way to one host or twenty.
The trade: everything Dokku gave you beyond deploys — provisioning databases, managing SSL for arbitrary apps, an addon ecosystem — is back on you. Kamal deploys what you tell it to and nothing more. That's the feature, but know what you're signing up for.
Best for: teams comfortable with Docker who want deploy automation with zero platform machinery.
Managed alternatives
At some point the honest question isn't "which self-hosted PaaS" but "should I be running servers at all." The real cost of self-hosting was never the software — it's being the person responsible for Postgres backups at 2 a.m.
Fly.io — best for multi-region apps
[Fly.io](https://fly.io/docs/) runs your containers as lightweight VMs in regions around the world, with an Anycast network routing users to the nearest one. If your app benefits from running close to users — or you want one platform that handles global distribution without you building it — it's the strongest option here. The CLI-first workflow (fly launch) will feel familiar to Dokku users. Pricing is usage-based.
The counterpoint: it's a more complex mental model than a single-server PaaS (regions, machine states, volumes are region-pinned), and you should read their docs on database options carefully rather than assuming a Heroku-style managed Postgres.
Best for: apps where multi-region latency actually matters.
Render — best for the closest managed Heroku experience
[Render](https://render.com/docs) is a managed PaaS in the classic mold: connect a repo, it builds and deploys, with managed Postgres, cron jobs, background workers, and preview environments. Since Heroku removed its free tier in 2022, Render has been one of the default landing spots, and its free tier (which spins services down after inactivity) makes it easy to evaluate. The dashboard and docs are polished.
The counterpoint: as with any managed platform, costs scale with usage and you're inside their product decisions. Check the current numbers on their [pricing page](https://render.com/pricing) rather than trusting any blog post's snapshot, including this one.
Best for: teams that want to stop thinking about infrastructure entirely, with a mature UI.
PandaStack — best for Dokku simplicity without operating the server
[PandaStack](https://pandastack.io) is our take on the same problem Dokku solves — push code, it runs — but managed. Connect a Git repo; it auto-detects the framework (or uses your Dockerfile), builds with rootless BuildKit in ephemeral Kubernetes jobs, streams the build logs live, and deploys behind automatic SSL. Managed PostgreSQL, MySQL, MongoDB, and Redis are first-class: attach a database to an app and DATABASE_URL is injected automatically, which replaces the Dokku plugin-and-link dance. Cronjobs and edge functions are built in, and there's an actual team model — organizations, roles, SSO.
The free tier covers 5 web services, 5 static sites, one database, 100 GB bandwidth, and 300 build minutes a month; paid plans are flat at $15/mo (Pro) and $25/mo (Premium) rather than usage-based. Free-tier apps run sandboxed in gVisor and scale to zero when idle — which is also the honest caveat: cold starts on free, and a small database volume meant for dev rather than heavy production. We're also the newest platform on this list, and the ecosystem around us is still growing.
Best for: solo devs and small teams who liked Dokku's git-push loop but are done maintaining the VPS underneath it.
How to actually choose
Three questions settle it faster than any feature matrix:
- 1Do you want to keep the server? If yes: Coolify for a UI, CapRover for easy clustering, Kamal for minimalism. If no: keep reading.
- 2Does your app need to run in many regions? If yes, Fly.io. Most apps honestly don't.
- 3Who restores the database when it breaks? If the answer should be "not me," pick a platform where the database is managed and wired in — Render or PandaStack — and weigh flat pricing against usage-based for your workload.
Dokku set the bar for what one developer with one server can do. Everything on this list is a different answer to what happens after that. If the managed route is where you land, you can push a repo and see the whole loop at https://pandastack.io.