Kuzu
Fewer than 5 people recommend it so far, so there's no written verdict. Here is what commenters said.
4recommend
3warn against
Mar 21, 2026first mention
Oct 5, 2026latest mention
Why people recommend it
“Most recently my hope was for kuzudb, but they got acquihired”
“https://vldb.org/cidrdb/2023/kuzu-graph-database-management-system.html”
Show 1 more
“it's been left in a fairly stable rate which is fantastic”
Caveats and dissent
“to avoid leaving users left in panic when KuzuDB (which Ladybug forked) was acquired by Apple and killed”
Often compared with
Threads where it came up
- Grafeo – A fast, lean, embeddable graph database built in Rust 5 mentions
- Show HN: Minigraf – An embedded, bi-temporal graph database in Rust 2 mentions
- Show HN: LatticeDB – Like SQLite but for graph databases 1 mention
- I Analyzed 163K Lines of Kuzu's Codebase. Here's Why Apple Wanted It 1 mention
- Algorithms on billion-scale graph using 10GB RAM: I love DataFusion 1 mention
- YouTrackDB is a general-use object-oriented graph database 1 mention
Also written as KuzuDB. Data: kuzu.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 13
Here's a comparison matrix, although it doesn't include ladybug yet: https://github.com/project-minigraf/minigraf/wiki/Comparison
“Most recently my hope was for kuzudb, but they got acquihired”
this one? https://pygraphistry.readthedocs.io/en/latest/gfql/index.html
There’s a fork https://github.com/LadybugDB/ladybug that you can use.
“benchmarks vs neo4j, memgraph, kuzu, etc”
“https://vldb.org/cidrdb/2023/kuzu-graph-database-management-system.html”
“to avoid leaving users left in panic when KuzuDB (which Ladybug forked) was acquired by Apple and killed”
This is very cool to hear. Please get in touch with me, I would love to learn more. By the way, I am recruiting participants for an upcoming seminar in which I am soliciting industrial participation: https://kmicinski.com/minnowbrook-26. Please get in contact with me if this is relevant to anyone at your company.
LadybugDB (https://github.com/LadybugDB/ladybug) at this point seems to be the only sustainable fork. When deciding what to do about the Kuzu archival on https://gdotv.com, we've gone with maintaining support for the last available version of Kuzu (it's still heavily used from what I'm seeing) whilst introducing support for LadybugDB. I've looked into a few other forks and at this point in time none seem to be active
“it's been left in a fairly stable rate which is fantastic”
“Quite annoyed about that one, was using it extensively.”
“This is essentially what Kuzu implemented and DuckDB tried to implement (DuckPGQ)”
“LadybugDB is backed by this tech (I didn't write it)”