MCP-native · Sovereign

The connecting layer between you and every model.

One memory store you own, reachable from any MCP client. Stateful, portable, sovereign — connect it in two lines.

# add Flow to your MCP client config, then:
flow save "we ship to prod on Fridays"
flow recall "deploy cadence"
# → we ship to prod on Fridays

Self-serve · open standard · export or delete anytime.

01   Why build on it

ChatGPTClaudeGeminiSoul file

No lock-in

Your memory is portable and exportable. Point it at a different model or client whenever you want.

Sovereign by default

The record plane is hosted in Sweden under an EU operator. Inference is swappable behind a gateway.

EraLayerCompanyOutcome
WebIdentityAuth0$6.5B
CloudPaymentsStripe$95B
AIMemoryPersistent Flow

Coming Soon

API access to our memory layer

Data Sovereignty

Your data. Your jurisdiction. Your rules.

Not a compromise. Not an upgrade tier. Sovereign by default — because your memory belongs under your flag, not theirs.

🇪🇺 EU Jurisdiction

Stored in Sweden — and the AI that reads it runs in Sweden too. Your memory sits outside the reach of the CLOUD Act, FISA, and every other alphabet soup that wants your data.

🔐 A key of your own

Every person and every workspace is encrypted under its own key. Delete, and that key is destroyed — the ciphertext left behind, backups included, is mathematically unrecoverable. Not a flag in a database.

📦 Always exportable

Export everything in open formats, any time. Delete everything, any time. No lock-in, no hostage data, no 'contact sales to leave.'

Platform, not a client

Build on the memory layer

We're infrastructure. Use our connectors, or build your own solutions on top. The memory layer works with everything.

Any MCP client — verified where we say so

Verified by us

Λ Claude
Claude Code

Speaks MCP — untested by us

ChatGPT
Mistral
Cursor
VS Code
Zed
Perplexity

Planned

Slack
Teams
WhatsApp
G Gemini
Notion
Salesforce
GitHub
Obsidian

Connected something we have not listed? Tell us and we will add it — with your name on it.

One URL, no SDK

Paste a single address into your assistant's connector settings and sign in. Nothing to install, nothing to configure, no code.

MCP-native

We speak the Model Context Protocol, so anything that speaks it can read and write your memory — including tools you build yourself.

That connecting layer doesn't exist yet. We're building it.