What "owning" your AI memory actually means.
You hold the file
Your persona is a signed .person.json in a git repo you own. Your corpus is a local SQLite database. There is no version of you living only on our servers — because by default there is no version of you on our servers at all.
It's the same AI everywhere
One persona, projected into every tool you open — 13 editors over MCP and 21 cloud chat surfaces over the extension. Not four copies drifting apart. One memory, present at once.
Leaving is a feature, not a fight
Export the whole corpus to Obsidian-ready markdown any time. Signed snapshots round-trip byte-for-byte. The format is open and the relay is self-hostable. You are never locked in — which is the whole point.
Renting vs. owning
The difference between a memory a vendor keeps and a memory you hold.
Renting (vendor memory)
- Lives on the vendor's servers, in the vendor's format.
- Works in one app only.
- Travels as a lossy, one-time copy — if at all.
- Models the AI as a generic tool; the character is theirs.
- Ends when your subscription, or their terms, end.
Owning (aiperson)
- Lives in a file you hold — your git repo, your machine.
- Present across 30+ AI surfaces at once, including local models.
- Already there — nothing to migrate when you switch.
- Carries the persona: voice, conventions, refusals, history.
- Yours to keep, export, and self-host — forever.
The AI you've shaped should be yours to keep.
Two commands, no credit card. Free while we build toward our first 100 Founding Members.