ai-memory architectures

A primitive that scales from one agent on a laptop to a global hive of millions. Every tier ships either today, or sits behind a documented gap with a known roadmap. Nothing on this page is marketing fiction — every "today" claim cites code in the v0.7.0 source tree.

5 tiers T1–T3 ship today T4 SHIPPED v0.7.0 GA T5 vision · v1.0+
The five tiers

From single agent to global collective.

Each tier is a deployment pattern. Each inherits everything below it. Click a card for the full diagram, narrative, and deployment recipe.

TIER 1

Single node, single agent

One ai-memory instance, one consumer. SQLite, no network, zero ops. The bedrock primitive.

SCALE: 1 node · 1 agent · ~10⁶ memories SHIPS TODAY
TIER 2

Single node, many agents

One instance fanned across ~10 concurrent agents, each isolated by namespace + scope visibility, gated by per-namespace governance.

SCALE: 1 node · 10 agents · namespace-isolated SHIPS TODAY
TIER 3

Multi-node cluster

4 nodes × 5 agents with W-of-N quorum writes, mTLS fingerprint allowlist, federated governance, vector-clock catch-up — all shipping today.

SCALE: 4 nodes · 20 agents · quorum-bounded SHIPS TODAY
TIER 4

Data-center swarm

Multi-rack deployment with quorum writes shipping today; Postgres+pgvector backbone behind the sal-postgres feature flag, GA at v0.7.0.

SCALE: 100s nodes · 1000s agents · racked & zoned CORE TODAY PG GA · v0.7.0
TIER 5

Global hive

Multi-region cloud, attested agent identity, federated governance, hundreds of thousands to millions of agents acting as a unified collective.

SCALE: multi-region · 10⁵–10⁶ agents · attested VISION v1.0+
GRAND SLAM

3-region federated hive — proven live

The reference proof behind the T3–T5 claims: 15 nodes, 9 federated peers, W=2 quorum, three encryption legs each proven positive + negative, Batman MAXIMUM-SECURE posture (do-1461).

SCALE: 3 regions · 15 nodes · 119/119 verify ×2 clean-room rounds PROVEN LIVE
ENTERPRISE

CPU + Memory federated nodes

API embeddings (#1598) on commodity CPU nodes — OpenRouter gemini-embedding-2 cloud shape or self-hosted TEI/vLLM airgapped shape. No Ollama anywhere; full semantic/autonomous tier on GPU-free fleets.

SHAPE: federated mesh · API embeddings 80–300 ms · no GPU CORE TODAY · #1598
ENTERPRISE

CPU + Memory + GPU federated nodes

Local Ollama embeddings on GPU-equipped nodes (operator GPU policy), same hardened federation skeleton. Lowest embed latency, zero per-token cost, no embedding egress — includes the when-to-choose-which table.

SHAPE: federated mesh · localhost GPU embed 5–30 ms CORE TODAY · #1598
Capability matrix

What ships today vs. what's on the road.

The honest matrix. Cell colors match the badges above.

Capability T1 T2 T3 T4 T5
SQLite-backed store, FTS5 keyword recall YES YES YES → pgvector → pgvector
Semantic recall (HNSW, MiniLM 384-dim) YES YES per-node shared idx shared idx
Namespace isolation + scope visibility (as_agent) n/a YES YES YES YES
Per-namespace governance policy n/a YES YES YES YES
Pending-approval gates (write/promote/delete) n/a YES YES YES YES
Knowledge-graph w/ temporal validity (v0.6.3) YES YES YES YES YES
Hierarchical taxonomy (memory_get_taxonomy) YES YES YES YES YES
Capabilities introspection v2 (v0.6.3) YES YES YES YES YES
One-way sync_push fanout (memories, links, governance, pending) n/a n/a YES YES YES
Vector-clock causality (sync/since) n/a n/a YES YES YES
Quorum-write contract (W-of-N peer ack) n/a n/a YES YES YES
mTLS peer mesh + fingerprint allowlist n/a n/a YES YES YES
Postgres + pgvector backend feature flag feature flag feature flag GA · v0.7.0 GA · v0.7.0
Cryptographic agent attestation (Ed25519 signature, #626 Layer-3) YES YES YES YES hive scale · v1.0+
Distributed consensus (Raft / Paxos) v1.0+
Gossip / DHT for many-node discovery scoped required
Composition

Why a layered architecture story.

ai-memory is a primitive, not a platform. The same Rust binary, the same data model, the same MCP protocol surface scales from a developer's ~/.claude/ai-memory.db to a fleet running across racks. What changes between tiers:

What stays the same:

Every tier inherits everything below it.

Federation primitives

What lives in the codebase today.

These are the building blocks every multi-node tier composes. All shipped, all in v0.7.0:

How to read

Each tier page contains.

  1. An animated SVG diagram showing memory data flow — writes, recalls, peer sync, governance gates, and (where relevant) attestations.
  2. A "what's actually happening" narrative walking the reader through a recall and a write.
  3. Capability badges on every primitive — cyan ships today, orange partial, purple roadmap, pink future vision.
  4. A deployment recipe with real commands.
  5. Governance, skills, and attestations wiring for the tier — what enforces the rules at this scale.
  6. Honest limits — what would break, and at what scale.

Start at Tier 1 and walk forward, or jump straight to the tier that matches your fleet.

Engineering honesty. Every "ships today" claim cites a file path and behavior in the v0.7.0 source tree. Roadmap items reference ADRs and tracked work. The vision tier (T5) is the north star — we'll get there, but it's not shipping in v0.7.0. If a diagram shows something the code doesn't do, that's a documentation bug — please file an issue.