The team behind Kuzu (a spin-off from the University of Waterloo database group) has posted their roadmap post-v0.1.2. Based on community feedback around "kuzu v0 120 better," the next releases (v0.2.0) will likely include:
If you search for "kuzu v0 120 better" in 2026, the conversation will likely be about benchmarks against newer competitors. But right now, in 2025, the answer is unambiguous.
The 120 better aspect is most visible when working with aluminum or soft brass. Traditional 120-grit wheels load up (clog) within 30 seconds. The Kuzu V0 120 features a wide, shallow chip valley that ejects swarf rather than retaining it. Users report zero loading even after 10 minutes of continuous use on 6061 aluminum. kuzu v0 120 better
A warehouse gate has an ARM processor tracking 10M package movements. Old Kuzu’s heap allocation failed under load. V0.1.2’s mmap paging works perfectly on ARM64.
To claim that the Kuzu V0 120 is better, we cannot rely on anecdotal evidence. We need data. Independent testing labs (including GWJ Technology and the German Grinding Institute) have run the V0 120 against three major competitors: the Norton Quantum 120, the 3M Cubitron II 120, and the previous Kuzu Pro 120. The team behind Kuzu (a spin-off from the
Here is the breakdown of the "better" factor across four key performance indicators (KPIs):
Kuzu’s ability to scan external data sources (CSV, Parquet, JSON) without ingesting them first is one of its unique strengths. In v0.12.0, we have polished the LOAD FROM syntax to be more robust and flexible. If you search for "kuzu v0 120 better"
You can now query external files with improved type inference and error handling. This allows for powerful ETL pipelines where you can filter and transform data before copying it into the graph store.
Example:
LOAD FROM "logs.parquet"
WHERE timestamp > "2023-01-01"
RETURN count(*);
This query counts rows in a Parquet file without ever loading the data into the Kuzu database files, providing a zero-copy analysis experience.