Explore the system

The state layer for agentic workflows

Give your agentic fleet
one shared memory that compounds.

Ouroboros allows you to turn your documents, your code, your research, and every observation your agents make into a typed, queryable graph. Quote-grounded by code so the model can't hallucinate facts. Scoped per connection so each agent sees only what you authorize. Journaled so every write is reversible. What one agent learns today, every agent scoped for it on the graph knows.

A true state layer and coordination platform for the agentic era. Not a wiki, not a harness, the foundation. The purpose of Ouroboros is to give individuals the ability to structure their data, remain sovereign over that data, and increase the efficiency and power of their agentic workflows. To learn about the current capabilities of Ouroboros: Explore the system.

Private beta · BYOK (Claude Code, Codex, Cursor, your own) · Local-first

The thesis

Pay once. Query forever.

Most teams don't notice the pattern. Every fresh agent session re-reads the same documents from scratch. Ask your agent about a 200-page lease today — 60,000 tokens, ten minutes, one answer. Ask again tomorrow in a new session — another 60,000 tokens, another ten minutes, the same answer. A week of that across a few agents and a handful of documents is half a million tokens of pure rework. Your agent is slow the whole time, waiting for the same parse to complete before producing the same answer it produced yesterday.

Same math for code. A coding agent on a fresh repo burns context before it writes a single line — globbing the file tree, reading a dozen files to map the architecture, following imports, hunting for callers. Every new session repeats it. Every agent you switch to repeats it. The repo didn't change; the cost did.

Without Ouroboros

Pay every time.

  • First read: 60k tokens · ~10 min
  • Same question tomorrow: 60k tokens · ~10 min
  • 10 questions across 5 agents: ~3M tokens of rework
  • Cost trajectory: linear in queries — every agent re-derives every answer.

With Ouroboros

Pay once. Query forever.

  • One-time extraction: a few thousand tokens, the document lands in the graph.
  • Same question tomorrow: a few-thousand-token SDK query, sub-second round-trip.
  • 10 questions across 5 agents: the one-time extract, plus ~50k tokens of cheap queries.
  • Cost trajectory: flat after extract — every agent gets the same indexed answer.

The compounding is the whole point. Documents you ingested last week — or modules you parsed last week — aren't dead weight in your token budget. They're free knowledge for every agent you'll ever connect, today and a year from now.

The system

One daemon. Three layers.

Files on disk you can open without it. A typed knowledge graph your agents read through one connection. A gate between them that nothing crosses without your permission.

The gate

Every agent connection is minted by a click in the tray app — never by a config file, never by an HTTP call. Each connection has an explicit scope: which entities, which actions. Read it back, change it, or revoke it from the same tray.

The engine

Drop a folder, get a typed knowledge graph. Drop a repo, get a symbol graph with every import, call, and reference resolved. Every claim mined from a document carries a verbatim quote that's substring-checked against the source — claims whose quotes don't literally appear get dropped. The check is a for-loop, not a model.

The vault

Documents are content-addressed at ~/Ouroboros/vault/sha256/. Wiki pages are plain markdown at ~/Ouroboros/vault/wiki/. Open them in Obsidian; the wikilinks, embeds, and tags work natively. The encrypted SQLite is a projection of the files, not the other way around.

architecture: gate → engine → vault
flowchart LR
    A1[Claude Code] --> G
    A2[Codex] --> G
    A3[Cursor] --> G
    A4[Your agent] --> G
    G[The gate<br/>per-connection scope<br/>session-key auth<br/>audit log every read]
    G --> E[The engine<br/>tree-sitter ingest<br/>quote-verified extraction<br/>hybrid retrieval]
    E --> V[The vault<br/>content-addressed files<br/>plain-markdown wiki<br/>encrypted libsql]
    V -.opens directly in.-> O[Obsidian / your editor]

Get it

You can't, yet.

Ouroboros is in private beta and the source is closed. We're not taking sign-ups, running a waitlist, or selling early access. The page you're reading is the marketing surface; the product behind it is still the dogfood instance.

When the source opens and packaging ships, the install will be one command and you'll be able to point your own agents at your own machine. Until then, the right thing to do is wait. There is nothing to buy and nothing to download.

If you're an MCP-curious developer, a researcher with a folder of PDFs, or a privacy-conscious power user — keep reading the deep-dive pages so you'll recognize what's shipping when it does.