Dokku: My favorite personal serverless platform

Original Article ↗ Hacker News Discussion ↗

Overall sentiment

  • Many commenters are very positive on Dokku: long-term stability, low resource needs, and “just works” for many personal and small-production apps.
  • Several say they would or do financially support it because of perceived value and responsive maintainer support.
  • A minority report bad experiences (apps not restarting after VPS crashes, plugin bugs, LetsEncrypt issues, trouble running Dokku itself in Docker) and moved to other stacks.

What Dokku Provides

  • Git-push deploys, buildpack and Dockerfile support, automatic nginx config, optional Let’s Encrypt, zero-downtime deploys, plugin ecosystem (databases, storage, etc.).
  • Strong fit for many-apps-on-one-server scenarios and hobby / small SaaS hosting, with predictable low cost compared to commercial PaaS.

Configuration & Operations

  • Some dislike that most app setup is via ad‑hoc CLI commands, not a single declarative config. Workarounds: shell scripts, app.json, Terraform provider, and Ansible modules.
  • Others argue Ansible/Terraform are overkill when Dokku already makes single‑server deploys trivially quick.

Scalability and Resilience

  • Historically single-server; concern that this limited resilience and horizontal scaling.
  • Newer support for multiple servers and k3s / Kubernetes schedulers is highlighted as addressing clustering and failover, though details (e.g., ingress setup) are not fully clear in the thread.
  • Some argue vertical scaling and “one box” is enough for 80–99% of personal projects; large-scale clustering is seen as premature for most.

Comparisons and Alternatives

  • Alternatives mentioned: Dokploy, Coolify, CapRover, Kamal, Convox, Lunni, Piku, Ptah, plain Docker Swarm, k8s/k3s, Ansible + Caddy/Traefik, Proxmox, “just docker-compose + reverse proxy.”
  • Dokploy and Coolify get praise for web UIs and multi-node support; some still prefer Dokku’s simplicity and minimal “magic.”

“Serverless” Terminology Debate

  • Many object to calling Dokku “serverless,” noting it’s a self-hosted PaaS on a VPS.
  • Others defend broader usage: “serverless” as infra abstraction for app developers rather than literal absence of servers.
  • No consensus; several see the debate itself as pedantic.

Databases, Storage, and Networking

  • dokku-postgres works for some, but upgrades and plugin compatibility have bitten others; some now run Postgres directly on the host and just wire env vars.
  • Storage approaches: local disk, self-hosted MinIO, or cheap S3-compatible services combined with low-cost VPSes.
  • When using Cloudflare as proxy, commenters recommend TLS between Cloudflare and Dokku, possibly with origin certs, IP allowlists, or tunnels; wildcard-cert handling under Dokku is left unclear.