Part 5 - You Can Leave With Everything

The memory business has a quiet incentive problem. The more you tell a memory product, the harder it is to leave it, and that lock-in is the business model. Your accumulated context is the asset. The vendor holds it. You rent access to your own history.

I built MrAgentˣ to make that incentive impossible to act on.

The situation that forced it was simple. I was going to pour a year of decisions, client history, and hard-won mistakes into a memory layer. The only question that mattered was: whose is it when I stop paying? With every tool I looked at, the honest answer was "theirs, with an export button that gives you a fraction back."

The rabbit hole was trust language. Privacy pages, data-processing agreements, promises not to train on your content. Promises are a read-path feature. They can be revised. I wanted ownership that was true by construction.

So the atoms live in your own database project, not in a shared vendor pool. Reasoning routes through APIs that do not train on the content. The vendor never accumulates your alpha, because the vendor never holds it in a form it could accumulate. Full workspace export is live in production: queued, metered, delivered as a signed download of everything. You can leave with all of it, and I built the leaving before I built most of the staying.

Ownership without encryption is a promise with extra steps, so the content is encrypted with a key the database itself cannot read: a per-workspace key derived from a master secret the database never sees, non-extractable, rotation-ready. And the search was designed to work over the encrypted content, so nothing is decrypted on the retrieval path. Of the memory products I have verified, none can search its content without decrypting it first.

One fewer party touches it, too. Embeddings, the step where most products quietly ship your text to a third-party vendor, run on owned infrastructure with a version-pinned model, fail-closed authentication, and live-tested outage alerting.

Boundaries are enforced at the database layer, on every query, not by application politeness. A workspace cannot see another workspace because the database will not answer, not because the app was polite enough not to ask.

And the asymmetry runs in your favour. What you mark confidential stays fully visible to your own sessions and is omitted from every export and copy surface, so the sensitive parts of your map are the parts that never leave. When you delete a source email to control storage, the raw document is archived but the atoms extracted from it stay by default. Delete the storage, keep the knowledge.

The test I use for every ownership decision is the exit test. If a user leaves tomorrow, what do they take, and what did they give up? With MrAgentˣ the answer is: everything, and nothing. That is not a feature. It is the reason the product is allowed to exist.

Context Windows Close. AI Forgets Everything. Your Work Should Never Start From Zero.

MrAgentˣ is in private beta. Limited to the first 1,000 until launch.