Developers

Build on memory
that you don't own.

Your user's. It lives on their machine, it's encrypted, and they govern it — including against you. That's the constraint, and it's what makes everything else possible.

Your own code

Point it at your project. It takes on its memory.

Declare your repo folder: Mnemosyne vectorizes your code — the files, the docs, your working conversations — and doesn't stop at search. Its consolidation turns it into a synthesized memory of the project: its architecture, the decisions you made, and why.

It's not a search engine handing you a line. You ask "why did we choose this?" and you get the synthesis — across months of work, without the right keyword. All local: your code never leaves your machine.

Get started

The shortest path, by surface.

MCP — zero lines of code

Infinity open, Node 18+, then in your project's .mcp.json:

{ "mcpServers": { "mnemosyne": {
  "command": "npx",
  "args": ["-y", "@mnemosyne_os/mcp"],
  "env": { "MNEMO_DEFAULT_VAULT": "DEV" }
} } }

App Layer 2

pnpm add @mnemosyne_os/sdk

import { MnemoClientBrowser } from '@mnemosyne_os/sdk';

const client = await MnemoClientBrowser.connect();  // 127.0.0.1:7799
await client.register(MANIFEST);                    // the user grants, or refuses
await client.ingest('A note to remember', 'NOTE', 'DEV');
const chronicles = await client.query('my search', 'DEV', 10);

Cartridge

Copy apps/mnemo-cartridge-boilerplate/, replace the workspace:* dependency with the npm version, then:

pnpm add @mnemosyne_os/cartridge-sdk
pnpm dev     # vite, 127.0.0.1:5185
pnpm build   # tsc && vite build -> dist/

In the app: MnemoHub → My dev apps → link your folder. The first link is free; the second requires an active Engramm license — better you learn it here than in the middle of your integration.

Soon · the creator economy

An economy where the creator keeps the biggest share.

When the store economy opens, the rule will be simple and public: the developer keeps 80% of every sale, the hub takes 15%, and 5% funds a community DAO that gives back to the ecosystem's development. No hidden cut, no terms that shift.

The rest — how it works, when it opens — is coming. Leave your email and be first to know. Zero spam, just the announcement.

Keep me posted

The contract

Memory perceives, situates and reveals.
The human governs.

For you, developer, it comes down to one sentence: your app can propose, the user decides. It erases nothing in silence, it mixes nothing without a human gesture, and it leaves its vault only if invited. Build with that, not against it.

How do you build?