Perspective
Why your AI's memory shouldn't live inside your AI
The case for separating what you know from the tool that reads it — and why every assistant should be a renter, not a landlord.
The tool-agnostic context vault
Own your context.
Own your context.
Swap AI tools freely.
AI assistants change every month — your knowledge shouldn't have to move with them. Geode keeps your context, workflows and connections in one vault that every AI client plugs into through a single endpoint.
Open-source/
Self-hostable/
Your model, local or cloud/
Built on MCP
Connects to
Claude
OpenClaw
Hermes
ChatGPT
Cursor
VS Code
JetBrains
and any MCP client →
The problem
Your AI knows you today.
Your AI knows you today.
Next month, you start over.
You spend months teaching an assistant how you work — your projects, clients, conventions, hard-won shortcuts. Then a better tool drops, and it knows none of it. So you either stay put, or start cold. Either way, the tool is holding you hostage — and every assistant you add keeps its own drifting half-copy of who you are.
Without Geode
fragmented
With Geode
one source
Without Geode — fragmented
- × Re-teach every new assistant from scratch
- × Four tools, four half-stale copies of your context
- × A client preference one tool knows, the others don't
- × Switching tools resets you to zero
With Geode — one source
- ✓ Connect a new tool, it inherits everything
- ✓ One vault, read by every assistant at once
- ✓ Update a fact once — every tool sees it
- ✓ Switch tools and lose nothing. It compounds
The solution
One vault. Every tool. Zero migration.
Geode is the durable layer underneath the churning AI ecosystem. Your context lives in a vault you own, reachable through one universal MCP endpoint — so every client, today's and next year's, draws from the same source the moment you connect it.
The agent in the middle
It prepares. You stay in control.
Ask in plain language. The vault's agent reasons over your files, recipes and SOPs and returns a synthesized answer — or a ready-to-run plan with the exact steps to execute. It looks things up and tells you how; your tools do the executing. A consequence of that boundary: the agent never needs your secrets.
› query "how do I onboard a new client?" synthesized from your vault · playbooks/client-onboarding.md · integrations/notion, integrations/gmail plan (you execute via invoke) 1. invoke notion.create_page ← "Acme · Onboarding" 2. invoke gmail.send ← welcome + intake 3. remember ← "Acme: net-30, 1st" // the vault prepares. your tool runs it. secrets never seen.
01 Tool-agnostic by design
Connect any MCP client and it instantly inherits everything you've built. Switch whenever you want; your knowledge never moves and never resets to zero.
02 One source, all your tools
Stop maintaining four drifting copies of yourself. Save a fact once and every connected assistant sees it — no more re-explaining your conventions to each new tool.
03 Your keys never touch the AI
The agent only plans — it never needs a credential. Secrets stay in an encrypted, server-side broker, injected only at execution. The model that reads your context never sees a token.
04 It compounds
Every interaction enriches the vault. The longer you use Geode, the more valuable it gets — and that value follows you across every tool change, not into the trash.
Inside your vault
Plain markdown, woven into a graph.
No proprietary database. Your context is human-readable files in the vendor-neutral Open Knowledge Format — one concept per file, linked to the others. The agent walks the graph; you can read it in any editor.
- Markdown + frontmatter — one concept per file, your identity in the path.
- Linked concepts — canonical facts referenced, never copied.
- Git-versioned — every change is a commit; nothing is ever lost.
How it works
From zero to connected in three steps.
1
Spin up your vault
Self-host the open-source kernel over a git-backed folder. One command, one endpoint, one token.
$ npm start
› geode vault live on :8787
mcp endpoint ready
2
Connect your tools
Point Claude Code, Cursor, ChatGPT or any MCP client at your endpoint. They all share the same context instantly.
Claude Code connected
Cursor connected
+ add a client
3
Ask, save, build
query for answers and runnable plans. remember new facts in a sentence — the agent files and dedups them.
query "what's our refund policy?"
› synthesized from vault ✓
remember "Acme renews in Q3"
Built in the open
Trust isn't claimed. It's verifiable.
The whole promise is that you own your context and can walk away any time. A closed black box would just move the lock-in up one layer — so we don't ship one.
“The vault is the constant; the AI front-ends are interchangeable. You never reinvent the wheel when a new tool appears.”
— Geode design principle
100% open-sourceThe full kernel. Read it, run it, fork it.
Self-hostableYour server, your data. Nothing leaves.
Open MCP standardNo proprietary protocol to bet on.
Vendor-neutral formatPlain markdown (OKF) in your git repo.
Bring your own modelLocal (Ollama) or cloud (Claude, GPT…).
Pricing
Free to own. Pay only to never run it yourself.
Open-core. The kernel is free forever — that's the part that proves the promise. You pay for what's genuinely hard to self-host: collaboration, governance and managed privacy.
Self-Host
For individuals & developers. Your vault, your box.
$0
- ✓ The full open-source kernel
- ✓ Unlimited context & connections
- ✓ Local or cloud model
- ✓ Single-tenant, no accounts
Most popular
Team
For teams that share a vault and need governance.
Coming · join waitlist
- ✓ Shared vaults with inheritance
- ✓ Roles, audit logs & SSO
- ✓ Maintained integration library
- ✓ Managed, monitored, zero ops
Private Managed
For regulated & security-first organisations.
Talk · to us
- ✓ Isolated instance, per customer
- ✓ Local-model add-on — nothing leaves
- ✓ Hardened secret isolation
- ✓ Compliance & egress controls
Honest note: the hosted tiers are in build — today the self-host kernel is the real, shippable product.
Questions
The things people ask first.
How is this different from my assistant's built-in memory?
Built-in memory lives inside one tool and dies when you leave it. Geode lives outside every tool — switch assistants and your context comes with you, because it was never inside the assistant to begin with.
Which AI tools does it work with?
Anything that speaks MCP — Claude Code, Cursor, ChatGPT and a growing list of clients. You connect them all to one endpoint; they all share one vault.
Do I have to trust you with my data?
No. The kernel is open-source and self-hostable — your vault is a git-backed folder on your infrastructure. Want us to host it later? That's opt-in, isolated per customer, with a local-model option so nothing leaves your environment.
Will the AI model see my API keys and secrets?
Never. The agent only plans — it doesn't execute external actions, so it never needs a credential. Secrets sit in an encrypted broker and are injected server-side only at execution time.
What if I get locked into Geode itself?
You're not. Your vault is plain markdown in the vendor-neutral
Open Knowledge Format, in your own git repo. No proprietary database, no SDK lock-in. Walk away with everything, any time.Is it ready to use right now?
The self-hostable kernel is here today —
query, remember and list_capabilities over your vault. Integration execution (invoke), the dashboard and the hosted tiers are on the roadmap.
Field notes
Read all field notes
Ideas worth keeping.
Notes on owning your context, the MCP ecosystem, and building AI workflows that outlive any single tool.
Standards
OKF: a context vault you can actually read
How the Open Knowledge Format turns your context into plain, linkable markdown — no SDK, no registry, no lock-in.
Engineering
The agent that plans but never executes
Why drawing a hard line between preparing a plan and running it makes secrets trivial to protect — and keeps the vault a specialist, not a rival.