> ## 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.

# Known limitations of FalkorDB Enterprise

> Constraints of the current release that affect planning: platform, Admin Server, authentication, networking, TLS, backups and licensing.

This page collects the limitations of the current release in one place, so you can plan around them before you install. Each entry links to the page that covers it in detail.

## Platform

* **One installation per Kubernetes cluster.** Only one FalkorDB Enterprise installation is supported in a Kubernetes cluster. See [Requirements](https://docs.falkordb.com/enterprise/get-started/requirements.md).
* **The admission policy needs Kubernetes 1.30.** On Kubernetes 1.27 to 1.29 the chart installs without the Admin Server's admission policy, and only RBAC constrains the Admin Server. See [Requirements](https://docs.falkordb.com/enterprise/get-started/requirements.md#kubernetes-version).
* **KubeBlocks version.** The supported KubeBlocks version is `1.2.0-alpha.1`, the version the chart pins and the installer deploys. The FalkorDB addon needs KubeBlocks 1.2 or later. Its sharding definition accepts `spec.tls.shared` and ignores it. See [KubeBlocks upgrades](https://docs.falkordb.com/enterprise/upgrades/kubeblocks.md).
* **FalkorDB versions can't be downgraded.** Upgrading a deployment to a newer FalkorDB version is one-way. See [Upgrade FalkorDB Enterprise](https://docs.falkordb.com/enterprise/upgrades/enterprise.md#rollback).

## Admin Server

* **Single replica.** The Admin Server runs as one replica. Its audit log is a SQLite database on a `ReadWriteOnce` volume, so it can't be scaled out. An Admin Server restart or upgrade makes the Admin UI and API briefly unavailable. Your deployments keep serving traffic. To protect its state, see [Admin Server backup](https://docs.falkordb.com/enterprise/operations/admin-server-backup.md).
* **No self-service password reset.** There is no "forgot password" flow. An admin resets other users' passwords, and the admin account is recovered through its Kubernetes Secret. See [Reset admin password](https://docs.falkordb.com/enterprise/operations/reset-admin-password.md).

## Authentication

* **Two single sign-on providers.** Google and Microsoft Entra ID (Azure AD) are supported. Okta, Auth0, generic OpenID Connect, SAML and LDAP are not supported yet. See [Google OAuth](https://docs.falkordb.com/enterprise/authentication/google-oauth.md) and [Microsoft Entra ID](https://docs.falkordb.com/enterprise/authentication/azure-ad-oauth.md).

## Networking

* **Sentinels aren't published through node addresses.** With `externalAddress` set to `NodeExternalIP` or `HostIP`, only data pods are published. Expose Sentinels with a `LoadBalancer` service instead. See [ExternalDNS](https://docs.falkordb.com/enterprise/deployment/external-dns.md).
* **One data pod per node with node addresses.** Node addresses use fixed host ports, which also need the deployment's namespace to run at the `privileged` Pod Security level. See [ExternalDNS](https://docs.falkordb.com/enterprise/deployment/external-dns.md).
* **GKE direct pod access needs VPC-native clusters.** Routes-based GKE clusters are not supported for direct pod access. See [VPC access](https://docs.falkordb.com/enterprise/deployment/vpc-access.md).

## TLS

* **TLS is set at creation.** You can't turn TLS on or off for an existing deployment. See [TLS](https://docs.falkordb.com/enterprise/databases/tls.md).
* **KubeBlocks-issued certificates are limited.** The **Issued by KubeBlocks** option works only for standalone deployments and replication without Sentinel, and can't be used with an external domain. Use the default FalkorDB Enterprise issuer, cert-manager or your own Secret for the other topologies. See [TLS](https://docs.falkordb.com/enterprise/databases/tls.md#choose-who-issues-the-certificates).
* **Sharded deployments without persistent volumes aren't restarted for a new certificate.** If reloading a certificate in place fails, restart the deployment yourself. See [TLS](https://docs.falkordb.com/enterprise/databases/tls.md#renewal).

## Backups and restore

* **No restore into an existing deployment.** Every restore, including a point-in-time restore, creates a new deployment. See [Restore in place](https://docs.falkordb.com/enterprise/operations/restore-same-database.md).
* **Backups restore only in the Kubernetes cluster that took them.** The Admin UI and API can't restore a lost cluster's backups into a replacement cluster. FalkorDB support can help. To plan for that case yourself, see [Disaster recovery](https://docs.falkordb.com/enterprise/operations/disaster-recovery.md).
* **Point-in-time restore.** Continuous backups don't package offloaded graphs, and writes within the replication lag before the restore time can be left out. See [Point-in-time restore](https://docs.falkordb.com/enterprise/operations/restore-point-in-time.md#limitations).
* **RDB exports.** Exports of a sharded deployment aren't a consistent copy across shards. Repositories that rely on cloud IAM roles instead of keys aren't supported for RDB exports, and importing a graph over an existing graph of the same name is not supported. See [RDB export and import](https://docs.falkordb.com/enterprise/operations/rdb-export-import.md) and [Disaster recovery](https://docs.falkordb.com/enterprise/operations/disaster-recovery.md#limitations).

## Licensing

* **A license is bound to one Kubernetes cluster.** Rebuilding a cluster creates a new cluster ID, which needs a new license. See [Licensing](https://docs.falkordb.com/enterprise/licensing.md#binding-to-a-cluster).


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