// the find
coollabsio/coolify
An open-source, self-hostable PaaS alternative to Vercel, Heroku & Netlify that lets you easily deploy static sites, databases, full-stack applications and 280+ one-click services on your own servers.
Coolify is a self-hosted PaaS control plane that manages Docker deployments across your own servers over SSH — think Heroku's UX but your infrastructure. It handles applications, databases, and 280+ one-click services (Plausible, Umami, n8n, etc.) from a single Laravel dashboard. The target user is a developer or small team that wants Heroku-level convenience without the bill or the lock-in.
1. The no-lock-in architecture is genuine: all Docker configs live on your server, not in Coolify's database. If you nuke the control plane, your containers keep running and you can recover manually. 2. SSH-based deployment means it works against anything with an SSH daemon — VPS, bare metal, a Raspberry Pi in a closet. No agent to install on the target server. 3. The one-click service catalog is legitimately broad and kept current; each service ships its own compose template that you can inspect and modify. 4. Active maintenance cadence (daily pushes, 56k stars, well-funded via sponsors) means bugs get fixed and new Docker features land quickly.
1. The control plane itself needs a server, and that server is a single point of failure — if Coolify goes down you lose deploy capability and real-time status, even though your apps keep running. The recommended two-server setup (one for Coolify, one for apps) adds cost that partly undercuts the 'cheaper than cloud' pitch. 2. The 280+ service breadth is a liability: well-known services (Postgres, Redis, n8n) work reliably, but obscure ones have spotty issue tracker histories — you may find you're the first person to hit a specific edge case. 3. Background job reliability is a known pain point; Horizon queue failures can leave deployments stuck with no clear recovery path beyond manual SSH intervention. 4. Real-time container status depends on a separate Sentinel sidecar; when it gets out of sync the UI shows stale state, which erodes trust in the dashboard during incidents.