Coolify
Open-source, self-hostable PaaS that gives you most of Heroku/Netlify/Vercel — push-to-deploy apps, managed databases, and 280+ one-click services — running entirely on servers you own, billed by your VPS instead of per-seat/usage. Source: coollabsio/coolify, https://github.com/coollabsio/coolify, 2026-06-12
Coolify (by Andras Bacsai / coollabsio) is the most prominent open-source answer to "I want Vercel's DX without Vercel's bill." You point it at any VPS (Hetzner, DigitalOcean, a home server), run a one-line curl installer, and get a web control plane that builds from Git, manages SSL, and deploys static sites, full-stack apps, databases, and services as Docker containers. As of 2026-07-04, coollabsio/coolify is Apache-2.0 with 57,839 GitHub stars, 4,912 forks, 809 open issues, default branch v4.x, latest release v4.1.2, and branch HEAD e7dff30 (v4.1.2 (#10452)). Source: coollabsio/coolify, 2026-07-04
What it does
| Capability | Detail |
|---|---|
| Install | One command (curl ... | bash) on a fresh Linux server. |
| Deploy | Git push-to-deploy; Dockerfile, Docker Compose, or auto-detected build (Nixpacks/buildpacks). |
| Databases | Postgres, MySQL, MariaDB, Redis, MongoDB, KeyDB, etc. provisioned in a click, with scheduled backups (S3-compatible). |
| Services | 280+ one-click open-source apps (Ghost, Plausible, Supabase, n8n, Umami, …). |
| TLS / domains | Automatic Let's Encrypt certificates, custom domains, reverse proxy (Traefik/Caddy). |
| Ops | Multi-server management, webhooks, preview deployments, env-var management, server resource monitoring. |
Why it shows up in Kevin's signal
Coolify is the flagship of the "RIP Vercel bills" / anti-PaaS turn — developers reacting to per-usage cloud pricing by moving back to a single owned box. The bookmarked launch framed it exactly that way ("RIP Vercel bills... runs entirely on your own server"), and the reviewed screenshot preserves the README-era pitch: open-source/self-hostable Heroku/Netlify/Vercel alternative, one-command installer, owned hardware via SSH, no vendor lock-in, 280+ services, and built-in databases. The image's 4.0.0-beta.470 badge is historical evidence, not the current version authority. Source: X/@sentient_agency and local image review, 2026-07-04
The same sentiment recurs across the corpus: builders replacing managed Vercel+Supabase stacks with k3s/Flux CD and self-hosted Postgres, and the BYOC ("bring your own cloud") posture for selling to enterprise. The @BadAINoData reply names the concrete anti-PaaS bundle: a dedicated server, k3s, Flux CD, Envoy Gateway, self-hosted Supabase, CloudNativePG, Redis, and Qdrant replacing small managed Vercel/Supabase plans. The @albert_ thread is the enterprise sales version of the point: be on-prem ready by containerizing, using Postgres behind an ORM, avoiding one-cloud lock-in, and provisioning infra with Terraform. The self-thread adds the important operational boundary: do BYOC, not unmanaged customer self-hosting, so the vendor can still operate the software while the customer keeps it inside their environment. Source: X/@BadAINoData, 2026-04-24; Source: X/@albert_ thread, 2026-05-22
It sits opposite the SaaS Stack 2026 default (Vercel + Supabase + Stripe) on the build-vs-own axis, complements Floci (run AWS-shaped services locally) for offline/integration testing, and overlaps Render Cloud Platform as a managed-deploy alternative — except Coolify hands you the control plane instead of renting it.
In Modern Web VPS Stack, Coolify is optional. Use it when a Hetzner server should feel like a small PaaS for TanStack/Vite apps, databases, services, domains, TLS, env vars, and previews. Skip it when Docker Compose/systemd plus a reverse proxy is simpler and the app does not need a UI control plane. Source: User request, 2026-07-06
The tradeoff
Self-hosting moves cost from a usage meter to a flat VPS bill and removes vendor lock-in, but you own the operational surface: OS patching, Coolify upgrades, uptime, and security are now yours. Coolify also offers a paid Cloud (a managed control plane that still deploys to your servers) for teams that want the DX without hosting the Coolify instance itself. Pick it when predictable cost and data ownership beat zero-ops; stay on managed PaaS when ops time is the scarce resource. Source: coollabsio/coolify, 2026-06-12
Install candidate (Apache-2.0, ~57K stars). It changes server state — run the three-gate chain (Brin → skill-auditor → reputation) and review the installer before running it on any box, per AGENTS.md.
Timeline
- 2026-07-06 | Linked Coolify into Modern Web VPS Stack as the optional PaaS/control-plane layer for Hetzner-hosted TanStack/Vite apps. Source: User request, 2026-07-06
- 2026-07-04 | Deep-reviewed the X bookmark image and refreshed source status. Screenshot preserved the anti-PaaS positioning and historical
4.0.0-beta.470README badge; GitHub source check moved the current authority tov4.1.2, branch HEADe7dff30, Apache-2.0, 57,839 stars, and 4,912 forks. Source: X/@sentient_agency, GitHub, local image review, 2026-07-04 - 2026-07-04 | Source-reviewed @albert_'s BYOC/on-prem readiness thread. Promoted it as enterprise deployment posture evidence: be portable enough for customer-owned infrastructure, but avoid unmanaged customer self-hosting when BYOC lets the vendor keep operational control. Source: X/@albert_ thread, 2026-05-22
- 2026-07-04 | Added the @BadAINoData self-host stack reply as concrete anti-PaaS evidence: dedicated server plus k3s/Flux/Envoy/self-hosted Supabase/CloudNativePG/Redis/Qdrant as the named alternative bundle. Source: X/@BadAINoData, 2026-04-24
- 2026-04-07 | @sentient_agency surfaced Coolify ("RIP Vercel bills… free, open-source PaaS, one-command install, 280+ one-click services, Postgres/Redis/MySQL/MariaDB built-in"). 220 likes, 245 bookmarks. Source: X/@sentient_agency, 2026-04-07
- 2026-06-12 | Dedicated page created from dev-tools bookmark absorption; researched repo (
coollabsio/coolify, Apache-2.0, ~57K stars). Anchored the recurring anti-PaaS / self-hosting theme (BYOC, k3s/Flux). Source: x-bookmark-absorb, 2026-06-12