Memuron lets AI agents remember.

Memory that decides, merges, links, and evolves.

For teams building AI agents that can't afford to hallucinate — in fintech, healthcare, and other high-stakes systems. Memuron resolves contradictions at write-time, so your agent never has to guess which memory is true.

Start BuildingRead the Source
Memories stored
Contradictions resolved / day
Live across Memuron
01 — The Problem

Agents have
amnesia
Vector DBs make it worse.

Every 90 seconds, an agent is handed a contradiction it cannot resolve.

Tell an agent “I like blue” on Monday and “actually, I prefer red”on Tuesday. A plain vector store returns both — a contradiction it can't resolve.

Memuron decides at write time: is this a new fact, or an update to one you already hold? Then it collapses the two into one evolved memory.

Every contradicted memory is a silent hallucination waiting to surface.
MON“I like blue”TUE“I prefer red”24 HOURS LATERsame two inputsPLAIN VECTOR DBlike bluesim 0.91prefer redsim 0.89!contradiction returnedMEMURON GUARDIANlike blueprefer redEVOLVED MEMORYprefers redmerged · 1 node
02 — THE GUARDIAN

An LLM pipeline that shapes memory before it commits.

Every ingest runs through the Guardian: it retrieves candidates with hybrid search, decides create-vs-update, draws semantic links, and commits typed events to an append-only ledger.

INGEST

Raw content arrives from the SDK or API and is accepted as an immutable payload.

payloadcontent in
auto-cycling · hover to focus a stage
INGESTpayloadQUEUEjob_idEMBEDpgvectorRETRIEVEhybridGUARDIANdecidesCREATEUPDATELINKedgesCOMMITledger
03 — WHAT YOU GET

A memory system, not a vector bucket.

Agent-repairable memory graph

live · hover a node

Memuron stores every relationship as a first-class memory_link, including self-loops and parallel edges agents can inspect later.

Hybrid graph search

Vector, lexical, and link-description matches surface memories plus the edge that made them relevant.

Context assembly

Prompt-ready blocks with citations, graph links, breadcrumbs, and a hard budget.

[M1][L1]

URL and folder ingest

Fetch pages, sync local folders, and keep files mapped to stable graph nodes.

URLMDPDFDOCXXLSX

Stable source identity

Attach custom_id, session, thread, source ID, and URL to every memory or document.

Multi-tenant scoping

Cryptographic tenant_id boundaries plus spaces for project, team, and user context.

org:acme
••••
org:globex
••••

MCP native

Connect Cursor over an HTTP stream, authenticated with Clerk OAuth — no key wrangling.

/docs/mcpcursorclerk oauth

Semantic traversal

Don't just match text. Ask a question and walk the edges that answer it.

node→ caused_by →node→ relates_to →nodehops ≤ 2 · sim ≥ 0.7
04 — QUERY LIKE A FILESYSTEM

Pipe semantic search through your graph.

One query, three stages. Toggle each below and watch the set narrow — from a fuzzy semantic match, down the graph's edges with traverse, to a final grep.

Which rollback decisions were tied to recent deploy incidents?

$ cwd spaces.work.deploys
>semantic "deploy decisions"|traverse caused_by · 2|grep "rollback"
3 memories· 0.018s

First, find memories that mean “deploy decisions.”

Semantic search reads for meaning, not keywords — so it surfaces anything about shipping, even without those exact words.

6 candidates
ranked by meaning
node_4f2rollback of v2.3 deploy after error spike0.91
node_9a1deploy gate now requires canary pass0.84
node_c07incident: latency regression in prod0.79
node_2b8new rollback policy requires sign-off0.76
node_7e3standup notes — sprint planning0.61
node_a15weekly deploy cadence adopted0.58
05 — UNDER THE HOOD

Memuron is the chassis. Arthaanu is the engine.

Memuron handles the product — tenancy, ingest jobs, the Guardian. The horsepower comes from Arthaanu, an open-source semantic engine you can inspect, self-host and swap: an append-only ledger, deterministic encoders, rebuildable projections, and the retrieval math underneath.

THE ENGINE BLOCK
ArthaStoreappend-only ledger

the append-only source of truth — objects, encodings, relations and traces

ONE LEDGER · EVERY INDEX REBUILDABLE
semantic_eventsappend-only
SEQEVENTMESSAGE
Vector0
sqlite-vec · cosinerebuilding…
Lexical0
FTS5 · BM25rebuilding…
Graph0
edges · traversalrebuilding…
Temporal0
point-in-timerebuilding…
SIX WAYS TO HOLD A MEANING — THE COMPRESSION GRADIENT
The same memory, re-encoded left to right — each arrow is a recorded transform.
01token
rolledbackv2.3deploy
extract
02tag
#deploy#rollback
link
03relation
caused_by →
assert
04claim

“v2.3 deploy was rolled back.”

embed
05embedding
[ 0.12, -0.04,
0.88, 0.31,
-0.17, … ]
summarise
06summary
tokencompression · very highloses context

Build agents that actually remember.