Back to Gap Map Organization

Mem0

company · United States

Scores

1 product on the map — 1 open.

Mem0

Openness

4 high confidence
4.0
license
Apache-2.0 (mem0 Python library, mem0-ts TypeScript SDK and self-hosted server)
source
public
core features withheld
yes — graph memory, memory decay, temporal reasoning and Dream consolidation exist only in the hosted Mem0 Platform, and the open SDK raises "not supported by the OSS Memory SDK" for decay, timestamp and reference_date; the 1,844-path tree at fff8a64 has no ee/ or enterprise/ path, because the withheld features are not shipped at all
commercial
Mem0-Platform (hosted service with graph memory, decay, temporal reasoning, Dream, webhooks and org and project scoping)

Mem0's memory library, TypeScript SDK and self-hosted server are published under Apache-2.0 and run without a Mem0 account. Several memory features exist only in the hosted Mem0 Platform, though: the entity graph, decay of stale memories, temporal reasoning and Dream background consolidation, and the open SDK returns an error when asked for decay or temporal parameters. A paid service holding back part of the memory engine makes this open core.

Adoption

4 medium confidence
4.0

Adoption is counted as monthly downloads of the mem0ai package on PyPI and on npm. Each package carries both the self-hosted library and the client for the hosted Platform, so the count cannot separate open-source use from Platform use.

Capability

2 medium confidence
2.0

Mem0's open library extracts facts from conversations and serves them back by user, agent or session, but it only ever adds memories: it does not merge or correct what is stored, keeps no graph, and forgets only on dates the caller sets. Consolidation, decay and the entity graph are features of the hosted Mem0 Platform, not of the code Mem0 publishes.