If you’re comfortable managing servers, backups, monitoring, networking, and upgrades, the cost savings and control can be compelling. But for a customer-facing SaaS, I would also want to know how much time those responsibilities actually consume over six or twelve months.

I think I will probably look at Coolify less from the “how easy is it to deploy?” angle and more from “how much work will it still be giving me months later?” If I am constantly dealing with backups, updates, monitoring, failed deployments, or server issues, then the cheaper setup may not really feel cheaper anymore. For me, I would only choose it again if the control and savings still made sense after counting the time spent maintaining everything myself.
Speaking from my own point of view though.

Getting started is one thing, but long-term reliability and maintenance are where self-hosting truly gets tested. The real questions are always about what happens after the initial deployment excitement fades upgrades, stability, and whether the cost savings actually hold up.

The long term maintenance side is what I’d love to hear about too. Getting a SaaS utilized quickly is one thing but reliability, upgrades, backups, monitoring and troubleshooting are what really determine whether self hosting is worth it. I’d be really interested in hearing from teams that have used Coolify for months in production because that experience probably says more than the initial setup time.

Coolify gets interesting after the honeymoon period. The part I’d want to know is how it behaves when something goes wrong at 2 AM. A failed deployment, broken container, expired certificate, or bad update tells you much more about a self-hosting platform than how quickly it can deploy an app. I’d also be curious whether people eventually build their own layer of scripts and monitoring around Coolify. If you need a growing collection of workarounds to make production reliable, the initial simplicity starts losing its value.

What interests me most here is the difference between getting a deployment running and actually maintaining it over time. A tool can feel very convenient at the beginning, but production use brings a completely different set of concerns around updates, backups, monitoring, security, and troubleshooting. I’d also be interested in hearing how much hands-on maintenance people ended up doing after their initial setup.

Another advantage I see is portability. With a setup based around Docker and infrastructure you control, you’re not necessarily tied to one hosting provider’s particular deployment model. That can be useful for a growing SaaS. You can start small on a VPS and move to larger infrastructure later without completely redesigning how the application is deployed.