Omnigraph | Modern Relay

[As code]Graph as code<br>Schema, context, policies, UI and infra are declarative files: versioned like code, enforced by the engine.

ContextOntologySecurityUIInfra<br>Context-as-code<br>Git-style branch, version, and merge for data. A set of linted, typed queries defines each lens on the graph, and branches keep concurrent batch writes safe.<br>How it reads<br>find_experts ranks people three ways at once (vector similarity, BM25 full-text, and graph structure) and fuses them with rrf(). The whole lens is a file you lint, version, and review.

queries/team.gq<br>query find_experts($topic: String) {<br>match { $p: Person }<br>return { $p.name, $p.role }<br>order { rrf(nearest($p.embedding, $topic),<br>bm25($p.bio, $topic)) }<br>limit 5

[Workflow]Git-style workflows<br>Many agents work the same graph at once, each on its own branch, merging into main only through review.

matchresolvereviewClaude Codeclaude/dedupeingestlinkembedreviewHermeshermes/ingestmain<br>Fig. A single hour on one graph: Hermes adds new data on hermes/ingest while Claude Code dedupes records on claude/dedupe.

01Branch

Claude Code and Hermes each fork main into their own branch.<br>cheap fork$ omnigraph branch create<br>02Write

Hermes adds new nodes and edges while Claude Code dedupes existing records. Isolated branches never collide.<br>schema + policy enforced$ omnigraph mutate<br>03Review

Each branch's diff is approved by a human or another agent before it lands.<br>human or agent$ omnigraph diff<br>04Merge

Both land on main in review order, three-way and attributed to their agent.<br>three-way · audited$ omnigraph branch merge

✓hermes/ingest and claude/dedupe merged into maineach commit attributed to its agent

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↗

[Features]Key features

Hybrid retrieval<br>Vector, full-text, and graph traversal in one query, fused with rrf().

Typed schema<br>Writes are typed and checked, rejected at the branch before they land.

Atomic whole-graph commits<br>Readers see a consistent snapshot, never a partial write.

Three-way merge<br>Row-level merges with typed conflicts, not last-write-wins.

Time travel<br>Every version stays queryable; pin a query to any snapshot.

Approval-gated operations<br>Destructive changes need explicit approval before apply runs.

Object-storage native<br>Data, catalog, and state live in one S3-compatible bucket.

Actor audit<br>Every commit records its actor, resolved server-side.

Anti-probing security<br>Denied and nonexistent are indistinguishable from outside.

[For agents]Graph optimized for agents<br>Your agents work with graph data the way engineers work with code: branched, typed, reviewed, merged, audited, and governed.

01An agent reads the graph as context.<br>Agent asksGraph returns<br>Who knows X?→5 people<br>What changed?→12 commits<br>What's related?→8 docs

The graph is how an agent understands the business.

02Everything that defines it is a file.<br>schema.pg<br>queries.gq<br>policy.yaml<br>notebook.yaml<br>cluster.yaml

Schema, queries, policy, dashboards, deployment. Versioned like code.

03The discipline code already has.<br>BranchTypeReviewMergeAuditGovern<br>Everything you trust for code now governs knowledge.

04Agents move at a different speed.<br>Teamquarterly

Agent fleetweekly

A team migrates a schema quarterly. A fleet wants to weekly.

05Plan. Apply. Review.<br>PlanApplyReview<br>Declarative files with a plan/apply cycle: the only form an agent can write and a human can review.

[Clients]SDKs and plugins<br>An open platform, easy to integrate — available to agents, humans, and apps through different means.

01TypeScript SDK<br>Typed client for omnigraph-server: instance-per-client, typed errors, async-iterator streaming export.<br>@modernrelay/omnigraph ↗02MCP server<br>The graph as agent tools — schema, branches, queries, mutations and ingest, bridged into LLM hosts over stdio.<br>@modernrelay/omnigraph-mcp ↗soonGenerative notebooks<br>Declarative notebooks generated from the graph — lenses an agent can write and a human can read.

soonMarkdown two-way sync<br>Edit graph content as markdown files; changes flow back as reviewed commits.

soonHermes plugin<br>Omnigraph as the context layer for Hermes agents.

→omnigraph-ts monorepo↗

[Deployment]Deploy on infrastructure you own<br>Not options to weigh, but guides and blueprints to follow: docs to run locally, guides for your own servers, and clone-and-go blueprints for the cloud.

Docs<br>Local<br>A folder on your machine. graphs/*.omni, zero infra.<br>Read the docs ↗Guide<br>Self-hosted<br>Your server plus any S3-compatible store.<br>Coming soon<br>Blueprint<br>AWS<br>S3, IAM and KMS inside your own account.<br>Clone the blueprint ↗Blueprint<br>Railway<br>One service booting from one bucket.<br>Clone the blueprint ↗<br>your machine▸your cloud

→Read the deployment guide

[Cookbooks]Start from a working graph<br>Cookbooks are runnable Omnigraph projects: schema, queries, seed...