CAPTURE STORAGE OWNERSHIP PROVENANCE RETRIEVAL
auto vs. manual local vs. cloud who controls receipts, when/how semantic, cross-app, persistent
  • MemoryIntelligence™
  • Vector Store / RAG
  • Semantic Search
  • Knowledge Graph
  • NotebookLM

Memory infrastructure is judged across five dimensions. Most tools hit one or two. MI™ hits all five — and goes further: 95% token reduction, $0 per query, first memory in minutes.

Not a vector database · Not a knowledge graph · Not a search tool · Not a note-taking app ·AI finally has a memory standard. · Not a vector database · Not a knowledge graph · Not a search tool · Not a note-taking app ·AI finally has a memory standard. ·
The Infrastructure Spectrum

How the approach compares

Most tools stop at layer 2 or 3. MI starts where they end.

Infra 01
Vector Store / RAG
"Here's a chunk of text that matched your query."
e.g. Pinecone, Weaviate, basic RAG
Converts data into numerical embeddings and retrieves the closest match. Fast, but context-free. Hits 1–2 dimensions.
✗ No temporal context · ✗ No structure or meaning · ✗ No verification
Infra 02
Semantic Search
"Here's what you wrote, and roughly when."
e.g. Obsidian + plugins, NotebookLM
Meaning-based retrieval that understands intent. Better recall, but still dependent on what you manually put in. Hits 1–2 dimensions.
✗ Manual input required · ✗ Single source only · ✗ No provenance
Infra 03
Knowledge Graph
"Here's what you wrote, and here's how it connects to something else."
e.g. Neo4j, Diffbot, custom graph DBs
Maps entities and relationships across data. Powerful for structured domains, but brittle with real-world unstructured input. Hits 1–2 dimensions.
✗ Expensive to maintain · ✗ Breaks on messy data · ✗ No receipts or rights layer
MI™
MemoryIntelligence™
"Here's what you captured, when, verified. Structured automatically across all your sources, retrievable in milliseconds, at zero per-query cost."
Patent Pending
Structures, compresses, and receipts every piece of data locally. No cloud. No manual effort. All five dimensions.
✓ Auto-capture · ✓ Verifiable data receipts · ✓ Cross-app, local-first

How the tools compare

Click any tool to see where it overlaps with MI, and where it falls short.

MemoryIntelligence™
MI™ SDK
Everything Obsidian does, and what it never could.
Matches
✓ Local first✓ Data ownership✓ Note linking✓ Privacy
MI also adds
+ Auto-capture+ Provenance receipts+ Cross-app memory+ Zero maintenance+ $0/query
Bottom line
Obsidian is a filing cabinet you stock yourself. MI is memory that stocks itself.
Compute cost
95% token reduction. $0 per query.
Competitor
Obsidian
"A second brain for your notes", you still have to build it yourself.
What it is
Local, private markdown note-taking with graph-based linking. Manual, always.
Overlap
✓ Local first✓ Data ownership~ Linking
Falls short
✗ 100% manual✗ No auto-capture✗ No provenance✗ No receipts✗ No cross-app✗ Single silo

Most Obsidian vaults become graveyards within months. Memory shouldn't require this much upkeep.

Layer
Infra 02: Semantic search, fully manual
MemoryIntelligence™
MI™ SDK
Everything NotebookLM does, without giving your data to Google.
Matches
✓ Document retrieval✓ Q&A interface✓ Source grounding
MI also adds
+ 100% local+ Persistent memory+ Grows over time+ Developer SDK+ No hallucination
Bottom line
NotebookLM is a session. MI is memory. NLM forgets when you close the tab. MI never does.
Hallucination risk
Near zero. MI retrieves, it doesn't generate. Every result is verifiable.
Competitor
NotebookLM
Google reads everything you upload. Session ends, memory is gone.
What it is
Google's AI notebook. Upload documents, ask questions. But Google owns the session and your data.
Overlap
~ Document retrieval~ Q&A interface
Falls short
✗ Cloud only✗ Google owns your data✗ No provenance✗ Session-based✗ Memory doesn't persist✗ No developer SDK

Every upload is a data gift to Google. Every session ends with everything forgotten.

Layer
Infra 02: Semantic search inside a Google-controlled silo
MemoryIntelligence™
MI™ SDK
MI is the memory infrastructure Omni sits on top of, if it could.
Matches
~ Data pipeline thinking~ Structured output
MI also adds
+ Unstructured data+ No SQL needed+ Auto-capture+ Edge processing+ Provenance receipts
Bottom line
Omni shows you data. MI remembers it. MI could be the memory engine that powers a BI tool like Omni.
Who installs it
Any developer. No data team required. No SQL. No warehouse.
Competitor
Omni
BI dashboards. Not in the memory business at all.
What it is
Business intelligence and visualization. Think Looker or Tableau. Dashboards, SQL, structured analytics for teams.
Overlap
✗ Minimal Different layer entirely.
Falls short
✗ Not in memory space✗ Requires SQL✗ Requires data team✗ Cloud warehouse only✗ No unstructured data

Omni shows you the data. MI is the reason there's anything worth showing.

Layer
Visualization layer, not memory infrastructure
MemoryIntelligence™
MI™ SDK
Both structure raw data. MI does it without SQL, a warehouse, or a data team.
Matches
✓ Data structuring✓ Pipeline thinking✓ Data lineage
MI also adds
+ No SQL needed+ Unstructured data+ Edge processing+ Provenance receipts+ Up in an hour
Setup time
Under an hour. npm install and go. dbt takes weeks, a warehouse, and a dedicated eng team.
Data type
Conversations, notes, documents. Human memory, not rows and columns.
Competitor
dbt Labs
SQL-based transformation for warehouses. Not built for humans.
What it is
Data transformation tool for engineers. Cleans and models structured data in your cloud warehouse.
Overlap
~ Data structuring~ Pipeline thinking
Falls short
✗ Enterprise only✗ Requires SQL expertise✗ Cloud warehouse required✗ No provenance receipts✗ No memory retrieval✗ No edge processing

dbt takes weeks to set up, requires a specialist, and still can't process a Slack message.

Layer
Infra 01/02: Transformation for warehoused structured data

All tools, all dimensions

Where the key differentiators actually land.

Dimension MI™ SDK Obsidian NotebookLM Omni dbt Labs
Local / Edge Processing 100% local Yes Cloud (Google) Cloud Cloud warehouse
Auto-capture Auto + manual Manual only ~ Upload required Manual ~ Pipeline setup
Provenance / Receipts Full data receipts None None None ~ Lineage only
Unstructured data All formats Markdown Docs/PDFs Structured only Structured only
Semantic retrieval 451% improvement ~ Plugin required AI-powered SQL only Not a retrieval tool
Cross-app memory Any connected source Silo Silo Silo ~ Warehouse only
Developer SDK npm install No No ~ API Yes (SQL)
Per-query cost $0.00 Free Free (Google) Subscription Subscription
Data ownership Always yours Yours Google's Vendor Warehouse vendor
Requires technical team One developer No No Yes Yes (data eng)

Ready to see the difference?

Install the SDK in under an hour. No data team required.

Explore MI™ SDK →