hydradb vs omnigraph
Object-store-native distributed graph DB in Rust: graph on SlateDB over S3, snapshot-consistent OpenCypher, GraphBLAS traversal, Neo4j Bolt 5.x compatibility, disaggregated data nodes and indexers. — versus — Lakehouse graph database for agent context — graph, vector and full-text retrieval fused in one runtime on branchable Lance/S3 storage; agent fleets write on isolated branches and merge Git-style.
Both are lakehouse/object-store graph databases aimed at agent context; omnigraph fuses graph+vector+full-text in one runtime, hydradb is a pure Cypher/GraphBLAS graph with Neo4j wire compatibility.
| hydradb | omnigraph | |
|---|---|---|
| Stars | 3.1k | 1.1k |
| Forks | 660 | 248 |
| Language | Rust | Rust |
| License | AGPL-3.0 | MIT |
| Last activity | 23 days ago | yesterday |
| Topics | knowledge-graphs, storage | memory, knowledge-graphs |
| Curated connections | 4 | 11 |
hydradb — the curator's take
Consider it when you want a Neo4j-shaped graph (Cypher, Bolt drivers) but with cloud-native durability — S3 is the only copy that matters, and compute nodes are disposable and scale independently. That makes it a fit for large agent-memory or knowledge graphs on a budget where you'd rather not run a stateful Neo4j cluster. Avoid it for embedded or single-process use (latticedb, pggraph or plain SQLite are simpler), for early-stage projects that need battle-tested drivers and tooling, and note the AGPL-3.0 licence if you embed it in a product. Still 0.x; verify with a round-tripped write, as its own README insists.
omnigraph — the curator's take
Reach for it when many agents must share one evolving knowledge store and you need blame, rollback and review on their writes — branch-per-agent with merge gates is the feature nothing else in this space has; also strong when retrieval genuinely needs graph + vector + full-text fused, not a vector store with metadata filters. NOT a drop-in vector DB: you take on a server, cluster.yaml, schemas and Cedar policy — for plain RAG recall, Chroma is answering queries before you've finished omnigraph's docs. Young project on a credible Rust/Lance foundation; expect sharp edges and a moving API.