The self-hosted PaaS pitch goes like this: "Install Coolify on a VPS, get your own Heroku for €5/month." Coolify is genuinely good software — this piece exists not to trash it, but to separate "free software" from "free platform". A €5 VPS invoice reads €5; the rest you pay yourself — in hours, downtime and the 3am pager.
As people who have run both models, here is an honest total cost of ownership (TCO) breakdown — including where Coolify is still the right answer.
What Coolify Actually Gives You
Credit where due: Coolify (and peers Dokploy, CapRover) turns a VPS into a mini-PaaS. Git push → build → deploy, SSL, log viewer, many projects on one panel. Open source, zero license fee. It genuinely works on a €5 Hetzner box and impresses in demos.
The problem is not the software — it is everything standing around the software that belongs to you.
The Invisible Invoice: €5 + Everything Else
| Item | Self-hosted (Coolify) | Managed PaaS (Skyversal) |
|---|---|---|
| Software license | ₺0 (open source) | Included in plan |
| Server (VPS) | €4-15/mo, grows with you | Included |
| OS updates, kernel, patching | You — weekly routine | Us |
| Docker/Coolify upgrades | You — breakage also yours | Us |
| SSL, firewall, fail2ban, port hygiene | You | Us |
| Monitoring, alerts, uptime | You install it (Uptime Kuma etc.) | Built-in |
| Backups + restore drills | You design them; untested = none | Automatic + PITR |
| Disk full at 3am | You wake up | We wake up |
| Database care (vacuum, replica, upgrades) | You | Managed |
The right column is not "free" — it is bundled into the plan price. The left column looks free but costs your hourly rate × monthly ops hours. One incident that eats two hours of a freelancer's time pays back the €5 saving several times over.
Three Real Scenarios — Who Should Pick What
Coolify is the right call:
- You already run a server fleet and Linux ops is part of your job
- Internal tools, staging, personal projects — workloads where downtime is tolerable
- Air-gapped / full-control environments (own datacenter, closed networks)
- You want to learn — Coolify is a superb sysadmin teacher
Managed PaaS is the right call:
- Customer-facing, invoiced, SLA-talking workloads — downtime is literally money
- Developers/teams who don't want to do ops or can't spare the hours
- Your one-person "SRE team" deserves a vacation
- You want end-to-end management including the database (backups, PITR, monitoring)
The Bonus: Currency and Data Residency
You can self-host on a Turkish VPS too — but then you are the sysadmin and you vet the VPS provider's quality yourself. Managed + Turkey-located kills two concerns at once: on the KVKK residency side the cross-border transfer machinery never arises, and TRY pricing removes exchange-rate surprises.
The Decision Formula
Ask one question: "How many maintenance hours will this server cost me in the next 6 months, and what are those hours worth?"
- 1 hour/week of ops + 1 incident/month × 3 hours ≈ 7 hours/month — at a modest ₺500/hour that is ~₺3.500/month, roughly 10× a Pro plan.
- If your ops hours are near zero and the server already exists — Coolify stays free and you win.
Both paths are legitimate. The only illegitimate choice is buying "a €5 free PaaS" and discovering the invoice at 3am during an outage.
FAQ
Isn't Coolify free?
The software is free (open source). The platform is not: VPS rent plus the hours you spend on updates, monitoring, backups and incident response is the real cost.
Coolify vs Dokploy?
Same class of self-hosted PaaS; they differ in community size and feature details. The TCO analysis in this article applies identically — the question is the model, not the product.
Where does Skyversal win and lose?
Wins: zero ops, managed DB/backups/monitoring, Turkey region, TRY pricing. Loses: if you already operate a fleet or need air-gapped control, self-hosting is cheaper and gives you more control.
Is migrating from Coolify hard?
Both speak the git-deploy model: repo + env + build command. A typical project migrates the same day; move the database with the steps in our docs.