Self-hosting with Coolify: a PaaS on your own server

Setting up Docker Compose for every service gets repetitive. Write the YAML, configure the reverse proxy, set up SSL, manage environment variables, handle updates. It works, but it is not fun after the tenth time.

Coolify is an open-source platform that gives you a Heroku-like experience on your own server. You install it once, and then you deploy apps through a web interface instead of SSH sessions and config files.

What it does

Coolify connects to your server (or multiple servers), and lets you deploy applications from Git repos, Docker images, or their one-click service catalog. It handles:

• Building and deploying your apps
• Reverse proxy with automatic SSL (using Caddy or Traefik under the hood)
• Database provisioning (PostgreSQL, MySQL, Redis, MongoDB)
• Environment variable management
• Deployment rollbacks
• Webhook-based auto deploys from GitHub/GitLab

The web UI is clean and covers everything you need without dropping to the terminal.

Installation

Coolify installs with a single command on any VPS running Ubuntu or Debian:

curl -fsSL https://cdn.coollabs.io/coolify/install.sh | bash

After installation, access the dashboard at http://your-server-ip:8000, create an admin account, and you are ready to deploy.

Deploying an app

Click "New Resource," pick "Application," connect your GitHub repo, and configure the build settings. For a Next.js app, Coolify detects the framework and sets the build command automatically. Set your environment variables, click deploy, and your app is live with HTTPS.

The experience is similar to Vercel or Railway, but everything runs on your server. You control the hardware, the data, and the cost.

The one-click catalog

Coolify has a catalog of 280+ services that you can deploy with a single click. Need a Plausible analytics instance? Click, configure the domain, done. Want a Gitea server? Same thing.

This is where Coolify really shines for home labs and small teams. Services that would normally take 30 minutes to set up with Docker Compose take 2 minutes through the catalog.

When to use Coolify vs raw Docker

If you are deploying more than 3 or 4 services, Coolify saves time. The automatic SSL, deployment UI, and service catalog reduce the operational overhead significantly.

If you have one or two simple containers, Docker Compose is fine and adds less abstraction. Coolify is another layer on top of Docker, and layers have costs in terms of debugging and understanding what is happening.

What I use it for

I run Coolify on a VPS for services that I do not want to manage manually. Small web apps, staging environments, and utility services. For my main projects (Landbound, Routemade), I use more hands-on deployment setups because I need the control. But for everything else, Coolify has replaced my Docker Compose workflow.

Sources

• Coolify