Kuzu V0: 136 [top]

If you’re evaluating Kuzu, follow these signs as indicators of maturity:

: It treats nodes and relationships as tables, allowing for columnar storage optimizations usually reserved for relational systems. Cypher Support

Databases are now stored as a single file on disk, making them incredibly portable.

This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later. kuzu v0 136

Data is organized into strictly typed node and relationship tables, ensuring data integrity and optimizing storage layout.

Native support for vector indices (HNSW) and Full-Text Search (FTS) , making it a strong choice for AI-driven applications like GraphRAG.

+-------------------------------------------------------------+ | User Application | | (Python / Rust / Node.js / C++ / Go Bindings) | +-------------------------------------------------------------+ | (In-Process API Calls) v +-------------------------------------------------------------+ | Kùzu DB Engine | | | | +------------------+ +--------------------+ | | | Cypher Parser | ------------> | Query Optimizer | | | +------------------+ +--------------------+ | | | | | v | | +------------------+ +--------------------+ | | | Vectorized Exec | <------------ | Factorized Planner | | | +------------------+ +--------------------+ | | | | +------------|------------------------------------------------+ | (Direct Memory Access) v +-------------------------------------------------------------+ | Storage Layer | | - Column-Oriented Tables - Dual-Indexed Adjacency Lists | | - In-Memory Buffer Pool - Spill-to-Disk Swapping | +-------------------------------------------------------------+ Factorized Execution If you’re evaluating Kuzu, follow these signs as

The buffer manager—responsible for moving data between disk and RAM—has been rewritten. introduces a multi-version concurrency control (MVCC) layer that allows readers and writers to operate without locks. The result: concurrent query throughput has improved by 25-30% on multi-core machines.

Enter , an open-source, in-process property graph database management system built for query speed and scalability. Modeled as a graph equivalent to DuckDB, Kùzu operates directly within your application process, eliminating the overhead of client-server architectures.

No more manual installation for algo , fts , json , and vector extensions. This link or copies made by others cannot be deleted

Kuzu v0.136 represents a significant milestone in the development of the Kuzu GDBMS. With improved query performance, enhanced Cypher support, and new features like node labels and edge properties, this release provides users with a more powerful and flexible graph database management system. The Kuzu team is committed to continuing to develop and improve Kuzu, and we look forward to providing future releases with even more features and capabilities.

Since its initial release, Kuzu has accumulated over 2,500 GitHub stars. Version 0.136 has already been downloaded over 15,000 times in its first two weeks.

If you are currently on a previous version (e.g., v0.120 or v0.130), note the following breaking changes:

Are you integrating with other data tools like ?