Interactive architecture workspace

Your AI agent needs memory. Your company needs an exit strategy.

Choose the architecture before the product. The advisor separates hard constraints from preferences, keeps a no-system outcome available, and returns a recommendation you can take into a real design discussion.

Read the research

Research snapshot: 2026-08-11 / 17 representative systems / no accounts or tracking

The premise

The product is downstream of the architecture.

First decide what must persist, who owns the meaningful state, which portability layer matters, and what the team can operate. Only then compare implementations.

01

Hard constraints first

Self-hosting, deletion, tenancy, licensing, model dependency, runtime fit, and recovery can eliminate a candidate.

02

Canonical state stays yours

Operational memory can be derived and replaceable. Organization-owned facts, records, and decisions should remain recoverable elsewhere.

03

Evidence stays dated

Current documentation, independent research, benchmark claims, and untested behavior are different evidence levels.

Decide

What are you actually trying to remember?

The path is adaptive. It does not end at a product category. It keeps asking the cross-cutting questions that make a production decision defensible.

What to expect

Five adaptive phases · browser-local · no account

Your answers stay in this browser. Shared links contain only allowlisted question and option identifiers, never free text or names.

The map

Eight architecture outcomes. One cross-cutting ownership rule.

The visual map is the fast orientation. The workspace applies deployment, governance, portability, and evidence constraints to the same family records.

01

Architecture first

What must remain useful when the current agent disappears?

02

No dedicated memory system

Are stable records and ordinary retrieval enough?

The durable facts already belong in Git, ADRs, an application database, or ordinary search.

First systems to evaluate
Existing source of truth + search
03

Developer operational memory

Does engineering work need continuity across tools and sessions?

Coding agents need lessons, decisions, fixes, and project context across sessions.

First systems to evaluate
AgentMemoryGBrainMemorix
04

Application and user memory

Must a product remember people, preferences, and recurring context?

A customer-facing or internal application needs persistent user, session, or agent context.

First systems to evaluate
Mem0SupermemoryMemobaseMemMachineHoncho
05

Temporal context graph

Do relationships change over time and need provenance?

The agent must answer what was true, when it was true, what superseded it, and which source produced it.

First systems to evaluate
GraphitiZep
06

Enterprise knowledge memory

Is the hard problem connecting heterogeneous organizational knowledge?

Documents, entities, workflows, and domain ontologies must become connected, queryable context.

First systems to evaluate
CogneeGBrainSupermemory
07

Reflective learning memory

Must the agent consolidate experience into lessons or mental models?

The agent should retain, reflect on, and improve from prior experience.

First systems to evaluate
Hindsight
08

Stateful agent runtime

Should the runtime itself own the agent's durable state?

A long-running agent needs a runtime-managed identity, memory hierarchy, or framework-native store.

First systems to evaluate
LettaLangMemMemOSOptMem
09

Canonical sovereign knowledge

Must the organization own the meaningful state independently of the memory engine?

Portability, auditability, and long-term ownership dominate automatic memory formation.

First systems to evaluate
GBrainExisting source of truth + searchMemorix
ALL

Canonical state stays yours. Derived memory may accelerate an agent, but it should not be the only copy of meaning.

Accessible decision map

Architecture families and their first evaluation candidates

Use the guided advisor for the complete adaptive path. This list exposes the same branches without relying on the visual map.

  1. No dedicated memory system

    Decisive question: Are stable records and ordinary retrieval enough?

    The durable facts already belong in Git, ADRs, an application database, or ordinary search.

    First systems to evaluate: Existing source of truth + search

  2. Developer operational memory

    Decisive question: Does engineering work need continuity across tools and sessions?

    Coding agents need lessons, decisions, fixes, and project context across sessions.

    First systems to evaluate: AgentMemory, GBrain, Memorix

  3. Application and user memory

    Decisive question: Must a product remember people, preferences, and recurring context?

    A customer-facing or internal application needs persistent user, session, or agent context.

    First systems to evaluate: Mem0, Supermemory, Memobase, MemMachine, Honcho

  4. Temporal context graph

    Decisive question: Do relationships change over time and need provenance?

    The agent must answer what was true, when it was true, what superseded it, and which source produced it.

    First systems to evaluate: Graphiti, Zep

  5. Enterprise knowledge memory

    Decisive question: Is the hard problem connecting heterogeneous organizational knowledge?

    Documents, entities, workflows, and domain ontologies must become connected, queryable context.

    First systems to evaluate: Cognee, GBrain, Supermemory

  6. Reflective learning memory

    Decisive question: Must the agent consolidate experience into lessons or mental models?

    The agent should retain, reflect on, and improve from prior experience.

    First systems to evaluate: Hindsight

  7. Stateful agent runtime

    Decisive question: Should the runtime itself own the agent's durable state?

    A long-running agent needs a runtime-managed identity, memory hierarchy, or framework-native store.

    First systems to evaluate: Letta, LangMem, MemOS, OptMem

  8. Canonical sovereign knowledge

    Decisive question: Must the organization own the meaningful state independently of the memory engine?

    Portability, auditability, and long-term ownership dominate automatic memory formation.

    First systems to evaluate: GBrain, Existing source of truth + search, Memorix

Cross-cutting rule: keep organization-owned canonical state outside the operational memory product.