What it is
You’ve built a website or an app. It works beautifully on your computer. Now comes the awkward part: getting it onto the internet and keeping it running. Coolify makes that part considerably easier.
Think of Coolify as a control room for your own servers. Instead of remembering a collection of commands to install an application, connect a domain, arrange HTTPS and check whether everything is still running, you do much of it from a friendly dashboard. Coolify can deploy websites, apps, databases and ready-made services, then show you their logs, settings and status.
You bring the server. That might be a rented VPS (a virtual private server, essentially a computer you rent on the internet), a machine at home or another Linux server you control. Coolify connects to it over SSH, the usual secure way of managing a server remotely. It can take a project from GitHub and turn it into a running application, or start a ready-made Docker image without needing any code.
There’s a useful choice from the beginning. Self-hosted Coolify is free software that you install and manage yourself. With Coolify Cloud, the Coolify team operates the dashboard for you, but your apps still run on servers you provide. Both offer the same core features. You choose who looks after the control room.
What’s new
The recent 4.7 release makes Coolify more useful after the excitement of the first deployment has worn off.
Less wasted work when you push code. Imagine making three changes to an app in quick succession. Previously, all three might queue up for deployment. Coolify can now cancel older queued deployments triggered by Git changes so it concentrates on the newest version. Manual deployments and rollbacks aren’t swept away by that default.
Better visibility into security. Coolify added optional container-image vulnerability scanning. A container image is the packaged software your server runs; scanning it can highlight known security issues and suggest newer versions. The scans run on your server, with results available in the dashboard.
More useful backups. Database and storage backups gained additional destinations, including SFTP, FTPS and WebDAV. These give you more ways to store copies away from the server doing the work. Coolify also expanded its API and MCP tools, making it easier to manage deployments and inspect security findings from other software or AI assistants.
Version 4.7.5 follows with smaller fixes for API-token settings and IPv6 backup connections. Not every improvement needs fireworks; it’s rather nice when the everyday controls simply become more dependable.
What else is similar to it
Dokploy is probably the closest comparison. It also lets you deploy apps and databases to servers you control, with Docker Compose, backups, monitoring and templates for common services. It’s worth comparing the dashboards and deployment workflows if you’re choosing a self-hosted home for several projects.
CapRover offers another straightforward route from an app to a running service. It’s built around Docker, with its own web dashboard, HTTPS and app-management commands. It can be attractive if you want a simpler, established deployment approach.
Services such as Heroku or Vercel take a different approach: you deploy to infrastructure operated by the provider. That’s wonderfully convenient when you don’t want to manage a server. Coolify gives you more say over where your software runs, while leaving server upkeep in your hands.
The deciding question is surprisingly ordinary: Do you want someone else to host the whole thing, or would you rather operate your own servers with a dashboard doing much of the repetitive work?
Why it’s different
Coolify’s appeal isn’t that it invented deployment. It’s that it brings several jobs together in one place. Connect your code, choose how to build it, add your domain and deploy. Coolify can take care of the container, routing and HTTPS certificate, and show you what happened if a deployment fails.
It can also manage databases and hundreds of ready-made services. That makes it handy for a small product with several moving parts: a website, an API, a database and perhaps an analytics tool. You can manage them together instead of maintaining a separate set of instructions for every service.
A particularly reassuring part of the design is that the actual applications run as ordinary containers on your servers. Coolify is the management layer, not a special runtime your software must depend on forever. If you stop using the dashboard, those running containers don’t suddenly evaporate.
Of course, a tidy dashboard doesn’t magically maintain the machine underneath. Your server still needs updates, sufficient memory and backups that can actually be restored. Coolify removes a great deal of deployment busywork; it doesn’t remove ownership. For someone who likes controlling their own infrastructure, that’s the attraction rather than the catch.
How to get started
- Choose your route. With self-hosted Coolify, you’ll install the dashboard on a Linux server. With Coolify Cloud, you’ll create an account and connect a server you own. Cloud manages the dashboard, not the server where your app will run.
- For self-hosting, a spare Linux server is ideal for your first try. Coolify’s starting requirement is 2 CPU cores, 2 GB RAM and 10 GB free disk space, plus room for anything you deploy. You’ll need SSH access as a user able to administer the server.
- You won’t need a GitHub repository or even a domain for the first experiment. We’ll deploy a ready-made Nginx webpage, so you can see the whole process work before adding your own code.
- Self-hosted route: connect to your Linux server using SSH and follow the official installation guide. Its installation command is
curl -fsSL https://cdn.coollabs.io/coolify/install.sh | bash. It will print an address for the dashboard when it finishes. Open that address and create your administrator account promptly. - Coolify Cloud route: follow the Cloud setup guide to sign up, connect your server using SSH and confirm Coolify can reach it. You can then follow the same deployment steps as self-hosted users.
- In the dashboard, open Servers and check that your server is connected and its proxy is running. The proxy is the part that sends visitors to the correct application; Coolify can start it from the server page.
- Create a project, add a new resource of type Docker Image, enter
nginx:alpine, and set the exposed port to80. Press Deploy. Coolify should give you a generated address; open it to see the Nginx welcome page. That’s your first application, running on your server.
- Can’t reach the self-hosted dashboard? Use the address printed at the end of installation, check that the server is reachable and that the dashboard’s port is permitted by your firewall. The installer normally shows a URL using port
8000. - Registration says the setup window closed? The first administrator account can be created during a short setup window. On the server, run
docker restart coolifyto reopen it, then create the account. - The Nginx app deployed but the link won’t open? Check that the server’s proxy is running, the container is healthy, and ports
80and443are reachable. The first-app guide walks through these checks. - Ready to deploy something important? Save the Coolify installation secrets and configure backups. For self-hosting, the file
/data/coolify/source/.envcontains keys needed to restore your Coolify instance. Back up your application data separately, whether you use self-hosted or Cloud.
Explore further: Choose self-hosted or Cloud · Install Coolify · Deploy your first app · Coolify on GitHub · What’s new in 4.7.
