The Origin Graph is a living knowledge graph of your entire component ecosystem — relationships, history, usage, and design tokens — all queryable in real time.
A two-pass pipeline — static analysis plus runtime capture — builds a continuously updated graph with zero manual annotation required.
An AST walker scans every component file, extracting imports, prop signatures, and design-token references without running your code.
A React Fiber hook captures live props and state at render time, adding real-world usage data that static analysis alone can't see.
Nodes and typed edges — usage, inheritance, token links — are written to Supabase, forming a queryable graph that updates incrementally.
A REST API and MCP tool set expose the graph to AI agents, the diff engine, and the Inspector — answering natural-language queries in real time.
Because every design-token link is a first-class edge in the graph, changing --color-primary immediately highlights every component downstream. No Storybook trawl. No grep. Just the answer.
Every node in the graph is a structured JSON object accessible via REST or MCP tools. AI agents, CI pipelines, and custom tooling can query your entire component ecosystem programmatically — no scraping, no docs to keep in sync.
Origin Graph is designed to stay accurate as your codebase moves — incremental, typed, and accessible to any tooling that speaks REST or MCP.
A Babel-based AST walker traverses every component file on save, extracting imports, JSX usage, and design-token references — without executing any code.
Static analysisA Fiber hook captures live props and state during rendering, adding real-world usage data — actual prop values in production — that static analysis cannot infer.
RuntimeNodes and edges are persisted in Supabase Postgres with a graph-friendly schema. Postgres views and RPC functions serve subgraph queries with sub-10ms latency.
PersistenceThree edge types — usage, inheritance, token — are stored with directionality and metadata, making impact analysis a simple graph traversal rather than a heuristic search.
Agent Bridge exposes the graph as an MCP tool. Ask "What will break if I rename Card?" in plain English from Cursor, Claude Code, or any MCP-compatible editor.
Agent BridgeOnly the files touched since the last commit are re-indexed. No full rebuild. A project with 1,000 components updates in under two seconds on a file save.
PerformanceThe graph is infrastructure. Every Originmain feature that needs to understand your codebase queries it first.
Early access is free. Connect your repo and the first full graph index runs in under a minute.