Langflow Memory

https://docs.langflow.org/memory

Agent component has built-in chat memory enabled by default, keyed by session ID. Custom session IDs isolate per-user history. Bundled Mem0 + Redis integrations for external memory layers.

Acquired. acquired by DataStax Source · Alternatives and migration notes →

Acquired · Verified 2026-10-22 · fresh as of 2026-10-22 · 59 cited facts, 12 with a third-party source · 2 recorded changes · Suggest a correction

At a glance

Tier
T1
Latest release
v1.11.4 (2026-08-19) repo fix
License
MIT repo fix
Freshness
2026-10-22 fix
Layer
agent-infra repo fix
Licensing
open-source vendor fix
Deployment locus
local vendor fix
Platform vs product
platform vendor fix
Maturity
ga registry fix
SDK languages
python, rest, typescript vendor fix

Memory taxonomy

storage
relational
retrieval
injection
persistence
cross-session
update
append-only
unit
episode
governance
inspectable
conflict
append-only

When to use

Optimised for: visual flow building + Mem0/Redis integrations

Anti-fit: not for code-first only stacks

Pros & cons

Pros

Strong DataStax / Astra DB integration gives it a managed-database memory backend out of the box.

Cons

Visual-builder positioning competes with Flowise without a clear differentiator on memory specifically.

Claims & capabilities

Open source. Cloud free tier.

Technical surface

API surface
REST + Python SDK; MCP server endpoint
Backend storage
pluggable
Deployment
OSS self-hosted (all major clouds); DataStax cloud deprecated; IBM acquisition path unclear
Embedding model
multiple supported
Multi-tenancy
namespace
MCP
native (first-party) — Langflow MCP server
A2A
searched not found
OpenTelemetry
via adapter — LangSmith / Arize

Compare Langflow Memory 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.

  • LangGraph Persistence T2

    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.

  • 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.

Sources (58 cited facts, 12 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-23
    • Pricing “OSS free (MIT); DataStax Langflow cloud was free tier + paid; DataStax cloud deprecated Mar 2026. Self-host infra: …” → “OSS free (MIT); DataStax Langflow cloud was free tier + paid” source
    • Funding / ownership “Acquired by DataStax Apr 2024; DataStax being acquired by IBM (announced Feb 2025); Langflow original company (Logs…” → “Acquired by DataStax Apr 2024; DataStax being acquired by IBM (announced Feb 2025)” source
    #223
  2. 2026-10-22
    • License “not applicable — not OSS” → “MIT” source
    • Latest release “not applicable — not OSS” → “v1.11.4 (2026-08-19)” source
    #195

Related systems

References (1)

  • Mem0 integrates with — Bundled Mem0 + Redis integrations for external memory layers.