A New Chapter: Introducing Predictable Labs, Inc. and RyuGraph

The news hit the community recently: the Kuzu Github repository was archived on October 10, 2025. This marked the end of the Kuzu team's work on the project as they moved on to new pursuits.

Before going further, I want to take a moment to acknowledge Semih Salihoglu and the Kuzu team. They engineered an outstanding product that clearly filled a gap in the embedded graph database space. We at Predictable Labs appreciate the foundation they laid and sincerely wish them well.

Why We Forked: Owning Our Destiny

At Predictable Labs, Kuzu was not a side project; it was a key component of a much larger data system we are developing and plan to announce in the near future. For months, we have been working on our own fork, refining an earlier version of the code base to meet the specific requirements of our demanding use cases and workloads.

The archiving of the original repository was a clear signal to us. To ensure we can consistently deliver a robust, scalable, and reliable product to the enterprise market, we must own our destiny. This means mitigating risk by controlling the core graph component ourselves.

This is why we are formally introducing RyuGraph, our open-source fork.

• GitHub Repository: github.com/predictable-labs/ryugraph

• Documentation: ryugraph.io/docs

The Predictable Difference: Enterprise Focus and Experience

Our decision to open source RyuGraph is driven by our confidence that our enterprise use cases will serve as the perfect proving ground, ensuring the project remains hardened and innovative.

Having spent my career working with databases and data systems of every type—from academic research labs to large and small technology companies—I have seen what it takes to build a system that stands up to real-world, high-stakes workloads. This deep, practical experience is what we bring to RyuGraph, ensuring it is engineered to meet a wide variety of production demands.

Why Kuzu, and Why the Community Matters

The original appeal of Kuzu was twofold: its open license and its strong schema. This architecture made it an ideal fit for the complex work we've been doing, particularly our involvement with the LEX and Text2Graph working group at the Graph Data Council (GDC) (formerly the Linked Data Benchmark Council).

We have been part of the GDC for over two years. This membership is not a vanity metric; it is a serious commitment reflecting our belief that working collaboratively to establish standards and benchmarks is the most valuable way to contribute to the technology community at large.

The Ecosystem and The Path Forward

We recognize that this moment has sparked activity across the community, leading to the creation of other forks. We admire the speed and passion with which teams have moved to continue the Kuzu legacy. We are committed to fostering a strong ecosystem, are in early conversations, and will actively look for opportunities to collaborate for the common good. Because RyuGraph is a key part of our larger enterprise system, owning its development path is critical to mitigating risk and ensuring its long-term reliability.

We need your help. Please clone the repository, kick the tires, and let us know what you find.

Our packages and containers should be available. Please file GitHub Issues if you encounter any broken links, packages, or containers.

You can also contact us directly at contact@ryugraph.io.

Connect with me on LinkedIn.

We are excited about the journey ahead and look forward to building a valuable, sustainable product with the input and contributions of the open-source community.