Memori
A LLM-agnostic agent memory layer for production systems, converting agent execution and conversation into structured, persistent states.
Who it is for: Developers who want self-hosting and control over the technology stack and data, and teams or organizations using production agents and requiring enterprise deployment forms
Positioning
A LLM-agnostic agent memory layer for production systems, converting agent execution and conversation into structured, persistent states.
- Product stage: Open source self-hosting and production solutions coexist; the pricing page also lists Cloud Free, actual commercialization stage and scale still need verification
Core features
- Structured Memory Capture: Captures each chat turn and classifies it as fact, preference, rule, or summary.
- Relevant Context Retrieval: Extracts relevant content from conversations and documents when context is needed in prompts.
- Semantic Context Augmentation: Automatically supplements semantic context for ambiguous language queries.
- Explainable Retrieval Results: Provides reasons for including retrieval results and traces relevance by entity, time, and source.
- SDK and MCP Access: The official website states that SDK can be integrated with one line of code into existing code; the pricing page lists Full SDK and MCP server access.
- Memory Graph and Runtime Analysis: Provides an interactive memory graph and tracks memory creation, recall usage, and cache hit rates.
- Data Boundaries and Deployment Options: README lists hosted cloud, single-tenant cloud, VPC, and on-premises deployment; the official website states that in BYODB mode, data remains in the user's database unless Memori Cloud is explicitly enabled.
Target users
- Developers who want self-hosting and control over the technology stack and data: A LLM-agnostic agent memory layer for production systems, converting agent execution and conversation into structured, persistent states.
- Teams or organizations using production agents and requiring enterprise deployment forms: A LLM-agnostic agent memory layer for production systems, converting agent execution and conversation into structured, persistent states.
Pricing
- Open source self-hosting and Cloud Free layer coexist with production solutions; from the materials visible, production solutions are tiered by number of agents, deployment form, and organizational scope. Actual conversion path is unverified. · Open Source is free for self-hosting; Cloud Free is a $0 hosted layer with a quota of creating 5000 memories and recalling 15000 memories; Team starts at $60,000 annually; Business starts at $150,000 annually; Enterprise is a custom quote.: Billing rules after free Cloud quota have not been verified; actual contract discounts, implementation fees, renewal conditions, and usage-based billing for production solutions have not been verified.
Verdict
Existing materials support Memori having structured memory capture, relevant context retrieval, SDK/MCP integration description, enterprise deployment options, and tiered pricing information; however, there is insufficient evidence of user feedback samples, production effects, revenue, retention, financing, and scale, and the experimental scope for LoCoMo and cost figures also remain inconsistent, so it cannot be confirmed that the product-market fit, long-term moat, or scalability economics exist based on this.
- Strength: The official website and README directly describe structured persistent state, retrieval, deployment forms, and data location; the pricing page lists self-hosted open source, Cloud Free, and production solutions simultaneously; GitHub has public repositories, open issues, and version records.
- Limitation: Direct evidence is lacking for Python SDK, Hermes official support, data retention and deletion capabilities; LoCoMo accuracy and token/cost figures have multiple scopes, and evaluation conditions are not unified; independent user feedback, revenue, retention, financing, and real production effect evidence is missing; open issues record Dashboard, Graph, batch extraction, natural language fact extraction, and index backend-related problems or requests.
How it delivers value
- Task Input and Attribution: Memori captures chat turns; memory cannot be created if attribution information is not provided according to the README. → Memori captures chat turns; memory cannot be created if attribution information is not provided according to the README.
- Structured Understanding: Chat turns are categorized as facts, preferences, rules, and summaries. → Chat turns are categorized as facts, preferences, rules, and summaries.
- Context Retrieval: The system extracts relevant content from conversations and documents, and supplements semantic context for fuzzy queries. → The system extracts relevant content from conversations and documents, and supplements semantic context for fuzzy queries.
- Agent Execution: The official website reports an 87% accuracy rate on LoCoMo and a 97% reduction in token usage compared to full context. → The official website reports an 87% accuracy rate on LoCoMo and a 97% reduction in token usage compared to full context.
- Feedback and Observation: The product claims to track memory creation, retrieval usage, and cache hit rate, and provide memory graphs. → The product claims to track memory creation, retrieval usage, and cache hit rate, and provide memory graphs.
Competition
Memori positions itself as a structured agent memory infrastructure, emphasizing LLM, data storage, and framework independence.
- vs Zep: Wins: Memori's README claims it outperforms Zep in LoCoMo comparisons. Loses: Existing materials lack independent production environment comparisons.
- vs LangMem: Wins: Memori's README claims it outperforms LangMem in LoCoMo comparisons. Loses: Existing materials lack independent production environment comparisons.
- vs Mem0: Wins: Memori's README claims it outperforms Mem0 in LoCoMo comparisons. Loses: Existing materials lack independent production environment comparisons.
Risks
- Hermes-related open issues report empty Cloud Dashboard and Graph problems.: Hermes-related open issues report empty Cloud Dashboard and Graph problems.
- Batch or on-demand extraction, natural language fact extraction, and pluggable indexes still appear in open issues or proposals.: Batch or on-demand extraction, natural language fact extraction, and pluggable indexes still appear in open issues or proposals.
- LoCoMo has two sets of product-reported numbers: 87% and 81.95%, with existing materials not explaining differences in experimental versions, dataset scope, or evaluation conditions.: LoCoMo has two sets of product-reported numbers: 87% and 81.95%, with existing materials not explaining differences in experimental versions, dataset scope, or evaluation conditions.
- Token and cost metrics have different scopes such as 97%, 4.97%, and 98%; existing materials do not provide unified definitions and experimental conditions.: Token and cost metrics have different scopes such as 97%, 4.97%, and 98%; existing materials do not provide unified definitions and experimental conditions.
- PCI, SOC 2, and data control belong to official website or README materials; actual audit and production deployment evidence is not provided.: PCI, SOC 2, and data control belong to official website or README materials; actual audit and production deployment evidence is not provided.
Company
- Stage: Open source self-hosting and production solutions coexist; the pricing page also lists Cloud Free, actual commercialization stage and scale still need verification
- Funding: Not disclosed
User voices
- Positive: The official website's Swarms Corporation evaluation states that integrating Memori into their agents was simple, clean, and direct.
- Positive: The official website's Agno evaluation states that the Memori toolkit for Agno works well.
- Negative: GitHub open issue reports that the Hermes agent memory can be viewed via agent_recall, but the Cloud Dashboard is empty and has Graph issues.
- Negative: GitHub open issue requests support for batch or on-demand memory extraction, rather than message-by-message processing.
- Negative: GitHub open issue requests natural language fact extraction and pluggable retrieval backend.
- Requested: The official website's recommendation is a third-party quote presented by the product side, which cannot represent overall satisfaction.
- Requested: GitHub Issues do not represent all users.
- Requested: No attributable samples from Reddit, X, WeChat, Xiaohongshu, Zhihu, or independent reviews were collected in this round.
Sources
Updated 2026-08-18