The system of record for what your AI knows.
Memuron: the system of record for what your AI knows — an enterprise AI memory layer with source-traceable answers and on-premise deployment.
Enterprise AI forgetswhat your organization learns.
On Monday a team makes a decision. On Tuesday someone issues a correction. Most AI systems keep both, with no idea which one won — so your AI can hand back either version as if it were the truth.
Memuron settles it the moment it arrives: is this something new, or a correction to something you already hold? The correction becomes the answer — and the version it replaced stays on the record.
Storing more text doesn't make your AI more right.
Search finds the passage closest to your question. It has no opinion about whether that passage is still true.
Stores everything.
Then guesses which version you meant.
Decides what stays.
Checked against what you already hold.
Keeps both.
Ask twice, get two answers.
Keeps the right one.
The version it replaced stays on the record.
Returns a score.
No author. No date. No history.
Returns a receipt.
Source, author, and what it replaced.
Their cloud.
Your knowledge, on their terms.
Your walls.
On-prem, your VPC, or air-gapped.
Your AI gets one answer, and it stays right.
Underneath the graphs and the embeddings is a loop you can actually supervise: every decision gets checked, gets written down with its source, and feeds the one after it.
- 01
Something gets decided
A person or an AI agent makes a call, based on the context it had at the time.
- 02
Memuron checks it
Before it is stored, Memuron compares it to what you already know — and merges, links, or rejects it.
- 03
Your team confirms
Corrections, approvals, and outcomes are captured as they happen, not reconstructed later.
- 04
It's recorded, permanently
Who said it, where it came from, and what it replaced — written to a log that is added to, never rewritten.
- 05
The next answer starts from it
What has been confirmed once is available to every team, every agent, and every session after it.
The loop closes. Correct something once and it stays corrected. Your next decision starts from what you have already confirmed — not from scratch.
Ask it what your company already decided.
Every team asks the same kind of question: what did we decide, and is it still true? Memuron answers with the receipt attached.
“Why did we drop the retry limit?”
It was cut on 8 Apr after a duplicate-write incident. The decision moved into the v1.1 backlog and was never revisited.
- Incident review · 7 Apr — duplicate writes traced to retries
- ENG-318 — retry limit descoped from spec
- Agent trace · deploy-bot — flagged as still open
“What did we actually promise Northwind?”
A 60-day payment exception, agreed verbally on 27 Feb and confirmed in writing on 3 Mar. It supersedes the standard terms in the original quote.
- Deal notes · 27 Feb — exception agreed
- Contract addendum v2 — 60-day terms
- Superseded: quote v1 — standard 30-day terms
“Which policy version approved this claim?”
Policy v2.3, retired on 14 Mar. The exception was signed off by Risk on 2 Mar and replaced by v2.4 on 8 Apr.
- Policy register — v2.3 active 2 Jan to 14 Mar
- Risk sign-off · 2 Mar — named approver on record
- Superseded by v2.4 · 8 Apr
“Has this customer been told something different before?”
Yes — twice. The refund window was quoted as 30 days in January and corrected to 14 days in March. The March answer is the current one.
- Ticket #4412 · Jan — 30-day window quoted
- Correction · Mar — policy updated to 14 days
- Current: refund policy v3
“What has changed since the last review?”
Nine decisions recorded, two of them reversals, and three commitments still open past their date. Both reversals sit in pricing.
- Pricing review · 8 Apr — Mar framework withdrawn
- 9 decisions recorded since 26 Feb
- 3 commitments past due
Not your inbox. Memuron answers from what your own agents, tools, and services write into it.
You decide what goes in. Memuron decides what stays true.
Answers you can trust, knowledge that sticks, and control you can prove.
Answers you can trust
Contradictions are settled the moment something is written, so what comes back out is what your organization actually decided.
Finds the right answer, not the closest text
Vector, lexical, and link-description matches surface the memory plus the edge that made it relevant.
Follows the connection, not just the keyword
Ask a question and walk the edges that answer it — not just the text that matches it.
Hands your model a clean, cited answer
Prompt-ready blocks with citations, graph links, breadcrumbs, and a hard budget.
Knowledge that sticks
Corrections last. Sources stay attached. What your AI learned last quarter is still there this quarter, instead of resetting every session.
Wrong facts can be fixed, not buried
live · hover a nodeMemuron stores every relationship as a first-class memory_link, including self-loops and parallel edges agents can inspect and correct later.
Every fact keeps its receipt
Attach custom_id, session, thread, source ID, and URL to every memory or document.
Point it at your files and links
Fetch pages, sync local folders, and keep files mapped to stable graph nodes.
Control you can show an auditor
Separation between customers, a full history of every change, and rules for what is kept and for how long — so adopting AI does not mean losing oversight.
One customer's data can never reach another's
Cryptographic tenant_id boundaries plus spaces for project, team, and user context.
••••
••••
Replay any change, any time
Every create, update, and link is a typed, append-only event you can replay.
Keep what you must, delete what you must
Scope what each space can see, and retain or remove memory by scope.
MCP native. Connect Cursor and other agents over an authenticated HTTP stream — no key wrangling. Full SDK and API in the docs.
Five moves, one graph.
Follow a single memory as it moves through Memuron — connect, ingest, verify, recall. Then a fifth move that turns stored context into something you can actually trust.
- quickstart$ pip install memuronSDK · MCP · REST01 / CONNECT01
Plug in, in minutes.
One SDK, MCP server, or REST call. Runs anywhere your agents run — edge functions to long-lived services.
- spec.pdfthreadtool_call02 / INGEST02
Feed it any context.
Docs, chat threads, tool calls, decisions. Memuron extracts and types the content for retrieval — no schema wrangling.
- Guardian · verifiedmergelinkduplicate03 / VERIFY03
The Guardian checks it.
Before anything lands, the Guardian checks it against what you know: dedupe, merge, link, or reject. Not a blind vector dump.
- why did onboarding stall?04 / RECALL04
Query one living graph.
Memory, RAG, and profiles share a single semantic graph your agent traverses — not three systems you stitch together.
- append-only ledgeragent · claudeconfirmedhuman · reviewcorrectedsource · spec.pdflinked05 / COMPOUND05
Every recall is provable.
Source, actor, and full history land in an append-only ledger. Corrections compound — the next decision starts from what you've verified.
Steps 3 and 5 are the difference. Anyone can store and retrieve vectors. Verifying what enters and proving what came out is what makes the memory worth building on.
No new app for anyone to learn.
Memuron sits behind the tools your teams already use. Connect it once, and what one assistant learns is available to the next one — same memory, same rules, no copying context between windows.
- ClaudeChat
- ChatGPTChat
- Claude CodeCoding agent
- CursorEditor
- Google DriveFiles
- Memuron CLIFolder sync & CI
Prove what your AI knew, and why it acted.
Every decision leaves a trail. Rebuild it from the sources, the corrections, and what actually happened — narrowing with Retrieve, Trace, and Confirm — so risk, compliance, and leadership get a straight answer instead of a guess.
Which rollback decisions were authorized after recent production incidents?
Before a decision can stand as institutional evidence, it has to clear five bars. Memuron is built so every memory can.
Authenticity
Every memory carries who wrote it, from what source, in which session, and when — so you can prove it is what it claims to be.
Integrity
Nothing is silently overwritten. Creates, corrections, and links are typed append-only events — the record stays tamper-evident.
Completeness
Prior versions, linked sources, and corrections stay in the trail — the full decision history, not a cherry-picked snippet.
Reliability
The Guardian verifies before write; hybrid search and graph recall use governed, inspectable methods — not opaque vector dumps.
Strict Chain of Custody
Who wrote, who verified, what changed, and who recalled — a chronological trail you can replay from first write to last audit.
Retrieve records that mean “deploy decisions.”
Meaning-ranked retrieval surfaces institutional knowledge about shipping — even when the wording differs across teams and systems.
Memuron runs where your data has to stay.
On-prem, in your own cloud, or fully air-gapped — same API, same graph, same append-only ledger. Wherever it runs, the memory and its full audit trail stay inside your boundary.
In your data center.
Self-host the engine on bare metal or your own Kubernetes. The graph and the ledger never leave your perimeter.
In your VPC.
Bring your own cloud on AWS, GCP, or Azure — provisioned inside your account, under your keys, from day one.
Fully offline.
Run the whole stack air-gapped with zero outbound calls — for classified, regulated, or sensitivity-first work.
Available on Enterprise plans. Reviewing Memuron for a regulated or security-sensitive deployment? We'll walk your team through isolation, data residency, retention, and self-host options.
Talk to an enterprise architectYour Agent
remembers what your organization already verified.
Every verified decision compounds into shared, governed memory — queryable across teams, agents, and sessions, never from scratch.
No lock-in on the memory your business runs on.
Memuron is the chassis; Arthaanu is the engine underneath it — and it is open source. You can read the code, run it yourself, or take your memory with you. Nothing about the knowledge your company builds up is locked to a vendor, including us.
the append-only source of truth — objects, encodings, relations and traces
“v2.3 deploy was rolled back.”
0.88, 0.31,
-0.17, … ]
See it against your own stack.
Book 30 minutes. We'll map Memuron to your AI stack, your governance rules, and where your data is allowed to live — before you commit to anything.