Coolify

A Heroku-shaped dashboard over ordinary Docker containers.

1guide Feed

Coolify is an open-source deployment platform you install on your own server. It connects to a git repository, builds an image, runs it as a Docker container and puts a reverse proxy in front. Databases, one-click services and scheduled backups are part of the package.

Its defining choice is the absence of an orchestrator. Applications are plain Docker containers, so the mental model you already have is the correct one, and during an incident you can keep a service alive by hand while you fix the dashboard.

Reach for Coolify when you are standing up many self-hosted services and want a large template catalogue to do it from, or when you value being able to drop to plain docker commands under pressure. Reach for a Swarm-based platform instead when zero-downtime deploys are a requirement rather than a preference.

The default deployment stops the old container before starting the new one, so there is a short window — usually seconds — where requests fail. For an internal tool that is irrelevant. For a public API it is not, and it is the first thing to configure around.

The other thing to verify yourself is backups. Scheduled database backups to object storage are built in, and a misconfigured endpoint fails quietly often enough to matter. Trigger one by hand, confirm the object actually exists in the bucket, and restore it into a scratch database. Do that before you need it.

Coverage here is comparative rather than exhaustive: what Coolify does differently, and which of those differences should decide your choice.

Start here

Dokploy vs Coolify: Choosing a Self-Hosting Platform

Both put a Heroku-style deploy UI on your own VPS, but on different container primitives. What that means for zero-downtime deploys, multi-server growth and the day the control plane breaks.

Intermediate · 6 min read

Beginner to advanced

A reading order that builds Coolify knowledge in the sequence it is actually needed.

  1. Build Dokploy vs Coolify: Choosing a Self-Hosting Platform 6 min

Common problems

Failure modes that come up repeatedly with Coolify, and where each one is solved.

A deploy briefly returns errors
The default deployment stops the old container before starting the new one. Expect a short gap unless you configure around it.
Scheduled backups appear to run but nothing lands in the bucket
Object storage misconfiguration fails quietly. Trigger a backup manually, confirm the object exists, then restore it into a scratch database.
The install script fails on a 1 GB instance
2 GB RAM is the practical floor and 4 GB is comfortable once a database and a container build are involved.

Latest Coolify guides

Browse the archive
  • intermediate

    Dokploy vs Coolify: Choosing a Self-Hosting Platform

    Both put a Heroku-style deploy UI on your own VPS, but on different container primitives. What that means for zero-downtime deploys, multi-server growth and the day the control plane breaks.

    6 min AI-assisted

Recently updated

  • intermediate

    Dokploy vs Coolify: Choosing a Self-Hosting Platform

    Both put a Heroku-style deploy UI on your own VPS, but on different container primitives. What that means for zero-downtime deploys, multi-server growth and the day the control plane breaks.

    6 min AI-assisted

Frequently asked questions

What runs my application under Coolify?

Ordinary Docker containers. `docker ps`, `docker logs` and `docker inspect` all behave exactly as you expect, which makes incident debugging simpler than on a platform that adds an orchestration layer.

How does Coolify handle several servers?

As independent hosts managed from one dashboard, rather than as a cluster. You place applications on specific servers yourself. There is no quorum to lose, and no scheduler to move workloads for you.

Is the template catalogue worth choosing Coolify for?

If your plan involves standing up a dozen open-source services, yes — it is a genuine time saving. If you are deploying one application from a Dockerfile, it makes no difference.

Sources

  1. Coolify documentation Coolify Primary source
  2. Coolify source repository coollabs Primary source