# How to Uninstall Kaneo: Complete Removal Guide for Helm, Drim, and Docker Compose

> Uninstall Kaneo completely using Helm, Drim, or Docker Compose. Our guide provides step-by-step instructions for full removal and cleanup.

- Repository: [kaneo.app/kaneo](https://github.com/usekaneo/kaneo)
- Tags: how-to-guide
- Published: 2026-08-02

---

**TLDR:** To uninstall Kaneo, use `helm uninstall my-kaneo` for Helm deployments, `drim uninstall` for CLI-managed installations, or `docker compose down` with volume removal for Docker Compose setups—then clean up persistent storage.

Kaneo is an open-source project management platform that can be deployed on Kubernetes via Helm, managed through the `drim` CLI, or run locally with Docker Compose. Removing it cleanly requires matching your uninstall method to your original deployment approach. This guide covers all three scenarios with commands sourced directly from the [usekaneo/kaneo](https://github.com/usekaneo/kaneo) repository.

## Uninstalling a Helm-Deployed Kaneo Instance

Helm-tracked installations are the most common production deployment for Kaneo. The Helm chart (`charts/kaneo/`) bundles the API, web interface, and PostgreSQL database as a single release.

### Remove the Helm Release

Run the following command to delete all Kubernetes resources created by the chart:

```bash
helm uninstall my-kaneo

```

This command is documented in [`charts/kaneo/README.md`](https://github.com/usekaneo/kaneo/blob/main/charts/kaneo/README.md) at lines 52-56. By default, the release name is `my-kaneo`—replace this if you used a custom name during `helm install`.

### Clean Up Persistent Volume Claims (Optional)

If you enabled PostgreSQL persistence, the Helm chart creates a PVC that survives release deletion. Free this storage with:

```bash
kubectl delete pvc -l app.kubernetes.io/instance=my-kaneo

```

Skipping this step leaves orphaned storage in your cluster.

## Uninstalling a Drim-Managed Kaneo Installation

The `drim` CLI provides a unified abstraction over Helm and Docker workflows. For installations deployed through `drim`, use its native uninstall command.

### Run Drim Uninstall

```bash
drim uninstall

```

As noted in `apps/docs/core/installation/drim.mdx` at lines 64-65, this command automatically detects whether Kaneo was deployed via Helm or Docker and removes resources accordingly. It handles the equivalent of `helm uninstall` for Kubernetes deployments or container/volume cleanup for local Docker mode.

## Removing a Docker Compose Kaneo Installation

Local development setups using [`compose.yml`](https://github.com/usekaneo/kaneo/blob/main/compose.yml) require manual container and volume cleanup.

### Stop Containers and Remove the Network

```bash
docker compose down

```

This stops the API, web, and database containers and removes the Docker network they shared.

### Delete the PostgreSQL Volume

The compose file defines a named volume for database persistence. Remove it to complete uninstallation:

```bash
docker volume rm kaneo_postgres_data

```

The volume name follows the pattern `<project_name>_postgres_data`—verify with `docker volume ls` if you used a custom project name.

### Remove Environment Files (Recommended)

If you created a `.env` file from `.env.sample`, delete it to clear database credentials and API keys:

```bash
rm .env

```

## Complete Uninstall Commands by Deployment Type

| Deployment Method | Primary Command | Cleanup Step |
|-------------------|-----------------|--------------|
| **Helm** | `helm uninstall my-kaneo` | `kubectl delete pvc -l app.kubernetes.io/instance=my-kaneo` |
| **Drim CLI** | `drim uninstall` | None (handled automatically) |
| **Docker Compose** | `docker compose down` | `docker volume rm kaneo_postgres_data` |

## Summary

- **Match your uninstall method to your deployment**: Helm releases use `helm uninstall`, `drim` uses `drim uninstall`, and Docker Compose requires `docker compose down` plus volume removal.
- **Persistent storage requires explicit cleanup**: PVCs in Kubernetes and named volumes in Docker are not deleted by default—remove them manually to free space.
- **Source files**: Key documentation resides in [`charts/kaneo/README.md`](https://github.com/usekaneo/kaneo/blob/main/charts/kaneo/README.md), `apps/docs/core/installation/drim.mdx`, and [`compose.yml`](https://github.com/usekaneo/kaneo/blob/main/compose.yml) in the usekaneo/kaneo repository.

## Frequently Asked Questions

### What happens if I uninstall the Helm release without deleting the PVC?

The PostgreSQL data persists as an orphaned PVC in your cluster. You can reclaim it later with `kubectl delete pvc` or retain it for a future reinstall with existing data intact.

### Does `drim uninstall` work for both Kubernetes and Docker deployments?

Yes. According to the `drim` documentation in `apps/docs/core/installation/drim.mdx`, the command detects your deployment context and executes the appropriate cleanup sequence automatically.

### Can I reinstall Kaneo after uninstalling?

Absolutely. Reinstallation follows the standard install flow for your chosen method. If you preserved the PVC or Docker volume, your previous data remains accessible; if you deleted storage, you start fresh.

### Where is the Docker Compose volume name defined?

In [`compose.yml`](https://github.com/usekaneo/kaneo/blob/main/compose.yml), the volume is declared as `postgres_data` and Docker prefixes it with your project directory name—typically `kaneo_postgres_data`. Run `docker volume ls` to confirm the exact name on your system.