kuzu
kuzu copied to clipboard
kuzudb
Feature: Support Bolt
API
Other
Description
Kuzu is a fantastic addition to the embedded ecosystem, the only thing it is missing is a bolt adapter to allow it to work with the various tools in the Graph ecosystem!
Any chance we can get this added?
Hi @voycey,
This is something we discussed several times and we need a bit more time to strategize about this internally. At a high-level this has always made sense to us to integrate Kuzu better into the graph technology ecosystem but we are not sure about when is a good time to focus on this and the engineering implementations given that we're also developing a server-client version of Kuzu, which we don't plan to base on Bolt. More importantly, currently the team is quite busy on developing our enterprise version and trying to get that out and that work will keep us busy in the next quarter or so at least.
I'll follow up when I have more updates on this.
Semih
For me the ability to have an embedded graphdb that I can hook up to existing tools far outweighs the benefits of a client server model, the reason I chose Kuzu is because of this, another client server setup puts you into a very crowded, more mature ecosystem and if you further hide features behind enterprise pricing then you aren't doing anything different in this space than anyone else.
I would even go so far as to say I'd pay for these kind of features specifically at a consumer level but if they end up being put behind an enterprise licence then you are going to cut out the very people who build on this.
The DuckDB model is excellent for this but they also have the benefit of excellent plugins because of the architecture they created around it, I can connect with MySQL drivers or use it as an embedded DB depending on the use case, KuzuDB has an opportunity to corner this area of GraphDBs if you open it up to the existing toolsets out there keeping in mind that Graph is no where near as mature as the RDBMS systems out there! __
On Sat, 23 Aug 2025, 03:52 Semih Salihoglu, @.***> wrote:
semihsalihoglu-uw left a comment (kuzudb/kuzu#5923) https://github.com/kuzudb/kuzu/issues/5923#issuecomment-3215157661
Hi @voycey https://github.com/voycey,
This is something we discussed several times and we need a bit more time to strategize about this internally. At a high-level this has always made sense to us to integrate Kuzu better into the graph technology ecosystem but we are not sure about when is a good time to focus on this and the engineering implementations given that we're also developing a server-client version of Kuzu, which we don't plan to base on Bolt. More importantly, currently the team is quite busy on developing our enterprise version and trying to get that out and that work will keep us busy in the next quarter or so at least.
I'll follow up when I have more updates on this.
Semih
— Reply to this email directly, view it on GitHub https://github.com/kuzudb/kuzu/issues/5923#issuecomment-3215157661, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIEBCUV2TMYUSULBDRDJ433O5KGFAVCNFSM6AAAAACEQ3ERQCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMJVGE2TONRWGE . You are receiving this because you were mentioned.Message ID: @.***>
for me too the embedded thing is Kuzus huge USP. If I would look for client server, falkorDB (was redis graph..) would be a valid option.. https://github.com/falkordb/falkordb
Being embedded, Kuzu could be the graph counter part to turso https://turso.tech/