## In their words

> “I mostly use Omnigraph to build a company brain. It fit so well that I ended up contributing Azure Blob Storage support myself.”

Roey Zalta Data & AI Solutions Engineer

> “Omnigraph is the right model for an agent-driven company brain. Agents work on branches across staging and production graphs, and nothing reaches main without review. It’s open source, so when I needed something, I sent a PR instead of waiting.”

Joan Reyero VP of AI & Data

## Omnigraph is a foundation for

### Company brain

Org knowledge in one graph.

### Agent memory

Versioned memory per agent or task.

### Context graph

Decisions and tribal knowledge.

### Research graphs

Hypotheses and results, reviewed.

[→Start from a template↗](https://github.com/ModernRelay/omnigraph-cookbooks)

## Key capabilities

- Typed schema  
- Branches  
- Hybrid search  
- Declarative config  
- Object storage

### Typed schema

All your agents share one model of the domain they work in, and every write is checked against it.

#### What to notice

A decision can't be saved unless it links to the meeting it was made in.

```graphql
node Person {
  handle: String @key
  role: enum(engineer, pm, agent)
}

node Team {
  name: String @key
}

node Meeting {
  slug: String @key
  title: String
  held_on: Date
}

node Decision @instruction("Link every decision to the meeting it was made in.") {
  slug: String @key
  title: String
  body: String @index
  embedding: Vector(1536)? @embed("body") @index
}

edge MemberOf: Person -> Team @card(1..1)
edge Attended: Person -> Meeting
edge DecidedIn: Decision -> Meeting @card(1..)
```

## The Knowledge IDE

A blazing fast, GPU-rendered desktop app to visualize your ontology and graph, inspect knowledge, and review changes before they merge.

1. **Spot changes**  
   Open an agent's branch and see what it added, changed and removed, in place.
2. **Inspect a record**  
   See any entity as a page: its properties and everything linked to it.
3. **Explore links**  
   Follow relationships out on a canvas or down a tree.
4. **Query safely**  
   Write queries against the schema. A typo shows up before anything runs.
5. **Approve a merge**  
   Go through a branch change by change, then merge it into main.

[→Download Studio for macOS, Linux and Windows](https://www.omnigraph.dev/studio)

## Git-style workflows

Agents safely collaborate and write to the same graph, each on its own branch, merging into main only through review.

### Branch

Claude Code and Hermes each fork main into their own branch.

cheap fork  
`$ omnigraph branch create`

### Write

Hermes adds new nodes and edges while Claude Code dedupes existing records. Isolated branches never collide.

schema + policy enforced  
`$ omnigraph mutate`

### Review

Each branch's diff is approved by a human or another agent before it lands.

human or agent  
`$ omnigraph diff`

### Merge

Both land on main in review order, three-way and attributed to their agent.

three-way · audited  
`$ omnigraph branch merge`

No agent touches main directly. The schema rejects malformed writes at the branch, the policy decides who can merge, and the commit graph records every change and its author. Two agents, one graph, no collisions.

[→Full CLI reference↗](https://github.com/ModernRelay/omnigraph#common-commands)

## Deploy anywhere

**Embedded** 
A folder on your machine. No server, no infra.  
**BYOC** 
AWS, Azure or GCP, in your own cloud account.

### On-prem

Your own servers and any S3-compatible store.

### Omnigraph Cloud

Run by us: a dedicated cluster with SSO, policy and audit.

[Private preview→](https://www.omnigraph.dev/cloud#join)

[→Read the deployment guide](https://www.omnigraph.dev/docs/getting-started/deployment)

## Templates

Cookbooks are runnable Omnigraph projects: schema, queries, seed data, and agent skills in one repo. Clone one, apply it, and inspect a real graph before you design your own.

1. **Industry intel↗**  
   Track AI and ML market signals through the SPIKE frame: signals, patterns, insights, and know-how.
2. **Pharma intel↗**  
   Monitor trials, filings, competitors, and market movement in a graph built for competitive intelligence.
3. **Company brain↗**  
   Claims, decisions, and action items with the exact source text they rest on, shared by a company's people and agents.
4. **VC OS↗**  
   Connect deal flow, theses, founders, portfolio signals, and follow-up work.
5. **Beads↗**  
   A beads-style work queue for coding agents, driven from the ob client.
6. **Second brain↗**  
   A personal operating graph for notes, people, commitments, routines, and recurring work.

[→Browse the cookbooks↗](https://github.com/ModernRelay/omnigraph-cookbooks)

## At a glance

### Engine
- Rust

### Version
- 0.15.0

### Storage
- S3-compatible · Azure Blob (preview) · local disk

### Format
- Lance · open columnar

### Retrieval
- graph · vector · full-text · hybrid (RRF)

### Branching
- zero-copy · git-style · three-way merge · time travel

### Policy
- Cedar · enforced in-engine

### Config
- Terraform-style · cluster + operator surfaces

### Clients
- CLI · TypeScript SDK · Python SDK · MCP

### License
- MIT · open source

### Deploy
- embedded · BYOC (AWS, Azure, GCP) · on-prem

## FAQ

### What is a context graph?
+
A graph of what your agents need to know: people, projects, decisions, documents, and how they connect, kept current as agents and people work. Omnigraph is the database underneath one: typed, versioned, and searchable by graph traversal, vector and full-text in a single query.

### Is Omnigraph an open source graph database?
+
Yes. The engine, CLI and server are MIT-licensed on GitHub. The graph is stored as open Lance files in S3-compatible storage, Azure Blob (in preview) or a local directory, so it runs anywhere: embedded on a laptop with no server, or in your own cloud account.

### Graph database vs vector database: which do AI agents need?
+
Usually both. A vector database finds text similar to a question; a graph database follows how people, projects and decisions connect. Omnigraph does both in one query: vector, keyword and hybrid ranking over the same typed nodes you traverse, so there are no two stores to keep in sync.

### Can I use Omnigraph for GraphRAG?
+
Yes. Store documents, chunks and the entities they mention as typed nodes and edges, with embeddings on the nodes. One query ranks chunks by vector, keyword or hybrid similarity and traverses to the related entities and sources, so the context you give the model comes with its connections.

### What database should I use for AI agent memory?
+
One your agents can write to safely and you can audit. In Omnigraph each agent writes on its own branch, the schema is enforced on every write, Cedar policies run inside the engine, and changes reach main only through a merge you can diff first. Every version stays readable, so you can see what an agent knew and when.

### Is Omnigraph a Neo4j alternative?
+
For agent workloads, yes. Neo4j is a mature graph database. Omnigraph is MIT-licensed, keeps the graph as open files in storage you own, and is built around what agents need: git-style branches and merges, a typed schema checked on every write, built-in vector and full-text search, and in-engine policy.

### Does Omnigraph work with MCP?
+
Yes. omnigraph-server serves MCP at /mcp, so Claude, ChatGPT, Cursor or any MCP client can read the schema, run queries and, where your Cedar policy allows it, write. omnigraph mcp connects a local agent to a served graph.

### Where does my data live, and what does it cost?
+
In storage you own (S3-compatible, Azure Blob or local disk), as open Lance files that stay readable without us. The engine is free and open source: you pay only for your own storage and compute.

## Get started

```bash
$ curl -fsSL https://raw.githubusercontent.com/ModernRelay/omnigraph/main/scripts/install.sh | bash
```

[Documentation Install and deployment guides.↗](https://www.omnigraph.dev/docs)  
[Cookbooks Starter graphs and agent skills.↗](https://github.com/ModernRelay/omnigraph-cookbooks)  
[TypeScript SDK @modernrelay/omnigraph↗](https://www.npmjs.com/package/@modernrelay/omnigraph)  
[Python SDK pip install omnigraph↗](https://pypi.org/project/omnigraph/)  
[MCP server Built into omnigraph-server at /mcp.↗](https://www.omnigraph.dev/docs/operations/mcp)  
[Source on GitHub MIT-licensed graph engine.↗](https://github.com/ModernRelay/omnigraph)  
[Slack community Ask questions, follow development.↗](https://join.slack.com/t/omnigraphworkspace/shared_invite/zt-3wfpglyxj-lHvJGhuySPfqLtN35uJZNw)
