maven

Shared AI memory · governed · time-aware

One memory.Every agent.

The memory layer under Claude, Cursor, and your agents. One audited source they all trust, instead of answers that disagree.

Works with any model · SOC 2-ready · connects over MCP

The brain underneath your existing stack

  • Anthropic
  • Cursor
  • GitHub
  • Linear
  • Notion
  • Jira
  • Confluence
  • Perplexity
  • Google Gemini
  • Figma
  • GitLab
  • Obsidian
  • Anthropic
  • Cursor
  • GitHub
  • Linear
  • Notion
  • Jira
  • Confluence
  • Perplexity
  • Google Gemini
  • Figma
  • GitLab
  • Obsidian
§01
The problem

Your assistants each remember something different.

One decision lives in Slack, a doc, and a stale wiki — and they disagree. Each assistant answers from whatever it saw first. Confidently. Usually wrong.

  • Each tool and each user keeps its own memory.
  • Old facts never expire, so last year's answer still sounds true today.
  • No record of who said it, who approved it, or what the AI believed.
one fact · three answers
slack/#engtimeout = 30swiki/apitimeout = 45sADR-114timeout = 60sresolvecurrent = 60s
The human side

It should feel like the company just remembers.

A person thinking, surrounded by scattered note-cards and a stray node
The problem

Nobody remembers the same thing.

Decisions live in someone's head, a thread, a half-stale doc. Each assistant starts from zero.

A person at a laptop recalling a decision, memory cards and a node floating nearby
With Maven

Just ask — it recalls.

The current, approved answer comes back in context, with where it came from attached.

Two people passing a highlighted memory card between them
For everyone

Shared the moment it's known.

What one person teaches Maven, every assistant and teammate quietly inherits.

§02
How it works

From scattered chatter to one answer you can trust.

step
01

Ingest

Connect Slack, GitHub, Linear, and docs. Maven pulls out the decisions and rules that matter.

facts + sources
step
02

Resolve

When facts disagree, Maven keeps the newest one from the most trusted source — and shows its work.

current vs. past versions
step
03

Serve

Every AI tool reads the same memory over MCP. Switch models anytime — the memory stays.

one MCP endpoint

Why now

$37B

Spent on enterprise AI in 2025.

95%

Of AI projects stall on memory, not models.

10k+

Public MCP servers — the tools Maven plugs into.

2:1

Teams pick specialized tools over building their own.

Sources: Menlo Ventures · MIT · Linux Foundation, 2025–2026.

§03
The product

See what your org knows, in one place.

Why did we change onboarding in Q1?

See how it connects
maven● live
Incidents
Policies
Customers
Teams

feature / onboarding

Self-serve flowauthoritative

source: ADR-072 · @ceo · Feb 2026

version history

v2Self-serve flow@ceo · now
v1Guided setup@pm · Jan

{ } via MCP · get_current_truth()

§04
Why Maven

Not just storage. A governed source of truth.

01

Resolve conflicts, and show its work.

When sources disagree, Maven picks a winner and shows why — by authority and recency, not a coin flip.

Several sources converging into one resolved answer
02

Know what was true then, not just now.

Ask what was true in March, when it changed, and why. Old facts are kept, not erased.

A timeline of facts with the current point marked
03

Memory your CISO signs off on.

Every fact carries who said it, who can see it, and its full history. Governance built in.

See security & governance
An audited ledger of facts secured with a lock

The thesis

The winner of the AI era won’t have the smartest assistant.It’ll own the memory every assistant trusts.

§05
Over time

Time-travel the truth.

Drag the timeline. Ask one question and get what was true at that moment — not just today.

one query · every point in time

service / billing · api.timeoutas_of now
45sconfirmed

source: INC-2891 · incident

replaced 60s

§06
Questions

Questions, answered.

§07
Get started

Make every decision provable.

Start with one engineering team and the decision-memory wedge, then grow across the org on the same governed spine. No migration project, no rip-and-replace, no begging people to change tools.

Plugs in over MCP · keep every tool you already use · one brain behind them