Mem0 Security / OpenMemory
Commercial Mem0 ships SOC 2 / HIPAA, zero-trust access controls, BYOK encryption, real-time monitoring, audit logs and workspace governance as defaults (Trust Center at trust.mem0.ai). For privacy-first deployments the self-hosted path is now the Mem0 open-source server (REST API + dashboard via Docker Compose with pgvector Postgres, admin setup wizard, per-user API keys, request audit log). As of Oct 2026 OpenMemory itself is a hosted MCP service and its old local Docker variant is no longer in the repo.
Active · Verified 2026-10-29 · fresh as of 2026-10-29 · 67 cited facts, 4 with a third-party source · 2 recorded changes · Suggest a correction
At a glance
- Type
- SOC 2 + HIPAA + zero-trust + BYOK vendor fix
- Tier
- T1
- Created
- 2024-01 (Mem0 launched Jan 2024; security features and HIPAA BAA added with enterprise tier) vendor fix
- Latest release
- v2.2.1 (2026-09-25) registry fix
- License
- Apache-2.0 registry fix
- GitHub
- mem0ai/mem0 — ~67.3k stars, last release 2026-09 repo fix
- Pricing
- Hobby free (10K adds/1K retrievals/mo); Starter $19/mo; Pro $249/mo; Enterprise custom vendor fix
- Funding
- $24M total ($3.9M seed Kindred + $20M Series A Basis Set + YC + Peak XV Oct 2025) third-party fix
- Freshness
- 2026-10-29 fix
- Layer
- agent-infra repo fix
- SDK languages
- python, rest, typescript vendor fix
- Protocols
- mcp-server vendor fix
- Compliance
- gdpr, hipaa, soc2-type1 vendor fix
- Developer activity
- OpenRank 25.56 (12-mo avg 24.36) · 193 participants — 2026-09 third-party fix
Memory 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 hosted or self-hosted (Docker)
- 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…
Alternatives to Mem0 Security / OpenMemory → live options ranked by shared design, licence, hosting and MCP support
Similar systems
Other memory governance, privacy & safety in the catalog, ranked by inbound references.
- Lakera Guard / Lakera Red T1
Acquired by Check Point Software (completed by 2025-11-11); being folded into Check Point's AI security platform. 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.
- Acuvity (now Proofpoint) T1
Acquired by Proofpoint (closed 2026-02-12). 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. Acquired by Anaconda (2026-08-04); Enkrypt AI is now sold as Anaconda's AI security and guardrails product.
- HiddenLayer AISec Platform 2.0 T1
AI security platform with four modules: AI asset discovery, supply-chain/model integrity validation, continuous attack simulation, and runtime detection/response, including protection of agents and MCP-based systems.
- Hyperconsciousness (hc) T3
Developer-alpha encrypted, append-only knowledge store for humans and agents, with CLI/MCP access and scoped, expiring grants. Traction: Submitted via intake issue #181
- 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.
Sources (66 cited facts, 4 third-party)
Each fact links to the page it came from; the badge says who published it (how to read sources).
- What it is SOC 2 + HIPAA + zero-trust + BYOK vendor
- What it does & what's distinct Commercial Mem0 ships SOC 2 / HIPAA, zero-trust access controls, BYOK encryption, real-t… vendor
- Claims / benefits Threat model: exfiltration, HIPAA/GDPR right-to-erasure, unauthorised access, cross-sess… vendor
- Modalities text vendor
- Created 2024-01 (Mem0 launched Jan 2024; security features and HIPAA BAA added with enterprise t… vendor
- Latest release v2.2.1 (2026-09-25) registry
- License Apache-2.0 registry
- GitHub mem0ai/mem0 — ~67.3k stars, last release 2026-09 repo
- Funding $24M total ($3.9M seed Kindred + $20M Series A Basis Set + YC + Peak XV Oct 2025) third-party
- Customers / scale 80k+ developers; AWS Agent SDK exclusive memory provider; 186M API calls/mo Q3 2025 vendor
- Pricing Hobby free (10K adds/1K retrievals/mo); Starter $19/mo; Pro $249/mo; Enterprise custom vendor
- Compliance SOC 2 Type II + HIPAA BAA (Enterprise); BYOK encryption; zero-trust access controls vendor
- Data handling cloud-managed US East (default); Enterprise VPC isolation; OpenMemory: local Docker Comp… vendor
- Deployment SaaS cloud; Enterprise VPC; OpenMemory hosted or self-hosted (Docker) vendor
- HQ San Francisco CA (YC S24) third-party
- Founders / pedigree Mem0 (YC S24; Taranjeet Singh & Deshraj Yadav) vendor
- Memory volume / scale cloud-managed; no published per-user cap vendor
- Performance no public benchmark scores found — vendor does not publish quantitative perf metrics vendor
- API surface REST (typical SaaS REST + first-party SDK pattern; see vendor docs for language coverage) vendor
- Backend storage hybrid vendor
- Multi-tenancy namespace vendor
- Encryption at-rest + in-transit vendor
- SSO / RBAC SSO + RBAC vendor
- Embedding model multiple supported vendor
- Consistency not specified — vendor docs do not address this dimension vendor
- Versioning not specified — vendor docs do not address this dimension vendor
- Tombstoning soft-delete only vendor
- Schema evolution schema with migration vendor
- Namespace primitives per-tenant vendor
- Contradiction handling LLM resolves and overwrites vendor
- Forgetting policy not specified — vendor docs do not address this dimension vendor
- MCP support native (first-party) vendor
- Webhooks / events webhooks supported vendor
- Import / export JSON (JSON-over-REST; CSV/Parquet export for analytical use) vendor
- Validated verticals regulated enterprise: financial-services, healthcare, government, legal vendor
- Time to running <1day to <1week (enterprise procurement + integration) vendor
- Anti-fit not for hobbyist / non-production use cases vendor
- Optimised for governance + compliance + audit + adversarial hardening vendor
- Adjacent infrastructure BYO agent stack; this layer guards it vendor
- Pros Native privacy / governance hooks inside Mem0 — encryption, masking, retention policies … vendor
- Cons Mem0-only; OpenMemory protocol is still emerging and lacks broad ecosystem support. vendor
- Project & sources security page security best practices vendor
- obs-custom Inherits Mem0 base observability surface vendor
- cost-token-budget no vendor
- cost-prompt-caching no vendor
- cost-semantic-caching no vendor
- cost-batching no vendor
- cost-model-routing no vendor
- cost-streaming-only no vendor
- cost-observability-cost-attribution no vendor
- eval-langsmith-evals no vendor
- eval-braintrust no vendor
- eval-weights-and-biases-agent no vendor
- eval-helicone-evals no vendor
- eval-custom-test-harness no vendor
- eval-human-loop no vendor
- eval-production-traffic-replay no vendor
- adoption-accelerator yc-s24 third-party
- architecture-deployment-locus hybrid vendor
- licensing-bucket open-core vendor
- positioning-platform-vs-product platform vendor
- taxonomy-three-layer-rollup agent-infra repo
- developer-activity-opendigger {"activity":442.12,"as_of":"2026-09","openrank_12mo":24.36,"openrank_current":25.56,"par… third-party
- compliance-certifications gdpr,hipaa,soc2-type1 vendor
- sdk-languages python,rest,typescript vendor
- protocol-support mcp-server vendor
What changed
Changes to this record's lifecycle, licence, release, pricing and hosting facts, from the catalog's git history. Subscribe (Atom)
- 2026-10-29
- Homepage “https://mem0.ai/security” → “https://trust.mem0.ai/”
- 2026-10-22
- License “not applicable — not OSS” → “Apache-2.0” source
- Latest release “not applicable — not OSS” → “v2.2.1 (2026-09-25)” source
- Pricing “Hobby free; Starter $19/mo; Pro $249/mo; Enterprise custom with SOC2/HIPAA” → “Hobby free (10K adds/1K retrievals/mo); Starter $19/mo; Pro $249/mo; Enterprise custom” source
- Deployment “SaaS cloud; Enterprise VPC; OpenMemory self-hosted (Docker Compose)” → “SaaS cloud; Enterprise VPC; OpenMemory hosted or self-hosted (Docker)” source
Related systems
References (2)
- pgvector builds on · depends on at runtime — For privacy-first deployments the self-hosted path is now the Mem0 open-source server (REST API + dashboard via Docker Compose with pgvector Postgres, admin setup wizard, per-user API keys, request…
- Qdrant builds on — OpenMemory is the local self-hosted variant (Docker + FastAPI + Postgres + Qdrant)