OpenMemory (now LongMemory)

https://github.com/CaviraOSS/LongMemory

Renamed LongMemory (repo CaviraOSS/LongMemory; packages longmemory / longmemory-sdk, with openmemory-js@2 / openmemory-py@2 as forwarding bridges). Open-source cognitive memory engine for LLMs and agents.

Renamed. now LongMemory Source · Alternatives and migration notes →

Renamed · Verified 2026-10-29 · fresh as of 2026-10-29 · 48 cited facts, 6 with a third-party source · 2 recorded changes · Suggest a correction

At a glance

Tier
T2
Created
2025-10 repo fix
License
Apache-2.0 repo fix
Funding
searched not found fix
Freshness
2026-10-29 fix
Layer
agent-infra repo fix
Licensing
open-source repo fix
Deployment locus
local repo fix
Platform vs product
platform repo fix
SDK languages
python, typescript repo fix
Protocols
mcp-server repo fix

Memory taxonomy

storage
vector
retrieval
similarity
persistence
long-term
update
extraction
unit
fact
governance
user-controllable
conflict
none

When to use

Optimised for: local-first / privacy-preserving

Anti-fit: no anti-fit explicitly stated

Pros & cons

Pros

Cross-tool memory protocol — designed to make memory portable between agents that today silo it.

Cons

Protocol adoption is early; ecosystem support outside Mem0 is thin.

Claims & capabilities

+165/mo; Apache-2.0; OpenMemory MCP first-party MCP server; v1.2.3 released 2025-12-12; self-hosted ~$5-8/mo for 100k memories vs $60-120 for SaaS

Technical surface

API surface
REST; OpenAI-compatible chat endpoint with embedded memory ops
Backend storage
hybrid (vector + graph)
Deployment
Self-hosted (local + Docker; no cloud service found)
Embedding model
multiple supported
Multi-tenancy
namespace
MCP
yes — built-in stdio MCP (longmemory mcp) and authenticated Streamable HTTP MCP
A2A
not documented publicly
OpenTelemetry
not documented publicly

Similar systems

Other dedicated memory layers in the catalog, ranked by inbound references.

  • Mem0 T1

    Universal memory layer for AI agents. Three concurrent stores (vector + graph + KV); LLM-extracted facts; concurrent retrieval via ThreadPoolExecutor.

  • Zep & Graphiti T1

    Bi-temporal knowledge graph (event time + ingestion time). Strong on chronological reasoning and contradiction tracking. Graphiti is the open-source core.

  • Cognee T1

    "Extract–Cognify–Load" pipeline that turns raw input into a typed, queryable knowledge graph for agent recall.

  • Hindsight (Vectorize) T1

    Standalone memory service from Vectorize. Open source. Biomimetic four-network design (World, Bank, Observation, Opinion). Ships an MCP memory server.

  • Letta / MemGPT T1

    Originated as MemGPT (UC Berkeley), where the model pages its own memory between context, recall and archival tiers. The product now centres on Letta Code, a stateful agent harness whose agents rewrite their own memory, skills and prompts over time.

  • Memori T2

    Structured, persistent memory layer for AI agents. Open source.

Sources (47 cited facts, 6 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
    • Name “OpenMemory” → “OpenMemory (now LongMemory)”
    • Homepage “https://github.com/CaviraOSS/OpenMemory” → “https://github.com/CaviraOSS/LongMemory”
    #223
  2. 2026-10-22
    • Latest release “v1.2.3 2025-12-12” → “v1.2.3 (2025-12-12); v1.3.0 beta pre-release (2025-12-20)” source
    • MCP support “native (first-party) — OpenMemory MCP” → “yes — built-in stdio MCP (longmemory mcp) and authenticated Streamable HTTP MCP” source
    #195

Related systems

References (1)

  • Qdrant depends on at runtime — adjacent-infrastructure cell: BYO LLM; self-hosted Postgres + Qdrant