Every service, ranked by real customers

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.

They 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.

They 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.

They 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.

After more than three years of use, steep upcoming price increases could no longer be justified and prompted a move to CloudPanel.

Seems 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.

Moved from Envoyer to Forge's zero-downtime deployment, though it is not as well supported for multi-site setups.

Keeps 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.

They are a long-time Coolify user who finds it robust but says it eats too many resources compared with alternatives.

Moved 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.

They 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.

They say they just love Coolify for deployments.

They tried Coolify but dependencies would not start after deployment and they filed a GitHub issue.

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.

Lack of SQLite support and rigid cloud constraints required too many workflow changes compared to a traditional server setup.

Clean user interface and reliable operation prompted a move back after trying an alternative panel.

Straightforward and easy to set up when hosting a WordPress site.

Happy with it and sees no need to migrate dozens of servers; starting on it made an alternative panel's UI feel confusing.

Works well for tiny side projects or full-scale businesses, but pricing shifts made mid-sized projects too expensive and custom processes are restricted.

They used Coolify and replaced it with Dokploy because they wanted lower resource usage on their server.

Using Cloudways with Vultr for a while with solid performance and no need to move.

They ran Coolify on 4GB of RAM without problems and later moved to 8GB for headroom. They say it has some overhead but has been fine for them.

They run Coolify on a VPS managing a dozen docker apps auto-deployed from GitHub pushes. They do not feel locked in, are moving off Vercel and have had no RAM issues.

They use Coolify for most of their deployments and fall back to manual docker compose for the finicky ones.

Used at work for Laravel apps, with automatic zero-downtime deployments, auto-deploy on new releases, and management of workers and queue jobs, and considered probably the best way to get it just working.

Platform stability has improved since launch and migrating from Vapor was fast, though support responses across paid tiers can still be slow.

They moved from Vercel to self-hosted Coolify and have never looked back.

Works great for managing VPS servers with zero downtime.

Auto-scaling eliminated server maintenance and weekend provisioning worries for five e-commerce apps, though a stuck 20-hour deployment exposed slow support.

Brief trial ended quickly because the platform did not support running Puppeteer for the project.

They use ServerPilot on their DigitalOcean droplets and find it makes server setup simple.

Has been with Cloudways for years and never felt any reason to leave.

A great product but RunCloud means friction: server commands to add disk space and failed agent updates needing manual installs.

Runs around 100 sites across 9 Linode and Vultr servers on RunCloud and calls it flawless.

They deployed a client web platform with Next, MongoDB and Redis managed via Coolify and say it ran like clockwork.

Ten days and nine Cloudways support agents could not resolve a Google InspectionTool "blocked by robots.txt" error, finally calling it out of scope.

They could not get Coolify installed on Ubuntu 24.04: they had to change the DB password manually and the real-time service and localhost were unreachable, a very frustrating experience.

They run a couple of Node apps on a cheap VPS with Coolify. They found setup painless, with GitHub repo builds and deploys handled automatically.

Early adopter preparing to leave the platform because current pricing has become extortionate.

Automated server backups work without needing external WordPress plugins after switching over from RunCloud.

Using Linode servers with the control panel for a handful of clients has never brought a server down, and a good VPS with a server panel is seen as unbeatable on price and performance.

Ridiculous API pricing prompted a move of their servers away from RunCloud to an alternative panel.

Ships apps super quickly, though from India the nearest Singapore region adds noticeable request latency compared to a local VPS.

After years of nightmare hosts, found Cloudways a godsend: fast, affordable with great tech support.

They have been using Coolify and so far really like it. They have not tried Dokku.