> ## Documentation Index
> Fetch the complete documentation index at: https://docs.falkordb.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> FalkorDB is a graph database that speaks the Redis protocol. Queries are issued as OpenCypher through the GRAPH.QUERY and GRAPH.RO_QUERY commands, not over Bolt or a SQL connection.
> FalkorDB implements a subset of OpenCypher with proprietary extensions. Do not assume Neo4j-only syntax or procedures are available — check /cypher/cypher-support and /cypher/known-limitations before using a clause.
> FalkorDB is the successor to RedisGraph, but they are separate products. Do not present RedisGraph commands, versions, or limitations as current FalkorDB behavior.
> Use the official clients listed in /getting-started/clients rather than generic Redis or Neo4j drivers, and prefer the language the user is already working in.
> Configuration parameters are set with GRAPH.CONFIG SET or at startup; cite the exact parameter name from /getting-started/configuration rather than inventing one.
> This site covers four products: FalkorDB (core), FalkorDB Cloud, FalkorDB Enterprise, and the GraphRAG SDK. Name which one an answer applies to, since setup and operations differ.

# Uninstall

> Remove FalkorDB Enterprise and, optionally, the platform components it installed.

## Preview the plan

The uninstall script is published alongside the installer, so it can be run without a repository checkout. It supports dry-run mode:

```bash theme={null}
curl -fsSL https://falkordb.github.io/FalkorDB-Enterprise/uninstall.sh | \
  bash -s -- --dry-run
```

For a specific context and namespace:

```bash theme={null}
curl -fsSL https://falkordb.github.io/FalkorDB-Enterprise/uninstall.sh | \
  bash -s -- \
    --kube-context production-cluster \
    --namespace falkordb-system \
    --dry-run
```

## Uninstall Enterprise only

This removes the FalkorDB Enterprise Helm release and retained FalkorDB addon resources. KubeBlocks is kept.

```bash theme={null}
curl -fsSL https://falkordb.github.io/FalkorDB-Enterprise/uninstall.sh | \
  bash -s -- \
    --namespace falkordb-system
```

For automation:

```bash theme={null}
curl -fsSL https://falkordb.github.io/FalkorDB-Enterprise/uninstall.sh | \
  bash -s -- \
    --namespace falkordb-system \
    --yes
```

## Also uninstall KubeBlocks

```bash theme={null}
curl -fsSL https://falkordb.github.io/FalkorDB-Enterprise/uninstall.sh | \
  bash -s -- \
    --namespace falkordb-system \
    --kubeblocks-namespace kb-system \
    --uninstall-kubeblocks
```

## Delete namespaces

```bash theme={null}
curl -fsSL https://falkordb.github.io/FalkorDB-Enterprise/uninstall.sh | \
  bash -s -- \
    --namespace falkordb-system \
    --kubeblocks-namespace kb-system \
    --uninstall-kubeblocks \
    --delete-namespaces
```

If `--uninstall-kubeblocks` is not provided, `--delete-namespaces` deletes only the Enterprise namespace.

## Delete CRDs

Deleting CRDs removes KubeBlocks and VolumeSnapshot API definitions from the cluster. This can affect other workloads that use those APIs.

```bash theme={null}
curl -fsSL https://falkordb.github.io/FalkorDB-Enterprise/uninstall.sh | \
  bash -s -- \
    --uninstall-kubeblocks \
    --delete-crds \
    --yes
```

## Verify removal

```bash theme={null}
helm status falkordb-enterprise -n falkordb-system
kubectl get all -n falkordb-system
```

If KubeBlocks was removed:

```bash theme={null}
helm status kubeblocks -n kb-system
kubectl get pods -n kb-system
```

If namespaces were deleted:

```bash theme={null}
kubectl get namespace falkordb-system kb-system
```