Coolify

What it is

Coolify is "self-hosting" software: instead of paying Vercel, Netlify or Heroku to run your app, you rent a plain server (a VPS, a virtual private server, from a company like Hetzner for a few dollars a month) and Coolify gives it a friendly dashboard.

From that dashboard you connect a GitHub repo, and Coolify builds and deploys the app on every push, sets up HTTPS for your domain, and runs databases like Postgres. It also has more than 360 one-click services, such as analytics, n8n or uptime monitors. Under the hood it's Docker containers behind a Traefik proxy.

It's free and Apache-licensed, with an optional paid Coolify Cloud. After years labelled "beta", version 4.0 became stable on 2026-04-27. There's also a read-only MCP server, so an agent like Claude Code can look up your deployments and logs.

What actually happens when you use it

1. Rent a server. A fresh Ubuntu or Debian machine with at least 2 cores and 2GB of RAM. Coolify recommends one server for Coolify and others for your apps, though one box works to start.
2. Run the installer. One command, as root, sets up Docker and the dashboard on port 8000. You create the admin account in the browser.
3. Connect git and deploy. Point it at a repo. It detects how to build the app, or uses your Dockerfile, and redeploys on every push, with optional preview builds for pull requests.
4. Add a domain. Point your DNS at the server and Coolify fetches HTTPS certificates automatically.
5. Set up backups yourself. Database backups to S3-style storage are built in, but you have to configure them and check they run.
6. Keep it updated. Coolify updates from its dashboard. You still own the operating system, firewall and SSH access underneath.

What people like

• It feels like Heroku at VPS prices. One Hacker News user ran Hetzner plus Coolify for a year and called it a great Heroku-like experience that's easy on the wallet. Another said it turns countless settings into a few intuitive buttons.
• Many people run real things on it. Hacker News commenters this month use it for their vibe-coded apps and for smaller Docker apps alongside other tools.
• Happy small-scale users. On r/selfhosted, one person running apps on a VPS with Coolify said they're happy with it at their scale.
• Security fixes ship fast. When two critical PHP flaws landed in October, the team backported the fix to every 4.x line the same day, and the issue filled with users thanking them for the quick rollout.
• No lock-in. Apps run as normal Docker containers, and the README says they keep running if you stop using Coolify.

What people run into

• A heavy security record. In January, researchers disclosed 11 critical flaws, several letting a logged-in user run commands on the server as root. Censys counted about 52,890 exposed instances, and Belgium's cyber agency told organizations to patch immediately. By our count, more than 60 advisories were published in the last year, 16 rated critical. No exploitation in the wild had been reported at the time of the January disclosure.
• Updates can break things quietly. After one upgrade, scheduled backups of Coolify's own database silently stopped running. Another user saw random build failures after updating to 4.1.
• The server work never ends. A senior front-end developer who set up Hetzner plus Coolify said they were drowning in firewall, Cloudflare and resource-limit settings. A first-time self-hoster was startled by 2,000 bot requests within hours of going live, which replies said is normal once you get an HTTPS certificate.
• Backups aren't production-grade out of the box. One commenter called it hobby-grade until it supports streaming database backups. Another found it can lose track of containers it started.
• Some people leave for alternatives. Users have moved to Dokploy for its interface or to Komodo after hitting broken behaviors. For a single app, some say plain Docker Compose is less to maintain.
• One server is one point of failure. If the box goes down, so does everything on it. A blunt r/selfhosted reply warned against hosting customer data without DevOps experience.

Before you install

• Don't leave the dashboard open to the internet. Put it behind a private network like Tailscale, as one commenter advised in a thread about this week's Railway security incident, and close public SSH, as suggested on r/selfhosted.
• Update quickly, and subscribe to security news. Watch the advisories page or the releases. As of 2026-10-23, anyone below v4.4.7 should update now; if you're still on an old beta, go straight to v4.4.7, since the patch route for older lines fails on betas.
• Back up off the server, then test a restore. Send database backups to outside storage, and save the /data/coolify/source/.env file, which the docs say you need to restore Coolify. Check backups still run after each update.
• Build somewhere else if you can. Builds can make the server unresponsive, so the docs and experienced users suggest keeping heavy builds off the box that serves your app.
• Consider Coolify Cloud. At $5 a month for two servers, it takes the Coolify dashboard off your plate. Your app servers are still yours to patch.

The short version

Coolify really does turn a cheap server into a personal Vercel, and plenty of people run side projects on it happily. But it moves the hard parts, like security updates, backups and uptime, from a hosting company onto you, and this year Coolify itself was a big part of that security workload. If you're excited to learn server basics, try it on a side project. If you just want your vibe-coded app online and safe, pay for managed hosting.