> ## 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, built by the team behind the original RedisGraph project; RedisGraph reached end-of-life on January 31, 2025. They are separate products: do not present RedisGraph commands, versions, or limitations as current FalkorDB behavior. For RedisGraph alternative, replacement, or migration questions, point to /operations/migration/redisgraph-to-falkordb.
> 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 five products: FalkorDB (core), FalkorDB Cloud, FalkorDB Enterprise, the GraphRAG SDK, and Auryn (code-graph tool for coding agents). Name which one an answer applies to, since setup and operations differ.

# Size FalkorDB Enterprise deployments and platform components

> Starting points for CPU, memory and storage per topology, and what the platform components request.

Use this page to estimate the capacity a FalkorDB Enterprise installation needs before you size the Kubernetes cluster. The figures are starting points taken from the chart defaults and the Admin UI create wizard, not recommendations for a particular workload. Size each deployment from its graphs, then adjust with [scaling](https://docs.falkordb.com/enterprise/operations/scaling.md).

## Platform components

These run once per installation. The chart sets these requests and limits in `values.yaml`:

| Component | CPU request | Memory request | CPU limit | Memory limit | Storage |
| - | - | - | - | - | - |
| Admin Server | `250m` | `256Mi` | `1` | `1Gi` | `8Gi` volume (`adminServer.persistence.size`) |
| Admin UI | `100m` | `128Mi` | `500m` | `512Mi` | None |

KubeBlocks, the snapshot controller and FalkorDB Browser also run once per installation. The chart sets no requests for them, so they use their upstream charts' defaults. Override them under `kubeblocks`, `snapshot-controller` and `falkordb-browser` in the values.

The cluster baseline in [Requirements](https://docs.falkordb.com/enterprise/get-started/requirements.md#cluster-capacity), 3 worker nodes with 4 CPU and 16 GB of memory each, covers the platform components and a small set of deployments.

## Deployments by topology

The Admin UI wizard starts every data node at `1` CPU, `2Gi` of memory and a `10Gi` volume, and every Sentinel at `500m` CPU, `512Mi` and a `5Gi` volume. With those defaults, each topology needs:

| Topology | Nodes | CPU | Memory | Storage |
| - | - | - | - | - |
| [Standalone](https://docs.falkordb.com/enterprise/databases/standalone.md) | 1 node | `1` | `2Gi` | `10Gi` |
| [Replication](https://docs.falkordb.com/enterprise/databases/replicated.md) | 1 primary + 1 replica | `2` | `4Gi` | `20Gi` |
| [Replication with Sentinel](https://docs.falkordb.com/enterprise/databases/sentinel.md) | 1 primary + 1 replica, 3 Sentinels | `3.5` | `5.5Gi` | `35Gi` |
| [Sharded](https://docs.falkordb.com/enterprise/databases/sharded.md) | 3 shards of 1 primary + 1 replica | `6` | `12Gi` | `60Gi` |

The wizard's minimum for a sharded deployment is 3 shards of 2 nodes each. Each database pod also runs the `kbagent` and `metrics` sidecars, which add a small amount on top of the node's own resources.

> [!NOTE]
>
> The license counts the CPU and memory requests of every node, including Sentinels and every shard's replicas, falling back to limits when no request is set. Use the totals above when you check a deployment against your license. See [Licensing](https://docs.falkordb.com/enterprise/licensing.md#what-a-license-limits).

## Choosing memory

FalkorDB keeps graphs in memory, so memory is the figure that matters most.

* **Start from the data.** Give each data node enough memory for the graphs it holds, with headroom for queries, replication buffers and background saves. On a sharded deployment, a graph is one key and lives on one shard, so the largest graph must fit on one node.
* **Replicas need the same memory as the primary.** Every replica holds a full copy of its primary's data.
* **Size storage from memory.** The data volume holds the persistence files, so make it larger than the memory limit. Volumes can grow later; see [Parameters & resources](https://docs.falkordb.com/enterprise/operations/parameters.md).
* **Let memory grow automatically.** Automatic memory scaling raises a deployment's memory as it fills, up to a ceiling you set. See [Scale memory automatically](https://docs.falkordb.com/enterprise/operations/scaling.md#scale-memory-automatically).

## Choosing CPU

Start at the wizard's `1` CPU per data node. Add CPU when the pods' CPU stays busy or query latency rises as more queries run at the same time. [Monitoring](https://docs.falkordb.com/enterprise/operations/monitoring.md) shows both.

## Spread nodes across failure domains

For replication and sharded deployments, plan for a primary and its replicas to run on different nodes, and ideally in different zones, so one node failure doesn't take down a shard. Set node affinity and tolerations in the create wizard when you need to control placement. Plan worker capacity so a node can drain without leaving pods unscheduled. On multi-zone clusters, also plan where backups are stored; see [Multi-zone clusters](https://docs.falkordb.com/enterprise/operations/backups.md#multi-zone-clusters).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.