Dora NodaCoolify is selling something self-hosters swore they would never buy: someone else running the dashboard. The code is identical — Apache-2.0, no feature gating, the self-hosted version is the full product — yet more than 3,400 people pay $5 a month for Coolify Cloud instead of running it free on their own box. That $5 receipt is the cleanest measurement the self-hosting world has ever produced of the operate-it-yourself tax: the dollar value of not babysitting the control plane.
This post works out that tax exactly. What the managed tier costs at 1, 2, 5, and 10 servers against the same Hetzner boxes self-hosted. What the $5 buys and what stays your problem. And where the managed middle tier stops making sense — in both directions, versus pure self-hosting and versus a fleet that provisions the machines too.
The price, exactly
Coolify has two tiers and no price grid. Self-hosted is free forever: every feature, unlimited servers, unlimited deployments, unlimited team members, community support via a 19,000-plus-member Discord. Cloud is a flat convenience fee for the identical codebase:
| Monthly | Annual (effective) | |
|---|---|---|
| Base (includes 2 connected servers) | $5/mo | $4/mo |
| Each additional server | +$3/mo | +$2.70/mo |
| Servers, deployments, team members | Unlimited | Unlimited |
Three details matter. First, one server still pays the full $5 base — the second slot is capacity, not a discount. Second, annual billing saves 20% across the board. Third, each additional team workspace needs its own subscription, so isolated environments with separate billing multiply the base. There are no per-seat fees, no execution limits, no credit system.
The model underneath is "bring your own servers." Coolify's own FAQ puts it plainly: you bring servers from any provider, your apps deploy onto them, and Coolify itself runs on managed infrastructure. You are not buying hosting. You are buying someone else runs the Coolify dashboard for me — Coolify-as-a-service, not a cloud PaaS.
The worked totals: self-hosted vs Cloud on the same boxes
Here is the core deliverable: both sides summed to a total, servers included, on identical hardware. The reference box is a ~$5/mo Hetzner-class VPS with 2 vCPUs, 4 GB of RAM, and 40 GB of NVMe (4 GB, not 2, because Coolify recommends a 2 GB minimum and a 2 GB box leaves no headroom for actual workloads). CapRover, for reference, sits at a $0 self-hosted-only anchor with Swarm-based clustering — proof the Cloud fee buys zero exclusive features.
| Servers | Self-hosted total | Cloud total | Cloud delta | Fee as share of Cloud total |
|---|---|---|---|---|
| 1 | $5/mo | $10/mo | +$5 (+100%) | 50% |
| 2 | $10/mo | $15/mo | +$5 (+50%) | 33% |
| 5 | $25/mo | $39/mo | +$14 (+56%) | 36% |
| 10 | $50/mo | $79/mo | +$29 (+58%) | 37% |
Read the table two ways, because both are true. In absolute dollars the fee is trivial at every scale: $5 to $29 a month for a managed control plane, where 8 services on Railway or Render can carry $100–200 a month in platform fees alone. Annual billing trims another 20%, taking the 10-server fee from $29 to about $26.
In relative terms the fee is large because the boxes are so cheap. At one server you double the stack cost, and every server past the second carries a permanent $3 surcharge on a $5 box — a 60% marginal markup that the blended rate asymptotes toward as you grow. The fee never fades into the noise the way a $5 add-on would on a $500 cloud bill.
Two symmetries sharpen the picture. First, the $5 base is roughly the price of a second $5 box — meaning Cloud costs about the same as self-hosting the panel on its own dedicated VPS for isolation. Second, the category has converged: Dokploy Cloud's Hobby tier prices its managed panel at roughly $4.50 per server, so the whole market values running the dashboard for you at $3–5 per server per month. That is the going rate for this job.
What the $5 buys — and what stays yours
The buys list is short and honest:
- Managed updates, tested before they reach you. Self-hosted Coolify offers automated or self-managed updates, so the gap is not automation — it is that Cloud updates are validated against the managed fleet first. You skip the changelog-reading and the occasional bad-release morning.
- An off-box dashboard. This is the genuinely architectural benefit. Self-hosted Coolify usually lives on the same box it manages, so you lose the panel exactly when you need it most — during an outage on that box. Cloud's panel survives your server dying, which means deploy history, logs, and one-click rollbacks stay available while you debug the dead machine over SSH.
- Email alerts for Coolify events. Deploy failures and server-health events reach your inbox without wiring your own monitoring to the panel.
- Limited email support on top of community support. Someone to email when the Discord cannot answer.
Now the stays-yours list, which is longer and matters more:
- The server bills. Every box is still yours to pay for, at every tier, forever.
- Reachability. If your server is unreachable over SSH — expired firewall rule, dead network route, host-null-routed IP — the managed panel cannot reach it either. Cloud manages Coolify, not your machines.
- The Docker host and the OS. OS patching, Docker Engine updates, disk-full troubleshooting, and kernel upgrades on every box remain your toil. Coolify never touches the host layer.
- Your application data. Backups of your databases and volumes are your design and your cron job; the panel orchestrates the containers, not your disaster recovery.
The honest bear case for Cloud fits in one sentence: installing Coolify takes about a minute, auto-updates exist, and the ongoing burden is on the order of fifteen minutes a month — so the fee is pure time-value arbitrage, worth it only if your fifteen minutes are worth more than $5.
Where the middle tier breaks
The managed tier is a middle, so it has two edges. It breaks downward against pure self-hosting and upward against fleets — and the two breaks have different causes.
Downward: the single-server double-pay. At one server, Cloud doubles your stack cost from $5 to $10 for a dashboard that manages one box. The off-box argument is weakest here too: the panel you are paying to isolate is orchestrating a single machine you could SSH into directly.
If you are comfortable managing a VPS at all — and you must be, since the box stays yours either way — the $5 buys the least where most solo developers actually live. This is the segment where just self-host it is nearly always the right answer, and where the free self-hosted tier keeps Cloud honest. The multi-workspace rule sharpens the same edge: a freelancer isolating each client's servers in its own workspace pays a fresh $5 base per client, which reframes Cloud from "coffee money" into a per-client line item.
Upward: no tier provisions machines. This is the structural ceiling. At 2 servers or 20, every box behind a Coolify dashboard — self-hosted or Cloud — was hand-created: clicked into existence in a provider console or Terraform, SSH keys distributed, firewall rules written, OS image chosen, Docker installed. Cloud removes the dashboard toil and none of the machine toil. Ten servers means ten individually created, patched, and firewalled machines plus a $29/mo fee; the fee line stays flat-ish while the machine toil grows linearly, and no managed dashboard flattens that curve.
That is the exact seam a Cluster API fleet is built to not have. In a CAPI-managed fleet, machines are declared like any other resource — MachineDeployments describe the desired node set, controllers reconcile reality toward it, and capacity scales through the same GitOps loop as the workloads. Node autoscaling on owned hardware, rolling machine-image upgrades, and drift reconciliation all follow from the machine lifecycle being declarative rather than manual.
So the two products answer different questions: Coolify answers who runs the deploy panel, while a CAPI fleet answers who provisions and heals the machines. Once your toil is machines — provisioning, patching fleets, replacing dead nodes, autoscaling — a managed panel, however cheap, is solving the wrong layer. The $5 fee is irrelevant at that point, not because it is too expensive but because the dashboard was never the bottleneck.
The verdict
Three buyers, three answers:
- Pay for Cloud if you run 2–5 servers, value your time above $5–14 a month, and want the panel alive during your own outages. The off-box dashboard alone justifies it for anyone running something production-adjacent on a single VPS.
- Self-host if you run one server, enjoy VPS toil, or simply refuse a 100% surcharge on a $5 box on principle. The product is identical; the install is a minute; auto-updates cover most of the burden.
- Outgrow both when adding the eleventh server sounds like a weekend. If your week is spent provisioning machines, patching hosts, and hand-holding capacity, you do not have a dashboard problem — you have a machine-lifecycle problem, and the fix is declarative fleet management, not a managed panel.
Coolify deserves credit for making the tax legible. Most of infrastructure pricing hides the operate-it-yourself cost inside bundled compute bills; Coolify unbundled it, priced it at $5, and let 3,400-plus customers vote with their wallets. The vote says the dashboard is worth about a coffee a month — and the worked math says everything underneath the dashboard is still, firmly, your job.
Comparing self-hosted PaaS options for your next deploy? Bex.co is the open-source, AI-native Render alternative — push a git repo, get a running HTTPS service on machines you own. Star the repo on GitHub or deploy your first app today.
