Mem0 Security / OpenMemory
Commercial Mem0 ships SOC 2 / HIPAA, zero-trust access controls, BYOK encryption, real-time monitoring, audit logs, workspace governance as defaults. OpenMemory is the local self-hosted variant (Docker + FastAPI + Postgres + Qdrant) for privacy-first deployments.
At a glance
- Type
- SOC 2 + HIPAA + zero-trust + BYOK
- Tier
- T1
- Created
- 2024-01 (Mem0 launched Jan 2024; security features and HIPAA BAA added with enterprise tier)
- Latest release
- not applicable — not OSS
- License
- not applicable — not OSS
- GitHub
- not applicable — no GitHub repo
- Pricing
- Hobby free; Starter $19/mo; Pro $249/mo; Enterprise custom with SOC2/HIPAA
- Funding
- $24M total ($3.9M seed Kindred + $20M Series A Basis Set + YC + Peak XV Oct 2025)
Taxonomy
- storage
- vector
- retrieval
- similarity
- persistence
- long-term
- update
- extraction
- unit
- fact
- governance
- auditable
- conflict
- llm-arbitrate
When to use
Optimised for: governance + compliance + audit + adversarial hardening
Anti-fit: not for hobbyist / non-production use cases
Pros & cons
Pros
Native privacy / governance hooks inside Mem0 — encryption, masking, retention policies as first-class config rather than bolt-ons.
Cons
Mem0-only; OpenMemory protocol is still emerging and lacks broad ecosystem support.
Claims & capabilities
Threat model: exfiltration, HIPAA/GDPR right-to-erasure, unauthorised access, cross-session leakage. MCP standard for local serving to Claude/ChatGPT/Perplexity.
Technical surface
- API surface
- REST (typical SaaS REST + first-party SDK pattern; see vendor docs for language coverage)
- Backend storage
- hybrid
- Deployment
- SaaS cloud; Enterprise VPC; OpenMemory self-hosted (Docker Compose)
- Embedding model
- multiple supported
- Multi-tenancy
- namespace
- MCP
- native (first-party)
- A2A
- no data — searched mem0.ai/security, docs.mem0.ai, docs.mem0.ai/platform/overview; A2A protocol not advertised
- OpenTelemetry
- no data — searched mem0.ai/security, docs.mem0.ai, docs.mem0.ai/platform/overview; OpenTelemetry export not advertised on enterprise tier
Compare Mem0 Security / OpenMemory with…
Similar systems
Other memory governance, privacy & safety in the catalog, ranked by inbound references.
- Acuvity (now Proofpoint) T1
Runtime enforcement targeting memory poisoning, unauthorised execution, identity spoofing per the OWASP LLM threat list. Visibility/control over MCP servers and locally-installed AI tools — the infrastructure layer where memory is most exposed.
- Enkrypt AI T1
Applies guardrails at three points: (1) before write to vector DB, (2) before query reaches embedding model, (3) before response. Detects malicious instructions in stored memory before retrieval; scans for PII/PHI in/out. Text + image + voice modalities.
- HiddenLayer AISec Platform 2.0 T1
Targets the supply-chain / lineage layer rather than runtime memory writes. Model Genealogy tracks training/fine-tuning/modification history — catches poisoning baked in during training. AIBOM generates auditable inventory of model components + datasets. Runtime layer also monitors agentic workflows.
- Lakera Guard / Lakera Red T1
Screens every prompt, response, and retrieved document for indirect prompt injection — primary vector for memory poisoning. Treats memory as untrusted: anything written to or read from memory is adversarial until proven clean. Lakera Red provides "Agent Breaker" gamified red-teaming.
- Microsoft Agent Governance Toolkit T2
Cross-Model Verification Kernel (CMVK) requires majority-voting agreement across multiple model calls before a memory-influenced action. Agent OS package intercepts every action (memory included) at sub-millisecond latency. MIT licensed.
- OWASP Agent Memory Guard T3
Open-source runtime defense. Enforces YAML policies on every memory read/write. SHA-256 baselines detect tampering, injection, sensitive-data leakage, protected-key modification, rapid-change anomalies. Forensic snapshots + rollback. Reference impl for OWASP ASI06 (Memory Poisoning).