dokku.com

What It Is

Dokku is an open-source, extensible, lightweight PaaS, officially described as “the smallest PaaS implementation.” It runs on a single server of your choice and uses Docker to build and run applications. Its deployment workflow is similar to Heroku: once the host is configured, a Git push can trigger the build and release process.

Core Capabilities

Dokku supports multiple build methods, including Dockerfile, Herokuish Buildpacks, Cloud Native Buildpacks, Nixpacks, and Railpack. It can automatically detect the application language or build from a user-defined image. At runtime, applications are placed into isolated containers, while nginx, cron, and related components handle web routing, background processes, and scheduled tasks. The documentation also covers operational features such as logs, remote commands, users, zero-downtime deployment checks, domains, SSL, ports, proxies, backups, persistent storage, and resource management.

Ecosystem and Extensibility

One of Dokku’s key strengths is its plugin system. Official plugins cover Postgres, MySQL, MariaDB, Redis, Mongo, RabbitMQ, Memcached, Let's Encrypt, Registry, Elasticsearch, Meilisearch, Grafana/Graphite/Statsd, and more. The proxy layer supports Nginx, Caddy, HAProxy, OpenResty, and Traefik; schedulers include Docker Local, K3s, and Nomad. The CI/CD documentation covers GitHub Actions, GitLab CI, Generic CI/CD, and Woodpecker CI.

Pricing and Deployment

The main materials clearly indicate that the open-source version of Dokku is available. Dokku Pro is also offered, and the project accepts sponsorship via OpenCollective and Patreon, but Pro pricing is not disclosed. Self-hosting requirements are relatively clear: Ubuntu 22.04/24.04 or Debian 11+, with support for AMD64 and arm64. For minimum memory, the Docker Scheduler recommends 1GB, while K3s requires 2GB per node.

Pros, Cons, and Best-Fit Users

Its advantages include no vendor lock-in, controllable costs, a Heroku-like experience, a rich plugin ecosystem, and detailed documentation. The downsides are that you need to maintain your own server, SSH access, domains, Docker setup, and security policies. As a single-server PaaS, it is naturally not ideal for complex high-availability production clusters, and community plugins can vary in maintenance quality. It is well suited to independent developers, small teams, internal tools, small SaaS projects, and users looking to migrate from Heroku to a self-hosted environment.

Access from China

The main materials do not provide information on access, payments, or mirrors for mainland China, so this remains unknown. In real-world use, you should also consider connectivity to GitHub, Docker sources, packagecloud, and your cloud server network. If you need a more graphical or integrated experience, compare it with Coolify and CapRover; if you are open to managed platforms, consider Heroku, Render, Railway, and Fly.io.