Catalog Systems Framework-embedded memory CrewAI Memory

CrewAI Memory

https://www.crewai.com/

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

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

At a glance

Type
Short-term + long-term + entity vendor fix
Tier
T2
Section
Framework-embedded memory
Created
2023-10 vendor fix
Latest release
v1.15.28 (2026-10-14) registry fix
License
MIT repo fix
GitHub
50.7k★ +1.6k/mo Python repo fix
Pricing
Free + paid vendor fix
Funding
$36M total Series A · 2024-10 third-party 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
SDK languages
python repo fix
Protocols
a2a, mcp-client repo fix

Memory taxonomy

storage
vector
retrieval
similarity
persistence
long-term
update
extraction
unit
episode
governance
inspectable
conflict
llm-arbitrate

When to use

Optimised for: multi-agent orchestration with built-in memory tiers

Anti-fit: not for non-CrewAI stacks

Pros & cons

Pros

Memory tuned for multi-agent crews — handles per-agent and shared-crew memory cleanly.

Cons

Crew-specific framing; less idiomatic for single-agent designs.

Claims & capabilities

CrewAI raised $18M; reports use by ~60% of Fortune 500 companies; v0.28 (December 2025) added improved memory management. Short-term memory backed by ChromaDB + RAG; long-term + entity memory layers built in. Mature multi-agent ecosystem

Technical surface

API surface
SDK: Python (ShortTermMemory / LongTermMemory / EntityMemory)
Backend storage
pluggable (ChromaDB default)
Deployment
Both
Embedding model
multiple supported
Multi-tenancy
not applicable — library; namespace via crew/agent IDs
MCP
via official adapter — crewai-tools MCP
A2A
searched not found
OpenTelemetry
via adapter — AgentOps + OTel

Alternatives to CrewAI Memory → live options ranked by shared design, licence, hosting and MCP support

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.

  • 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 (54 cited facts, 5 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
    • Latest release “1.14.4 2026-04-30” → “v1.15.28 (2026-10-14)” source
    #195

Related systems

References (3)

  • Chroma depends on at runtime — backend-storage cell: pluggable (ChromaDB default)
  • LanceDB integrates with — CrewAI memory docs say memory is stored in LanceDB by default. (verified 2026-10-29)
  • Mem0 integrates with · depends on at runtime — Memory subsystem inside the CrewAI orchestration framework; integrates with Mem0 for the long-term tier.

Referenced by (1)