ModernRelay/omnigraph
Lakehouse native graph engine with git-style workflows observed · 2026-09-03
Health v2 · maintenance only
82/100
- Activity 100
- Release rhythm 100
- Longevity 10
Flags: young
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: 5.5
- age_days: 145
- days_rel: 2
- days_push: 0
- n_releases_24m: 19
Adoption not part of the score
1092 stars · 262 forks observed · 2026-09-03
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
Omnigraph is a lakehouse-native graph database written in Rust that stores versioned graphs on object storage using the Lance format, with Git-style branching, merging, and time travel. It serves as an operational state and coordination layer for agent fleets, combining graph traversal, vector ANN, and full-text retrieval with Reciprocal Rank Fusion in a single query runtime.
Use cases
- build a versioned knowledge graph on S3-compatible object storage
- give AI agents durable, branchable shared memory
- coordinate hundreds of agents writing to one graph without collisions
- combine graph traversal, vector search, and full-text search in one query
- manage graph schema and security policies as code
- review and merge agent data changes like pull requests
- self-host a graph database that never leaves your own storage
When to choose
- you need Git-style branching, diffing, and merging for graph data
- you run multiple agents that must mutate a shared graph safely in parallel
- you want multimodal retrieval (vector + full-text + graph) fused in one runtime
- you require data to stay on your own S3, R2, GCS, or local storage
- you want declarative cluster, schema, and policy configuration with audit trails
When to avoid
- you need a mature, battle-tested graph database like Neo4j for production-critical workloads
- you only need simple key-value or relational storage without graph semantics
- you want a fully managed cloud database with no self-hosting overhead
- you need broad ecosystem tooling and drivers beyond the provided CLI and HTTP API
Facets
service · maturity active
database vector-database search-engine rag agent-framework mcp cli http-server version-control authorization databases large-language-models self-hosted developer-tools windows rust self-hosted cli graph-database lakehouse git-style-versioning knowledge-graph lance-format object-storage cedar-policies multimodal-retrieval context-assembly branch-and-merge ai-agents retrieval-augmented-generation data-engineering linux macos docker web-server
5 sources
- readme: https://github.com/ModernRelay/omnigraph · fetched 2026-09-03 · eec1d413ddfd
- homepage: https://omnigraph.dev · fetched 2026-08-29 · 836962996a95
- site_page: https://www.omnigraph.dev/docs · fetched 2026-08-29 · 355f1fa9762c
- site_page: https://www.omnigraph.dev/docs/getting-started/install · fetched 2026-08-29 · 3e62b2bf2034
- site_page: https://www.omnigraph.dev/docs/getting-started/deployment · fetched 2026-08-29 · 0cd6fa0f6337
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| ModernRelay/omnigraph | main | 82 |
For agents
markdown · JSON · MCP: product_card(name="ModernRelay/omnigraph")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem