Skip to content
selfhub.
Coolify logo

Self-hosting guide

Coolify

Open-source platform for deploying applications, databases, and services to servers you control, with Git builds, TLS, and a web dashboard.

How to Self-Host Coolify

Coolify is an open-source platform for deploying applications, databases, and services to servers you control, with Git builds, TLS, and a web dashboard. The notes below were checked against the project site and source repository.

When Coolify is a good fit

Choose Coolify when you want one dashboard for Git-based deploys, databases, and one-click services on machines you already administer. You still own updates, access control, backups, and recovery. Read the current installation guide before selecting a version, because host requirements change between releases.

Deployment notes

The project documents a one-command installer for a supported Linux server. Read that guide and the install script before you run it. Coolify is a control plane: it builds from Git or a container image and deploys onto servers you register, so the host that runs the dashboard needs Docker plus disk for images, build cache, and logs.

Put the dashboard behind HTTPS. Create the admin account immediately, and do not leave the setup wizard reachable from the public internet.

Data and recovery

The installer keeps application state, including encrypted server credentials, in its database and volumes. Back those up with the host. Restoring the dashboard is incomplete if the server inventory and SSH material cannot be recovered with it.

Write down the restore sequence, required secrets, exposed ports, and which machines Coolify is allowed to access. A scheduled backup is not complete until a clean host can restore it and pass a functional check.

Important limitation

Coolify can deploy and restart workloads on every server you connect. Treat the admin account and stored SSH credentials as production secrets.

Production checklist

  • Pin and record the deployed version.
  • Persist every documented data and configuration path.
  • Terminate TLS at a maintained reverse proxy or trusted tunnel.
  • Restrict administrative interfaces and rotate default credentials.
  • Monitor uptime, disk space, certificate expiry, and failed jobs.
  • Test an off-host backup with a real restore.

Official sources