2.0Memory

The knowledge base that writes itself.

Under the chat is a working memory: your clients, decisions, projects, and people, connected as you talk. Nothing to author, nothing to keep current.

Pinch or scroll to zoomDrag to pan
The knowledge base that writes itself. in Naumu

Every wiki has one good month.

Authoring is a second job stacked on the first, so wikis rot. Naumu builds the same knowledge out of the conversation your team is already having.

Nothing to author

No blank page and no template - saying what happened is the writing.

Never out of date

The newest thing your team said is already in it, because the work is what writes it.

Corrections are diffs

Say what changed and accept the proposed edit, attributed and reversible.

A source on every fact

Each fact traces back to the member who added it and the thread it came from.

An answer, not a results page.

Ask in plain language and Naumu answers from your own material, searching by meaning, with the notes, threads, and people it drew on linked in the reply.

You
You9:41 AM
new hire asking why we bill Meridian monthly when everyone else is annual - is that written down anywhere?
Ask Naumu...
An answer, not a results page.

Start from what you already have.

Paste your website, add your files, or connect Slack, Jira, Linear, and ClickUp. Naumu reads them and does a first pass you can correct.

Integrations

One message to start

Attach what you have, say what you are - the first pass builds itself.

Files and folders

Specs, transcripts, and exports come in as a first pass you correct.

Connected tools

Issues and tasks sync in one way and stay current as they move.

Your own AI

Claude and ChatGPT connect over MCP and write the same memory, acting as you.

Start with one project.

No signup, no credit card.