# Omnigraph > Open source graph database for AI agents and context graphs. Object-storage native, with Git-style branching and a typed ontology. Omnigraph keeps a typed property graph as Lance tables in storage you own: S3-compatible object storage, Azure Blob Storage or a local directory. Agents and apps read and write it through the `omnigraph` CLI, an HTTP server or MCP. Writes land on branches that merge like Git, and every commit stays queryable. Omnigraph is MIT-licensed. To set Omnigraph up for a user, follow the onboarding guide below. The CLI also carries an agent skill that matches its version: run `omnigraph skill show`. Every docs page is available as markdown: add `.md` to its URL, or send `Accept: text/markdown`. ## Start here - [Onboarding guide](https://www.omnigraph.dev/onboarding.md): For coding agents: install the CLI, build a first local graph, query it, then pick the next step for what the user wants to build. - [Install](https://www.omnigraph.dev/docs/getting-started/install.md): The installer downloads a release archive, verifies its SHA-256 checksum, and installs the binaries in ~/.local/bin. - [Quickstart](https://www.omnigraph.dev/docs/getting-started/quickstart.md): This walks the core loop end to end: define a schema, initialize a graph, load data, query it, and use a branch. It uses a local file-backed graph. - [MCP](https://www.omnigraph.dev/docs/operations/mcp.md): omnigraph-server serves the Model Context Protocol at /mcp, so Claude, ChatGPT, Cursor and other MCP clients can work with a graph with a URL and the caller's… - [All docs in one file](https://www.omnigraph.dev/llms-full.txt): Every docs page below, as markdown, in one file. ## Docs - [Overview](https://www.omnigraph.dev/docs.md): Lakehouse native graph engine with git-style workflows - Getting started - [Quickstart](https://www.omnigraph.dev/docs/getting-started/quickstart.md): This walks the core loop end to end: define a schema, initialize a graph, load data, query it, and use a branch. It uses a local file-backed graph. - [Install](https://www.omnigraph.dev/docs/getting-started/install.md): The installer downloads a release archive, verifies its SHA-256 checksum, and installs the binaries in ~/.local/bin. - [Deployment](https://www.omnigraph.dev/docs/getting-started/deployment.md): OmniGraph can keep a cluster on a local filesystem, S3-compatible object storage, or Azure Blob Storage. - Concepts - [Concepts](https://www.omnigraph.dev/docs/concepts.md): OmniGraph is a typed property-graph database. A graph contains nodes, edges, and a schema that defines their properties and constraints. - [Storage](https://www.omnigraph.dev/docs/concepts/storage.md): One OmniGraph graph lives at one storage root. The root contains the graph's schema, data, branches, and commit history. - Schema - [Schema Language (`.pg`)](https://www.omnigraph.dev/docs/schema.md): A schema declares the node and edge types a graph accepts. OmniGraph validates the same schema and constraints for mutation queries, loads, and branch merges. - [Blobs](https://www.omnigraph.dev/docs/schema/blobs.md): Use Blob properties for bytes that should not be projected through .gq. Blob values can contain graph-managed bytes, an external URI reference, or null. - Queries & search - [Query Language (`.gq`)](https://www.omnigraph.dev/docs/queries-search/queries.md): A .gq file contains named, typed queries. - [Session settings](https://www.omnigraph.dev/docs/queries-search/settings.md): A file may open with settings lines, before its declarations or its one statement. - [Explain](https://www.omnigraph.dev/docs/queries-search/explain.md): explain before a read declaration returns the query's v2 plan instead of its rows, regardless of the selected execution engine; before a load csv statement it… - [Explaining a load statement](https://www.omnigraph.dev/docs/queries-search/explain-load.md): The statement accepts every load option. It reads metadata, but no payload, and publishes nothing. - [Engine catalogue](https://www.omnigraph.dev/docs/queries-search/catalogue.md): The engine describes itself in GQ. - [Traversal and match patterns](https://www.omnigraph.dev/docs/queries-search/traversal.md): Omitted bounds always mean exactly {1,1}. Explicit {1,1} is equivalent. - [Diagnostics](https://www.omnigraph.dev/docs/queries-search/diagnostics.md): Every refusal of a query carries four things: a stable code, where the failure is, what was expected or violated, and one concrete fix. - [Mutations and Loads](https://www.omnigraph.dev/docs/queries-search/mutations.md): Mutation statements live inside a named .gq query. Run them with omnigraph mutate. - [Conditional mutations](https://www.omnigraph.dev/docs/queries-search/conditional-mutations.md): The condition compares the effective head of the target branch. - [Search](https://www.omnigraph.dev/docs/queries-search/search.md): OmniGraph combines vector, full-text, and graph patterns in one .gq query. - [Embeddings](https://www.omnigraph.dev/docs/queries-search/embeddings.md): OmniGraph can turn query text into a vector for nearest($document.embedding, $text). - Branching & history - [Branches, Commits, and History](https://www.omnigraph.dev/docs/branching.md): A branch is an isolated, durable graph history. Use branches to prepare and review a multi-step change without exposing intermediate results on main. - [Merging Branches](https://www.omnigraph.dev/docs/branching/merge.md): A merge integrates one branch into another and publishes the target change atomically across the whole graph. - [Changes, Diffs and Change Feeds](https://www.omnigraph.dev/docs/branching/changes.md): OmniGraph can describe what one commit changed, compare any two points in history, review what a branch changed, or deliver an ordered feed of changes on a… - Operations - [Maintenance](https://www.omnigraph.dev/docs/operations/maintenance.md): Follow the command-specific concurrency requirements below. - [Recorded operations](https://www.omnigraph.dev/docs/operations/recorded-operations.md): A cluster server can run optimize on a graph's main itself, so a scheduler or an operator starts it with one HTTP request and looks the result up later by an… - [Upgrade from 0.13 to 0.14](https://www.omnigraph.dev/docs/operations/upgrade-0.14.md): Finish pending deployments and resolve uncertain writes with the old CLI. Stop application traffic, servers and writers. - [Upgrading OmniGraph](https://www.omnigraph.dev/docs/operations/upgrade.md): Normal open accepts storage formats v14 to v17 and never migrates a graph: a v14 or v15 branch is stamped v16 at its first publish, and only the storage… - [Authorization and actors](https://www.omnigraph.dev/docs/operations/policy.md): OmniGraph uses Cedar policy bundles to authorize graph, server, and cluster configuration actions. - [HTTP server](https://www.omnigraph.dev/docs/operations/server.md): omnigraph-server serves every healthy graph in one applied cluster under /graphs/{graph_id}/…. It has no single-graph boot mode. - [Server logs and traces](https://www.omnigraph.dev/docs/operations/observability.md): The server writes text logs to stdout by default. Set OMNIGRAPH_LOG_FORMAT=json for structured logs. - [MCP](https://www.omnigraph.dev/docs/operations/mcp.md): omnigraph-server serves the Model Context Protocol at /mcp, so Claude, ChatGPT, Cursor and other MCP clients can work with a graph with a URL and the caller's… - [Troubleshooting](https://www.omnigraph.dev/docs/operations/troubleshooting.md): CLI failures include a human-readable message. Add --json where supported to receive structured fields suitable for automation. - [Storage failures and restart](https://www.omnigraph.dev/docs/operations/storage-failures.md): A served write sends many storage requests: data files, a transaction file, and last the conditional create of the graph's next manifest version, which… - [S3 cluster roots](https://www.omnigraph.dev/docs/operations/s3-cluster-roots.md): A cluster whose server is stopped has no served route for deployment, recovery or maintenance. - Clusters - [Operating a cluster](https://www.omnigraph.dev/docs/clusters.md): An OmniGraph cluster is a declarative bundle of graphs, schemas, stored queries and authorization policies. - [Cluster configuration reference](https://www.omnigraph.dev/docs/clusters/config.md): --config defaults to the current directory. Unknown fields and duplicate YAML keys are errors so that misspelled intent is never ignored. - CLI - [CLI guide](https://www.omnigraph.dev/docs/cli.md): Upgrading an existing installation? Start with the 0.13 → 0.14 checklist for before/after YAML and command examples. - [CLI reference](https://www.omnigraph.dev/docs/cli/reference.md): Use omnigraph --help or omnigraph --help for exact installed flags. - [Operator configuration](https://www.omnigraph.dev/docs/cli/targets.md): Use profiles for service/organization access and targets for resource access. This is target and credential protocol 2, with YAML version: 1. - [Open Studio](https://www.omnigraph.dev/docs/cli/studio.md): The command reads the operator configuration and nothing else: it sends no request to the server, reads no credential and starts no process that serves a graph. - [Managed data access](https://www.omnigraph.dev/docs/cli/managed-data.md): This guide covers data credentials for an existing managed cluster. - [Discover, configure and retire a managed cluster](https://www.omnigraph.dev/docs/cli/managed-lifecycle.md): These commands use your managed service identity and permissions. They do not open graph storage or require cloud credentials. - [Onboard and remove organization members](https://www.omnigraph.dev/docs/cli/managed-team.md): Invite teammates and manage organization membership through the managed CLI. ## Product - [Omnigraph](https://www.omnigraph.dev/index.md): Open source graph database for AI agents and context graphs. Object-storage native, with Git-style branching and a typed ontology. - [Omnigraph Studio](https://www.omnigraph.dev/studio.md): Omnigraph Studio, the Knowledge IDE: a GPU-rendered desktop app to visualize your ontology and graph, inspect knowledge, and review changes before they merge. For macOS, Windows and Linux. - [Omnigraph Cloud](https://www.omnigraph.dev/cloud.md): Omnigraph, managed for you, with an enterprise-grade control plane: SSO, isolation, policy, audit and declarative config. Join the private-preview waitlist. - [Source on GitHub](https://github.com/ModernRelay/omnigraph)