Bourdon is cross-agent memory federation: a recognition-first runtime that lets Claude Code, Codex, Cursor, and your own agents share one memory, and recognize each other's work, instead of each keeping a private, siloed store. Self-hosting is free and forever; managed hosting is the convenience layer on top.
Jump to: Quickstart · Self-host · Hosted · Enterprise · What you pay for
Quickstart
You need Python 3.12+ (or Docker). Self-hosting is the real path and it's live today, everything below works right now.
1, Install
pip install bourdon
# or run the container: docker run --rm getbourdon/bourdon serve
2, Serve the memory runtime
bourdon serve
Binds to 127.0.0.1 by default. To share across your tailnet, bind your tailnet address (bourdon serve --host 100.x.y.z) with a per-agent token, non-loopback binds refuse to start without auth, by design.
3, Connect an agent
Bourdon ships adapters for Claude Code, Codex, Cursor, and more, plus a convention-file path any agent can self-author. Point your agent's MCP config at the running server, or install the participant for its runtime. Every agent that connects publishes to, and recognizes from, the same federated memory.
4, See federation work
bourdon agents --federated # who's in the federation, across machines
bourdon doctor # health of the local store + peers
The moment a second agent connects, the first one recognizes the shared work, recognition fires before the details are hydrated. That cross-tool recognition is the thing nothing else in the category does.
Self-host (free)
The full engine, forever, nothing held back. Self-hosting is the default and the hero. You get the entire runtime: recognition-first retrieval, the tiered memory stack (L0–L6), and, critically, cross-agent federation included. There is no feature that only the paid tier unlocks; the engine is identical whether you self-host or we host it for you.
bourdon serveon your own box or tailnet- Per-agent token auth, trust tiers, quarantined adapters, append-only audit
- Fly.io / Docker / Compose templates in the repo
- Source-available (BSL 1.1 → Apache 2.0 after 4 years); free for solo developers, research, and non-competing commercial use
Federation is never gated. Cross-agent memory is the product, not an upsell, it's here at the free tier and stays here.
Hosted (coming)
Prefer not to run a box? Managed Bourdon is landing soon. The free→paid line is operations, never engine capability, you pay for always-on uptime, backups, per-tenant isolation, and an SLA, not for features you'd otherwise be missing.
| Tier | Price | For |
|---|---|---|
| Free hosted | $0, no card | Onboards without the ops burden, a few agents, one peer, capped by volume |
| Developer | ~$12–15/mo | The solo dev who's outgrown free, more agents, more writes, always-on |
| Team | ~$29–49/mo | Shared namespace, multi-seat, federation + graph memory included |
| Growth | ~$79–99/mo | Higher volume, analytics, priority support |
Prices are provisional until the hosted tier opens. Billing follows memory operations (writes + recalls), never per-seat. Join the hosting list →
Enterprise (coming)
SSO / SAML, BYOC / BYOK, long audit-retention, HIPAA BAA, dedicated support. Built on the same self-hostable core, so a compliance review can always run against infrastructure you control. Talk to us →
What you pay for
Bourdon's self-hosted edition is not a lesser version, it's the whole thing, and we're keeping it that way (no deprecated community edition). What managed hosting sells is convenience: uptime, backups, isolation, and support. Some teams want to run it themselves; some would rather pay us to. Both are first-class.
Family
Bourdon is one half of a fleet OS: it's what the fleet knows. Its sibling, Positif, is what the fleet is allowed to do, cross-agent governed routing with a full audit trail. Memory + governed routing for self-sovereign agent fleets.