Dokku

What Dokku actually is

Dokku is a self-hosted Platform-as-a-Service that runs on a single Linux server. The project's own description — "the smallest PaaS implementation you've ever seen" — is accurate in the literal sense: it is a compact layer of shell, Go and Docker glue that gives you Heroku's developer workflow on hardware you rent yourself. You push code with git push, Dokku builds it with Heroku-compatible buildpacks (or a Dockerfile, or a prebuilt Docker image), runs the result in isolated containers, wires up nginx routing, and issues Let's Encrypt certificates through a plugin. The promise is exactly what it sounds like: the ergonomics of a managed PaaS at the price of a VPS.

The project started in June 2013 — the GitHub repository was created on 2013-06-08 — as a small experiment by Jeff Lindsay combining Docker with Heroku buildpacks. It is MIT licensed, has accumulated roughly 32,000 stars on GitHub and 353 tagged releases, and is maintained today by a small group of contributors, with Jose Diaz-Gonzalez as lead maintainer. That history matters for a tool like this: a self-hosted PaaS is only as trustworthy as its maintenance, and Dokku has been continuously shipped for well over a decade. The current release line is v0.38.x.

Functionally, Dokku covers the full application lifecycle on one host: dokku apps:create, git push dokku main, config management via environment variables, process scaling, log tailing, zero-downtime deploys, and an official plugin set for datastores (Postgres, Redis, MySQL and others). The plugin ecosystem is the extension mechanism for everything else — queues, storage, alternative proxies. There is no control plane in someone else's cloud, no account to create, and no telemetry requirement. Your server is the whole platform.

We categorize Dokku under managed-cloud alongside commercial PaaS offerings, but the honest framing is that it is the self-hosted counterpoint to that category. It gives you the deployment workflow those services sell; you supply the operations.

Pricing: what you really pay

Dokku core is free software under the MIT license. There is no tier that gates features, no seat count, no usage metering. The money you spend is on the server underneath: a Hetzner Cloud CX22 (2 vCPU, 4GB RAM) at €4.35/month is a realistic baseline for hosting several small applications, and that is the kind of price point that makes this category compelling. We keep current numbers for hosts like that on our benchmarks page.

There is exactly one paid product: Dokku Pro, a self-hosted web UI and JSON API that sits alongside your existing installation. It costs $849 for a lifetime license — a one-time payment, not a subscription, covering one production server plus two pre-production servers, with free upgrades for life and email support from the maintainers. The maintainers are explicit that the current price is introductory and will rise as the product matures. Volume and team licenses are handled by email.

We think $849 is a lot for a UI at first glance, and we would not buy it for a single hobby project. But the comparison is not "UI versus no UI"; it is "UI versus hiring ops time". For a small team running a dozen client apps on Dokku, a one-time $849 that replaces daily CLI fiddling and includes direct email support to the people who write the code is a reasonable trade. Solo developers can ignore it entirely and lose nothing of the core workflow.

The other cost line is your own time. Dokku has no free tier in the hosted sense and no trial, because there is nothing to trial — install it on a $5-or-less-class VPS or a beefier box and you are running. Compare that with Heroku-style pricing, where a modest production dyno plus a database add-on quickly passes $50/month for resources that cost a fraction of that raw.

Performance & infrastructure

Dokku's performance is the performance of the host you choose. That is the point, and it is also the caveat. There is no bundled CDN, no global network, no proprietary hypervisor — you pick Hetzner, Vultr, a bare-metal box in your rack, or anything else that runs a supported Linux distribution (Ubuntu and Debian are the primary targets, with Arch packages also published). Whatever CPU, RAM, NVMe and bandwidth you pay for is exactly what your apps get.

On a modern VPS this is more than enough for most workloads Dokku targets: internal tools, side projects, small-to-mid SaaS products, agency client sites. Deploys are typically buildpack or Docker builds, so build speed scales with the machine; runtime overhead is Docker's, which is small. One nuance we care about: because everything lands behind nginx on one host, there is no artificial routing layer adding latency.

What you do not get is scale-out. Dokku's design is single-host. You can scale processes up and down within the box, and you can run multiple Dokku servers as separate islands, but there is no scheduler placing containers across a fleet and no automatic failover if the host dies. Backups, snapshots and DDoS mitigation are whatever your provider offers — Dokku itself ships none of those, though datastore plugins and community tooling cover backup workflows. IPv6, likewise, is a property of the host's network, not of Dokku.

In our view this is a fair trade at the price. Most applications that fit on one well-provisioned server do not need Kubernetes, and pretending otherwise is how teams end up paying more for orchestration than for compute.

Where it falls short

The biggest limitation is the one the whole design implies: you are the operations team. Security updates for the OS, Docker upgrades, Dokku upgrades, certificate renewals (automated by the plugin, but still on your box), disk monitoring, log rotation — all yours. Dokku upgrades have historically been smooth, but plugin compatibility is community-maintained, and a major version bump can mean a weekend of testing before you touch production.

Availability is single-machine. If your server's host reboots or its network drops, your apps are down until it returns. For anything that cannot tolerate that, you need redundancy at a layer Dokku does not provide — a second server with failover DNS, an external database, object storage off-box. That is solvable, but it is work the platform does not do for you.

Support is community-based: GitHub issues, documentation, and a Slack channel. That is normal for open source, and the docs are genuinely good — but there is no guaranteed response time and no SLA. The only paid support path is the email support bundled with Dokku Pro.

Finally, Dokku is not a multi-tenant PaaS in the enterprise sense. Teams and user management are improving (Dokku Pro 1.3 added user and team management), but if you need hard isolation between untrusted tenants, a shared Dokku host is not the right substrate.

Who should pick this

We pick Dokku when the person deploying is comfortable with SSH and a Linux shell and wants Heroku's workflow without Heroku's invoice. It is our pick for solo developers and small teams running a handful of production apps, agencies hosting client projects on one server each, and anyone with a homelab who wants push-to-deploy at home. It is also the cleanest exit path from Heroku: buildpacks carry over, the command idioms carry over, and the cost drops to raw infrastructure.

We would not pick it for a team with zero Linux experience, for workloads that demand multi-host high availability out of the box, or for organizations that need contractual SLAs and vendor accountability. In those cases a managed PaaS (or plain Kubernetes with real ops staff) fits better, and paying for that is not a failure.

Key takeaways

• Free MIT-licensed self-hosted PaaS: git push, Heroku buildpacks, Docker, nginx and Let's Encrypt on one Linux server you control.
• Mature project — created June 2013, 353 releases, ~32,000 GitHub stars, actively maintained by Jose Diaz-Gonzalez and contributors.
• Your only real cost is the VPS (a €4.35/month Hetzner class machine handles several small apps) plus your own ops time.
• Dokku Pro is an optional $849 lifetime license (1 production + 2 pre-production servers) adding a web UI, JSON API and email support.
• Single-host by design: no built-in failover, autoscaling, backups, or DDoS protection — those come from your host and plugins.
• Best for Linux-comfortable developers and small teams wanting Heroku ergonomics at VPS prices; wrong for teams needing SLAs or multi-host HA.

Sources

• https://dokku.com/
• https://pro.dokku.com/
• https://github.com/dokku/dokku
• https://dokku.com/blog/2026/pro-release-1.4.0/