Skip to main content
FalkorDB Enterprise is a self-managed distribution of FalkorDB for Kubernetes. It bundles the database, a Kubernetes control plane, and an administration surface into a single Helm release that you run inside your own cluster and network boundary.

What you get

Admin UI

A web console for creating deployments, running day-2 operations, managing backups, viewing metrics and logs, and administering users and roles.

Admin Server

The REST API behind the UI. It handles deployments, operations, backup and restore, logs, metrics, users, RBAC, settings, audit logs, licensing, and diagnostics.

FalkorDB KubeBlocks addon

The operator definitions that let KubeBlocks provision and reconcile FalkorDB topologies on Kubernetes.

FalkorDB Browser

A visual query and graph exploration tool, deployed alongside the platform.

Admin CLI

A command-line client for scripting Admin Server login, deployment operations, and license management.

Installer scripts

install.sh and uninstall.sh handle platform dependencies, CRDs, permission preflight checks, and quick-access networking.

Architecture at a glance

Operators interact only with the Admin UI or Admin CLI. The Admin Server translates those actions into KubeBlocks custom resources, and the KubeBlocks operator reconciles them into FalkorDB pods, services, and persistent volumes. Applications connect to the resulting database services directly.

Supported topologies

In the Admin UI and in these docs, a FalkorDB database instance is called a deployment. The word cluster is reserved for the Kubernetes cluster itself.

Namespaces and releases

The installer uses these defaults:
Only one FalkorDB Enterprise installation is supported per Kubernetes cluster. The chart creates a cluster-scoped install lock named falkordb-enterprise-install-lock and blocks installs from any other release or namespace in the same cluster.

Licensing

The Admin Server activates a signed Enterprise license supplied through Helm values or a Kubernetes Secret. Leaving those fields empty is fine — the admin server starts a 14-day free trial automatically, and you can activate or replace the license at any time from the Admin UI’s License page, without touching Helm values. If the license expires, is invalid, or a resource limit is exceeded, authenticated write operations are locked and the Admin UI becomes read-only until a valid license is active. See Helm values for license configuration.

Next steps

Check requirements

Cluster size, tooling, and network access.

Install

Run the quickstart in a scratch cluster.