Uninstall Coolify

The uninstall steps depend on how you use Coolify.

For a self-hosted instance, the steps remove Coolify's containers and its data.

For Coolify Cloud, they remove Coolify Proxy and Sentinel from your servers.

Deployed applications and services may keep running after removal. Removing Coolify Proxy stops the domains and TLS routing it provides.

Remove the self-hosted instance

Before you uninstall

Create an instance backup and keep a copy outside this server.
Save /data/coolify/source/.env separately. It contains the encryption key needed to restore the instance backup.
Save or migrate the application configuration, deployment files, local backups, and proxy routing you need after removal. These are stored in /data/coolify.
Plan a replacement proxy before continuing if your resources use Coolify-managed domains or TLS certificates.
Confirm that there are no active deployments and that you are connected to the Coolify server over SSH.

This cannot be undone

Deleting /data/coolify permanently removes Coolify's configuration, SSH keys, deployment files, proxy configuration, and locally stored instance backups.

An instance backup contains the Coolify database; it does not back up the applications, databases, services, or volumes you deploy with Coolify.

Connect to the Coolify server

Connect to the server that runs the Coolify instance over SSH:

ssh root@<server-ip>

Replace <server-ip> with your server's IP address. If you normally sign in with a non-root account, run sudo -i first to open a root shell.

Remove Coolify containers

docker rm -f coolify coolify-db coolify-redis coolify-realtime coolify-sentinel

Application, database, and service containers keep running.

Remove Coolify Proxy according to the Docker mode used by the server. For standalone Docker, run:

docker rm -f coolify-proxy

For Docker Swarm, run this command on a manager node instead:

docker stack rm coolify-proxy

Removing Coolify Proxy stops the domains and TLS routing it provides.

Remove Coolify data volumes

Remove the volumes that store the Coolify database and Redis data:

docker volume rm coolify-db coolify-redis

Do not run a broad docker volume prune command as part of this process. It can remove unused volumes that belong to other workloads on the server.

If application or service containers still use the coolify network, connect them to another network before removing it. If you want them to keep using the coolify network, leave the network in place and skip the command below.

When no workloads need the network, remove it:

docker network rm coolify

Delete Coolify files

After confirming that your backup and any application or service files you still need are stored elsewhere, delete the Coolify data directory:

rm -rf /data/coolify

This is the final destructive step. It permanently removes the instance .env file, local instance backups, and deployment and configuration files Coolify stored under /data/coolify.

Remove Docker images

Image versions may differ

Image tags can vary depending on when you last updated Coolify. Run docker images to see the images and tags on your server, then use those tags in the commands below.

Remove the default Coolify images to free disk space:

docker rmi ghcr.io/coollabsio/coolify:latest
docker rmi ghcr.io/coollabsio/coolify-helper:latest
docker rmi ghcr.io/coollabsio/coolify-realtime:1.0.16
docker rmi ghcr.io/coollabsio/sentinel:1.0.1
docker rmi postgres:15-alpine
docker rmi redis:7-alpine

If you used the default Traefik proxy, remove its image too:

docker rmi traefik:v3.7

If you used Caddy instead:

docker rmi lucaslorentz/caddy-docker-proxy

Verify the removal

Confirm that no Coolify control-plane containers remain:

docker ps -a --format '{{.Names}}' | grep -E '^(coolify|coolify-db|coolify-redis|coolify-realtime|coolify-sentinel|coolify-proxy)(_|$)' || true

The command should return no container names.

Then confirm that Docker reports the coolify-db and coolify-redis volumes as missing and that /data/coolify no longer exists:

docker volume inspect coolify-db coolify-redis
test ! -d /data/coolify && echo "Coolify data directory removed"

docker volume inspect should report that the two volumes do not exist.

If applications or services remain on the server, manage or migrate them directly with Docker and replace Coolify Proxy routing before exposing them publicly again.