FalkorDBLite

FalkorDBLite bundles Redis with the FalkorDB module into an embedded runtime that your application controls. It is ideal for local development, prototyping, offline demos, and CI/CD pipelines where you need a lightweight graph database without managing an external server.

Choose your SDK

What you get

  • Embedded Redis + FalkorDB server started by your app with sensible defaults
  • Full FalkorDB graph capabilities via the language SDKs
  • Data persistence when a database path is provided
  • Easy migration to remote FalkorDB by swapping the connection line in your code

When to use FalkorDBLite

  • Local feature development and unit/integration testing
  • Prototyping graph features without provisioning infrastructure
  • Demos, workshops, and CI jobs that need a disposable graph database
  • Small apps that prefer a single process runtime

For production workloads or multi-user deployments, move to FalkorDB Cloud or self-hosted FalkorDB using Docker or Kubernetes.

Frequently Asked Questions 4
What is FalkorDBLite?

FalkorDBLite is an embedded FalkorDB runtime that bundles Redis with the FalkorDB module into a single process your application controls. No external server management is needed.

When should I use FalkorDBLite vs. a full FalkorDB server?

Use FalkorDBLite for local development, prototyping, CI/CD pipelines, and demos. For production workloads, multi-user access, or high availability, use FalkorDB Cloud, Docker, or Kubernetes deployments.

Does FalkorDBLite support data persistence?

Yes. Provide a database file path when creating the instance and data persists between sessions. Without a path, data is stored in a temporary directory and may be lost.

Can I migrate from FalkorDBLite to a remote FalkorDB server?

Yes. Simply swap the connection line in your code from FalkorDB(path) (embedded) to connecting to a remote host. The graph API and Cypher queries remain identical.

Table of contents