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.
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
- × 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
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.
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.
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.
From zero to connected in three steps.
Spin up your vault
Self-host the open-source kernel over a git-backed folder. One command, one endpoint, one token.
Connect your tools
Point Claude Code, Cursor, ChatGPT or any MCP client at your endpoint. They all share the same context instantly.
Ask, save, build
query for answers and runnable plans. remember new facts in a sentence — the agent files and dedups them.
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.
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.
- ✓ The full open-source kernel
- ✓ Unlimited context & connections
- ✓ Local or cloud model
- ✓ Single-tenant, no accounts
- ✓ Shared vaults with inheritance
- ✓ Roles, audit logs & SSO
- ✓ Maintained integration library
- ✓ Managed, monitored, zero ops
- ✓ 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.
The things people ask first.
How is this different from my assistant's built-in memory?
Which AI tools does it work with?
Do I have to trust you with my data?
Will the AI model see my API keys and secrets?
What if I get locked into Geode itself?
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?
query, remember and list_capabilities over your vault. Integration execution (invoke), the dashboard and the hosted tiers are on the roadmap.Ideas worth keeping.
Notes on owning your context, the MCP ecosystem, and building AI workflows that outlive any single tool.
10 Best Practices for Knowledge Management for Tech Teams
Discover 10 best practices for knowledge management for technical teams, from git-backed vaults and open standards to secure, agent-driven workflows.
Graph Databases: Power of Index Free Adjacency
Discover index free adjacency, the pointer-based architecture giving graph databases their speed. Understand how this core concept powers AI agent performance.
Best API Integration Platforms 2026
Compare top API integration platforms for 2026. Explore iPaaS, workflow engines & SDKs. Review capabilities, pricing & security to pick your ideal tool.