What “persistent” leaves out
Memory platforms do keep what they learn across sessions and restarts — that part works. What they don’t give you is memory that belongs to you.
Portable
On a memory platform, what it learned lives in that vendor’s database, under their user id. Leave, and it stays behind.
With K01 it lives at an ENS name you own, as objects on IPFS. Change assistants and the next one reads the same memory.
Versioned
A newer extraction quietly replaces an older one. There is no history to look at and nothing to undo.
With K01 every change is a commit. Earlier versions stay readable, and a wrong claim is reverted, not erased.
Yours to share
Another app can only get your memory as a copy, through an export and a re-import.
With K01 a second app reads the same name and the same version. For private memory, you grant it a key — and can take it back.
In one line
Their memory is persistent for the application. K01’s is persistent for you: it exists on its own, under your name, and applications read it.
Side by side
Two different approaches. Where memory platforms are stronger, the table says so.
| Question | Memory platformsMem0, Supermemory | K01 |
|---|---|---|
| Who it is for | Developers adding memory to their app. | People who own their memory, the agents that read and write it, and developers building on it. |
| Who the memory serves | The app. You are the subject of the record, not its owner. | You. Apps read and propose; the name is registered to your wallet. |
| Can you see what is held | Only if the app builds a way to show you. | Yes — every claim, its source and its history, at your name. |
| How fast it saves | Milliseconds. | Milliseconds on your machine; published to your name on a schedule you set. |
| Where it lives | The vendor’s database. | An ENS name you own, with its versions on IPFS. |
| What is stored | Snippets of text with tags and a date. | Claims, each with its sources, who added it, who checked it, and a version. |
| Who else can read it | The app, through their API. | Any agent you allow — anyone for public memory, key holders for private. |
| Can you take it with you | Export it, then import it somewhere else as new text. | It is already yours. Same name, same history, next assistant. |
| When facts conflict | The newest one wins, silently. | Flagged. On your own memory the newest wins and it is noted; on shared memory a reviewer decides. |
| Two sources agree | Two entries, or a merge you can’t inspect. | One claim, both sources listed, and higher confidence. |
| Review | None. | Your choice per namespace: instant for personal memory, reviewed for shared knowledge. |
| Shared knowledge | Not covered. | The same building block: cancer-research.eth or conventions.acme.eth, owned by others, read by your agent. |
| Search quality | Strong: embeddings, graph memory, tuning. | Simpler keyword search by topic and subject; a vector index can sit underneath. |
| Setup | An API key. | An ENS name and one connected app. A few more steps, because you end up owning it. |