Open-source alternative to Heroku, Vercel, and Netlify

Original Article ↗ Hacker News Discussion ↗

Alternative self‑hosted PaaS and deployment tools

  • Many compare Dokploy to existing options: Dokku, CapRover, Piku, Coolify, Easypanel, Hatchbox, Swarmlet, and others.
  • Several commenters report long-term, reliable use of Dokku and CapRover, contrary to a claim that these only “work out of the box” about half the time.
  • Piku is highlighted for not using Docker; some like that it runs processes directly on the host.
  • Coolify is described as promising and improving quickly; Easypanel and Hatchbox are noted as closed-source / managed services.
  • Dokku is praised as mature, cheap to self‑host, and able to use different “schedulers” (Docker, Kubernetes, Nomad) and various proxies (nginx, caddy, etc.).

Kubernetes vs simpler PaaS

  • Some argue that if you already know Kubernetes, it’s hard to justify not using it everywhere, even for small projects, due to its flexibility.
  • Others say Kubernetes is overkill and time‑consuming; they want a Heroku‑like “git push and done” experience.
  • Tools like Korifi, Kubevela, Crossplane, Porter, and Otomi are mentioned as “PaaS on Kubernetes,” but perceived as more complex than Heroku.

Static site hosting and Netlify alternatives

  • Netlify is criticized in light of a past $104k bill; a commenter says promised safeguards are still not visible.
  • Alternatives suggested: Cloudflare Pages, BunnyCDN, GitHub Pages, or self‑hosting with nginx/Caddy plus CI to upload assets.
  • Some prefer EU‑based CDNs and are wary of “free” tiers.
  • tau is mentioned as a self‑hosted alternative comparable to Cloudflare/Vercel.

Licensing and “open source” status

  • Multiple commenters say Dokploy is not truly open source: it uses Apache 2.0 text with extra terms that forbid commercial/for‑profit use.
  • This is described as “source‑available” and compared to BSL‑style licenses.
  • The combination of standard Apache header plus custom appendices is seen as confusing and potentially misleading; several argue the “open‑source” label is inaccurate.

Commit history and development model

  • The repo’s small number of commits triggers suspicions that it’s a toy or that history was hidden.
  • Some defend flattening history when open‑sourcing: early commits may contain secrets, messy code, or embarrassing messages; a clean initial commit is seen as pragmatic.
  • Others call this a bad practice that harms maintainability and collaboration by losing rationale and incremental changes.
  • There’s debate over whether open source implies transparent development history, or simply access to current source code.

Perceived marketing red flags

  • Testimonials on the website are called out as looking fake (generic company names, avatars, abbreviated surnames).
  • The maintainer says these were leftovers from an earlier SaaS direction and has removed them, but some feel this doesn’t fully address authenticity concerns.
  • The project name’s similarity to other tools plus the restrictive license and commit history lead some to view it as “open source” mainly for marketing.

Operational details: ports, proxies, databases

  • One person wants a deployment tool that doesn’t seize ports 80/443 because they already manage nginx; discussion notes Dokku and others can be reconfigured or proxied behind an existing setup.
  • Database hosting is highlighted as the most complex/costly part; some propose a shared VPS database server, but others prefer managed services like RDS or managed Postgres for backups and simpler app mobility.