LangGraph Persistence

https://docs.langchain.com/oss/python/langgraph/persistence

Distinct from LangMem. Built-in checkpointer saves graph state per super-step (short-term, thread-scoped). Store System adds long-term hierarchical key-value memory across threads with optional vector search + TTL. Postgres / Mongo / Redis stores for production.

Active · Verified 2026-10-22 · fresh as of 2026-10-22 · 62 cited facts, 20 with a third-party source · 1 recorded change · Suggest a correction

At a glance

Tier
T2
Latest release
langgraph v1.2.16 (2026-10-16) registry fix
License
MIT registry fix
Freshness
2026-10-22 fix
Layer
agent-infra repo fix
Licensing
open-core vendor fix
Deployment locus
hybrid vendor fix
Platform vs product
platform vendor fix
Maturity
ga registry fix
SDK languages
python, typescript repo fix

Memory taxonomy

storage
relational
retrieval
exact-match
persistence
cross-session
update
overwrite
unit
episode
governance
inspectable
conflict
last-write-wins

When to use

Optimised for: durable graph-state checkpointing + Store System for cross-thread memory

Anti-fit: not for non-LangGraph workflows

Pros & cons

Pros

Persistent state for graph agents — checkpointing and resumability are first-class, not bolted on.

Cons

LangGraph-shaped; persistence model is general but most idiomatic when paired with LangChain memory.

Claims & capabilities

Checkpointer saves graph state at every superstep enabling memory between interactions, human-in-the-loop, and fault tolerance. Multiple backends: MemorySaver (in-memory), PostgresSaver, AsyncPostgresSaver, langgraph-checkpoint-redis (Redis integration). Part of LangChain ecosystem ($160M Series B, $1.2B valuation, October 2025)

Technical surface

API surface
SDK: Python, JS/TS
Backend storage
pluggable (Postgres, SQLite, Redis)
Deployment
Both (LangGraph OSS self-hosted; LangSmith Deployment cloud managed or self-hosted)
Embedding model
multiple supported
Multi-tenancy
not applicable — library; namespace is (thread_id, checkpoint_ns); hosted LangGraph Cloud runs in Anthropic-managed VPC
MCP
yes — Agent Server exposes deployed graphs as MCP tools at /mcp (streamable HTTP); MCP client via langchain[mcp] adapter
A2A
supported — LangGraph A2A wrappers
OpenTelemetry
first-class — LangSmith + OTel

Compare LangGraph Persistence with…

Similar systems

Other framework-embedded memory in the catalog, ranked by inbound references.

  • Spring AI ChatMemory T3

    Wraps conversation memory behind an Advisor abstraction. MessageWindowChatMemory default 20-msg sliding window (preserves system messages); pluggable ChatMemoryRepository backends (in-memory, JDBC, Cassandra, Neo4j). Memory injected as cross-cutting concern at the ChatClient level.

  • Flowise Memory T1

    Discontinued: Flowise (acquired by Workday, Aug 2025) was sunset in 2026 — code freeze 2026-07-29, GitHub repo archived 2026-08-13, end of life 2026-08-31. Was a visual LangChain canvas with LangChain-native memory nodes (Buffer, Buffer Window, Conversation Summary Buffer) backed by an internal chat_message DB table; Buffer Window kept the last K interactions, Summary Buffer compressed older turns while keeping recent ones verbatim.

  • AutoGen Memory T2

    AutoGen's memory layer: ListMemory chronological context plus teachable agents that vectorise corrections; integrates with Mem0/Zep rather than building deep memory natively. Microsoft AutoGen is in maintenance mode (community managed, bug and security fixes only), and Microsoft points new projects to Microsoft Agent Framework.

  • CrewAI Memory T2

    Memory subsystem inside the CrewAI orchestration framework; integrates with Mem0 for the long-term tier.

  • Hermes Agent memory (Nous Research) T3

    Nous Research's open-source self-improving agent keeps an agent-curated MEMORY.md/USER.md notebook injected at session start, full-text (FTS5) search over past sessions that returns raw messages without LLM summarisation, and optional Honcho user modelling. one of the most-starred agent projects of 2026.

  • Semantic Kernel Memory T2

    Microsoft Semantic Kernel's memory plugin (Microsoft.SemanticKernel.Plugins.Memory): a plug-in approach to long-term memory in the SK agent framework (agent memory marked experimental). Semantic Kernel's README names Microsoft Agent Framework 1.0 as its enterprise-ready successor, with a migration guide.

Sources (61 cited facts, 20 third-party)

Each fact links to the page it came from; the badge says who published it (how to read sources).

What changed

Changes to this record's lifecycle, licence, release, pricing and hosting facts, from the catalog's git history. Subscribe (Atom)

  1. 2026-10-22
    • License “not applicable — not OSS” → “MIT” source
    • Latest release “not applicable — not OSS” → “langgraph v1.2.16 (2026-10-16)” source
    • Pricing “OSS free (MIT); LangGraph Platform (now LangSmith Deployment as of Oct 2025): Free Developer plan 100k nodes/mo; Pl…” → “OSS free (MIT); LangSmith Developer $0 (5k traces/mo, 1 seat); Plus $39/seat/mo (1 free small serverless deployment); deployments metered at $1/LSU by compute+memory; Enterprise custom” source
    • Funding / ownership “$160M total (LangChain parent); $1.2B valuation; Series B Oct 2025” → “LangChain parent: $125M Series B at $1.25B valuation (2025-10); total not stated” source
    • MCP support “via official adapter — LangChain MCP adapters” → “yes — Agent Server exposes deployed graphs as MCP tools at /mcp (streamable HTTP); MCP client via langchain[mcp] adapter” source
    #219

Related systems

References (2)

Referenced by (6)