Kuzu V0 136 Instant

The v0.136 release is a stabilization and feature iteration update. It addresses community feedback regarding query execution and data ingestion, ensuring that the database remains robust as datasets grow into the billions of nodes and relationships.

At the core of v0.1.3.6 are substantial under-the-hood enhancements to Kùzu’s storage engine and buffer manager. Graph databases are notorious for random memory access patterns due to pointer-chasing across large topologies. Kùzu mitigates this using a custom memory manager that uses smart caching and columnar storage. Version v0.1.3.6 refines memory allocation strategies during complex OPTIONAL MATCH and data ingestion routines, preventing memory spikes and ensuring predictable performance on resource-constrained machines. Enhanced Data Import Layouts kuzu v0 136

As of October 2025, KùzuDB reached its final milestone with the release of , at which point the project was archived and Kùzu Inc. announced they were "working on something new". Reports suggest the team may have been acquired by Apple. The v0

Kùzu v0.13.6 brings parity and stability improvements across its official language APIs, including Python, JavaScript/Node.js, Rust, C++, and Go. The Python wheels have been optimized for better interaction with PyTorch Geometric (PyG) and NetworkX, streamlining graph machine learning (GML) data pipelines. Architectural Deep Dive: Why Kùzu is Fast Graph databases are notorious for random memory access

Kuzu differs from traditional graph databases like Neo4j by focusing heavily on alongside columnar disk storage. Rather than traversing one pointer at a time, Kuzu group-loads data blocks and filters entire batches at once to bypass irrelevant data structures. Key architectural features include:

Unlike traditional databases that run as separate server processes requiring network calls, Kùzu is embedded directly into your application process. There are no servers to manage, no ports to configure, and zero network overhead. Your data lives where your code runs. 2. The Property Graph Model