They run their 8-person agency's tooling on 2 cheap VPS managed through Coolify and call it one of their favourite tools, handling deployments and infrastructure. They have also moved client workloads from AWS and Vercel to it.
Every service, ranked by real customers
We read Reddit, YouTube and blogs so you don’t have to. Every review links to its source.
Latest managed cloud reviews
Freelancer here. I run 11 small client WordPress sites on one Hetzner VPS with the Essentials plan. Unlimited web apps on a single server is what makes the maths work for me. The panel takes care of the dull parts: setting up the stack, free SSL, picking the PHP version per app, scheduled backups, and one staging site where I test plugin updates first. Keep in mind you still pay Hetzner for the server, RunCloud only manages it. Prices have gone up more than once since I signed up, and API access is now only on the Business tier, which annoyed me. One time an agent update failed and I had to update it by hand over SSH. Support is ticket based, they answered within a day and were polite but it's not instant.
They run one Coolify on a single VPS for a Next.js app and find day to day deploys are just git push. The proxy being Traefik cost them debugging time because many older guides use Caddy labels.
View original sourceThey run Coolify across two servers for side projects and client sites and like its one-click services and template library. They find it heavy on resources and say the UI gets confusing as servers are added.
View original sourceThey ran Coolify on a single VPS for small apps and internal tools and stayed because it needed so little attention day to day. They could drop down to plain compose when a tweak was needed.
View original sourceThey found Coolify extremely resource hungry for how little it does, with critical bugs in persistent storage handling for compose services, and would not use it in production.
View original sourceAfter more than three years of use, steep upcoming price increases could no longer be justified and prompted a move to CloudPanel.
View original sourceSeems stable enough now that little is left besides security updates, but it isn't used often because you eventually outgrow it and need stronger security than giving a third party full server access.
View original sourceMoved from Envoyer to Forge's zero-downtime deployment, though it is not as well supported for multi-site setups.
View original sourceKeeps a project with a lot of self-hosted setup running without moving to cloud, which would be a huge undertaking with no return; it just works as is for now.
View original sourceThey are a long-time Coolify user who finds it robust but says it eats too many resources compared with alternatives.
View original sourceMoved off because it only supported Ubuntu and they did not want Ubuntu 26.04; they now run AI-written config scripts and use Caddy instead of nginx for flexibility.
View original sourceThey say Coolify makes system updates easy and even notifies them when an update is due. They add that the main overhead is keeping project dependencies current.
View original sourceThey say they just love Coolify for deployments.
View original sourceThey tried Coolify but dependencies would not start after deployment and they filed a GitHub issue.
View original sourceThey ran Coolify and Dokploy in low-stakes production and found Coolify has a larger community, built-in S3 backups and multi-server support. They say the cost is more surface area, with upgrades occasionally touching unexpected things.
They tried Coolify and Dokploy, had problems with Dokploy, and found Coolify more stable. They like its recently refreshed UI and constant updates, and plan to keep using it.
View original sourceLack of SQLite support and rigid cloud constraints required too many workflow changes compared to a traditional server setup.
View original sourceClean user interface and reliable operation prompted a move back after trying an alternative panel.
View original sourceStraightforward and easy to set up when hosting a WordPress site.
View original sourceHappy with it and sees no need to migrate dozens of servers; starting on it made an alternative panel's UI feel confusing.
View original sourceWorks well for tiny side projects or full-scale businesses, but pricing shifts made mid-sized projects too expensive and custom processes are restricted.
View original sourceThey used Coolify and replaced it with Dokploy because they wanted lower resource usage on their server.
View original sourceUsing Cloudways with Vultr for a while with solid performance and no need to move.
View original source