> ## 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, but they are separate products. Do not present RedisGraph commands, versions, or limitations as current FalkorDB behavior.
> 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 four products: FalkorDB (core), FalkorDB Cloud, FalkorDB Enterprise, and the GraphRAG SDK. Name which one an answer applies to, since setup and operations differ.

# FalkorDBLite

> Embedded FalkorDB runtime with Python and TypeScript bindings for embedded graph, local development, testing, and CI/CD pipelines without managing external servers.

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

* [FalkorDBLite for Python](/operations/falkordblite/falkordblite-py) — `pip install falkordblite`
* [FalkorDBLite for TypeScript](/operations/falkordblite/falkordblite-ts) — `npm install falkordblite`

## 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](https://app.falkordb.cloud) or self-hosted FalkorDB using [Docker](/operations/docker) or [Kubernetes](/operations/k8s-support).

## Frequently Asked Questions

<AccordionGroup>
  <Accordion title="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.
  </Accordion>

  <Accordion title="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.
  </Accordion>

  <Accordion title="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.
  </Accordion>

  <Accordion title="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.
  </Accordion>
</AccordionGroup>