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

# Production hardening checklist for FalkorDB Enterprise

> The settings to change from their defaults before a FalkorDB Enterprise installation goes into production.

The defaults are chosen so a first install works on any cluster. Several of them trade security for that. Work through this checklist before an installation holds production data. Each item names the setting and links to the page that explains it.

## Access to the Admin UI and API

> [!TIP]
>
> **Publish the Admin UI over HTTPS.** Don't install with `--quick-access` or `--no-ingress`: both serve the Admin UI over plain HTTP. Set `gateway.ingress` with a hostname and a TLS certificate. See [Production install](https://docs.falkordb.com/enterprise/deployment/production.md).

> [!TIP]
>
> **Keep secure cookies on.** Leave `adminServer.env.cookieSecure` unset, so cookies are `Secure` in production, and serve the Admin UI only over TLS.

> [!TIP]
>
> **Use a stable JWT secret from a Secret.** Generate one of at least 32 characters with `openssl rand -hex 32`, and reference it with `adminServer.secret.jwtExistingSecret` rather than a Helm value. See [Secrets](https://docs.falkordb.com/enterprise/security.md#secrets).

> [!TIP]
>
> **Replace the bootstrap admin password.** Change it at first sign-in, then delete the Secret that holds the generated password. If you set `adminServer.bootstrap.adminUser.password` yourself, keep `mustChangePassword: true`.

> [!TIP]
>
> **Protect the metrics endpoint.** `/metrics` is served without authentication by default. Set `adminServer.metrics.basicAuth.existingSecret`, or `username` and `password`. The chart's `PodMonitor` uses the same credentials.

## Identity

> [!TIP]
>
> **Sign in through your identity provider.** Configure [Google](https://docs.falkordb.com/enterprise/authentication/google-oauth.md) or [Microsoft Entra ID (Azure AD)](https://docs.falkordb.com/enterprise/authentication/azure-ad-oauth.md), and map groups to roles.

> [!TIP]
>
> **Turn off local sign-in once single sign-on works.** Set `adminServer.env.disableLocalAuth: "true"`. Keep the steps in [Reset admin password](https://docs.falkordb.com/enterprise/operations/reset-admin-password.md) for recovery.

> [!TIP]
>
> **Grant least privilege.** Give each user the narrowest role in **RBAC** in the Admin UI. Running queries from the query console needs the `clusters.query` permission; `write` lets a query change data. If you don't use the console, set `adminServer.queryConsole.enabled: false`.

## Kubernetes boundaries

> [!TIP]
>
> **Enforce the admission policy.** On Kubernetes 1.30 or later, make sure `adminServer.rbac.admissionPolicy.validationActions` is `[Deny]`, so the policy refuses violations instead of only warning. See [What the admission policy refuses](https://docs.falkordb.com/enterprise/security.md#what-the-admission-policy-refuses).

> [!TIP]
>
> **Confine databases to a namespace prefix.** Set `adminServer.managedNamespaces.pattern`, for example `"falkordb-.*"`, and list any other namespaces to protect in `adminServer.managedNamespaces.denied`. See [Database namespaces](https://docs.falkordb.com/enterprise/deployment/production.md#database-namespaces).

> [!TIP]
>
> **Turn on network policies.** Set `networkPolicy.enabled: true` on a CNI that enforces them, set `networkPolicy.ingressControllerNamespace` to where your ingress controller runs, and set `networkPolicy.ingressControllerPodSelector` to its pod labels so nothing else in that namespace can reach the Admin Server. See [Network policy](https://docs.falkordb.com/enterprise/reference/network-policy.md).

> [!TIP]
>
> **Keep Pod Security Admission labels.** The installer labels the release namespace `enforce=restricted` (`baseline` only while `dm-sql-to-falkordb` is enabled). Keep it there, and label the database namespaces at `baseline`. Don't enable the bundled CSI drivers in production, because they need `privileged`. See [Pod security](https://docs.falkordb.com/enterprise/reference/pod-security.md).

## Data

> [!TIP]
>
> **Turn on TLS for deployments.** Choose TLS in the **Encryption** step when you create each deployment. It can't be added later. See [TLS](https://docs.falkordb.com/enterprise/databases/tls.md).

> [!TIP]
>
> **Back up to object storage.** Create an S3, GCS or Azure Blob repository, mark it as the default, and test a restore. The default repository is a volume in the same cluster. See [Backups & schedules](https://docs.falkordb.com/enterprise/operations/backups.md).

> [!TIP]
>
> **Back up the Admin Server's volume.** It holds the audit log and the license state. See [Admin Server backup](https://docs.falkordb.com/enterprise/operations/admin-server-backup.md).

> [!TIP]
>
> **Keep credentials out of values files.** Supply the license with `adminServer.license.existingSecret`, the Browser key with `falkordb-browser.browser.encryption.existingSecret`, and the registry credentials with an existing pull Secret. See [Enterprise license](https://docs.falkordb.com/enterprise/deployment/production.md#enterprise-license) and [Private registries](https://docs.falkordb.com/enterprise/deployment/private-images.md).

## Supply chain and monitoring

> [!TIP]
>
> **Verify and pin images.** Verify the chart and image signatures before you install, and pin images by digest. See [Supply chain](https://docs.falkordb.com/enterprise/reference/supply-chain.md).

> [!TIP]
>
> **Turn on alerts.** Set `podMonitor.enabled` and `alertRules.enabled`, so failed backups, broken replication and full volumes reach you. See [Monitoring](https://docs.falkordb.com/enterprise/operations/monitoring.md).

For how each control works and where its limits are, read [Security](https://docs.falkordb.com/enterprise/security.md).


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