StackMap
Subscribe

MemOS alternatives

Curated alternatives to MemOS — and why you'd switch.

hindsight

Agent memory that learns, not just recalls: retain/recall/reflect API over Postgres, SOTA on LongMemEval. Self-host via Docker with UI; Python/TS clients, any LLM provider.

Why switchBoth are self-hostable agent-memory services chasing LongMemEval and LoCoMo. hindsight is a lean retain/recall/reflect API on Postgres; MemOS is a broader stack (Neo4j + Qdrant, memory cubes, skill evolution).
Full comparison →
MemMachine

Long-term memory layer for AI agents — episodic (graph), profile (SQL) and working memory behind Python/TS SDKs, REST and MCP; ships LangChain, LangGraph, CrewAI and LlamaIndex integrations.

Why switchSame job — long-term agent memory behind SDKs, REST and MCP with graph-backed episodic storage. memmachine ships framework integrations (LangGraph, CrewAI); MemOS adds memory cubes and harness plugins.
Full comparison →
OpenViking

Volcengine's context database: memories, resources and skills as one `viking://` filesystem agents ls, tree and grep — L0/L1/L2 tiers, traceable retrieval, sessions distilled into memory.

Why switchBoth unify memories, resources and skills for agents and distill sessions into long-term memory. OpenViking exposes it as a viking:// filesystem; MemOS as a graph-structured memory API.
Full comparison →
memory-os

A 7-layer memory operating system for Hermes Agent: Qdrant vectors, structured facts, fabric recall, an auto-curated wiki, and surgical context injection.

Why switchBoth pitch a layered 'memory OS' with a Hermes Agent integration — memory-os is a 7-layer Qdrant stack built for Hermes, MemOS a multi-harness core with local SQLite plugins.
Full comparison →