Deploying Apps Without the Cloud Tax
Coolify is an open-source platform that lets you deploy and manage web applications, databases, and services on your own servers – without routing everything through AWS, Render, or Heroku. The pitch is straightforward: you bring a server, Coolify handles the deployment interface, SSL certificates, reverse proxy configuration, and environment management. What you get is something that looks and behaves like a managed cloud platform, except the infrastructure bill goes to you directly, usually at a fraction of the cost.
The appeal goes beyond saving money. Coolify gives you full control over your data, your deployment pipeline, and your server configuration. There are no usage limits tied to a pricing tier, no vendor lock-in, and no black-box restrictions on what runtimes or languages you can deploy. If your server can run Docker, Coolify can work with it. The setup process is designed to be completed in under an hour, even for someone who has never managed a Linux server before.
What You Need Before You Start
Coolify runs on a single VPS or dedicated server. The minimum requirement is a machine running Ubuntu 22.04 or Debian 11 with at least 2 CPU cores and 2GB of RAM, though 4GB is more realistic if you plan to host more than one or two apps. A fresh server is strongly recommended – running Coolify alongside an existing web stack can create port conflicts with its built-in Traefik reverse proxy. You will also need a domain name or subdomain pointing to your server’s IP address if you want SSL to work automatically through Let’s Encrypt.
SSH access is required. Coolify installs everything through a shell script that pulls Docker, sets up its own internal network, and launches the management dashboard on port 8000 by default. Before running anything, make sure port 8000 is open in your firewall, along with ports 80 and 443 for web traffic. If you are using a cloud provider like Hetzner, DigitalOcean, or Vultr, this means adjusting both the provider’s firewall rules and your server’s UFW settings.
Running the Installation
The installation command is a single line. SSH into your server as root and run the official install script from Coolify’s GitHub repository using curl piped into bash. The script handles everything: Docker installation, Docker Compose setup, and the initial pull of Coolify’s own containers. On a clean server with a decent connection, this takes roughly two to five minutes.
Once the script finishes, open a browser and navigate to your server’s IP address on port 8000. You will land on a setup screen asking you to create an admin account. After that, Coolify walks you through registering the server – in most cases it will detect that you are running locally and auto-configure the connection. From this point, the dashboard is live and you can start adding resources.
Deploying Your First Application
Coolify organizes everything around projects and environments. When you add a new resource, you pick a project, choose an environment (production, staging, or a custom label), and then select what you are deploying. The options include Git-based deployments from GitHub, GitLab, or Bitbucket, pre-built Docker images, Docker Compose files, and a library of one-click services that covers databases like PostgreSQL and MySQL, as well as common self-hosted tools.
For a Git-based deployment, you connect your repository either through a public URL or via a private GitHub App integration. Coolify reads your Dockerfile or, if you prefer, uses Nixpacks to auto-detect your build configuration from the project files. Nixpacks can handle Node.js, Python, PHP, Ruby, Go, and several other runtimes without requiring you to write a Dockerfile at all. You set your environment variables inside Coolify’s dashboard, assign a domain, and click Deploy. The platform builds the container, runs it, and configures Traefik to route traffic to it automatically.
SSL is handled without any manual configuration. As long as your domain is pointed at the server and port 80 is accessible, Coolify requests a certificate from Let’s Encrypt and renews it automatically. This alone removes one of the most tedious parts of self-hosting – the ongoing maintenance of certificate expiry. Wildcard domains are supported if you configure DNS challenge validation through a supported DNS provider.
Persistent storage is managed through Docker volumes, which you define inside Coolify’s interface. For databases, Coolify creates and manages the volumes automatically when you deploy a service from its library. For custom apps, you add volume mappings manually in the deployment settings. Backups are a separate concern – Coolify does not manage them by default, so you will need either a separate backup solution or a scheduled script that handles snapshots at the server level.
Connecting Multiple Servers and Teams
Coolify supports multi-server management from a single dashboard. After initial setup on your primary server, you can add additional servers under the Servers section using SSH key authentication. Each remote server runs a Coolify agent, and from that point you can deploy applications to any connected server from the same interface. This makes it practical for separating workloads – running databases on one machine and application containers on another, for example, without needing to manage each server through a separate interface.
Team access is available through Coolify’s built-in user management. You can invite additional users, assign them to specific projects, and control what they can deploy or modify. This is particularly useful if you are managing apps for clients or collaborating with a small development team. Coolify does not enforce role granularity beyond basic member permissions at the current stable release, so very fine-grained access control is limited – something to weigh if your team has strict separation requirements.
Webhooks tie the whole deployment workflow together. When you push a commit to a connected repository, Coolify receives the webhook and triggers an automatic rebuild and redeploy. This gives you a continuous deployment setup without needing a separate CI/CD tool. For projects that do need a full pipeline – running tests before deployment, for instance – you can combine Coolify’s webhook-triggered deploys with GitHub Actions or GitLab CI by pointing the final deploy step at Coolify’s API.
One thing that catches new users off guard is Coolify’s resource consumption on the host server. The platform itself uses around 300 to 600MB of RAM in steady state, which is worth accounting for when sizing your server. A 2GB VPS running Coolify plus two or three small apps will start feeling tight under any real load. The practical minimum for a usable multi-app setup is closer to 4GB, and 8GB gives you real breathing room without worrying about the host running short while a new deployment is building.
