EverMemOS is an open source “memory operating system” developed by EverMind that adds durable, structured long-term memory to AI agents. Instead of treating every prompt as a fresh start, it lets LLM‑based assistants remember past interactions, build evolving user profiles, and reason with context over days, weeks, or months. Under the hood it uses a four‑layer architecture designed to mirror parts of human cognition: an agentic layer that plans memory tasks, a memory layer that stores and recalls information as structured units, an index layer that handles embeddings and keyword‑based search, and an API/MCP interface layer that connects to external services. The project is released under the Apache 2.0 license and is built to serve as a shared memory backbone for multiple agents and applications.

EverMemOS
Enables AI assistants to retain past conversations and tailor their responses to you.
- 01Four‑Layer Memory DesignSeparates agent behavior, long‑term storage, indexing, and integration, so teams can plug EverMemOS into existing systems as a centralized memory backbone without tight coupling.
- 02Structured MemCells and Multi‑Level MemoriesConverts raw conversations into atomic MemCell units, then builds episodes, user profiles, preferences, semantic knowledge, and more—giving agents rich, queryable memories instead of loose text blobs.
- 03Hybrid Retrieval and Agentic RecallCombines BM25 keyword search via Elasticsearch, vector retrieval via Milvus, reciprocal‑rank‑fusion (RRF), and optional LLM‑guided multi‑round retrieval, letting agents surface relevant memory while ignoring noise.
- 04Living Profiles and PersonalizationMaintains continuously updated user profiles that learn preferences, habits, and relationships over time, so agents respond like a colleague who truly remembers previous chats.
- 05Benchmark‑Driven Memory EvaluationShips with an evaluation stack aligned with EverMind’s EverMemBench and related tools, and has reported state‑of‑the‑art scores such as 92.3 on LoCoMo and 82 on LongMemEval‑S for long‑term memory reasoning.
- 06Developer‑Friendly InfrastructureProvides a Docker Compose file that spins up MongoDB, Elasticsearch, Milvus, and Redis, along with a Python API server offering REST endpoints for memorization and retrieval, plus ready‑to‑run demo applications.
01What is EverMemOS?
02Core Features
- Four‑Layer Memory Design: Separates agent behavior, long‑term storage, indexing, and integration, so teams can plug EverMemOS into existing systems as a centralized memory backbone without tight coupling.
- Structured MemCells and Multi‑Level Memories: Converts raw conversations into atomic MemCell units, then builds episodes, user profiles, preferences, semantic knowledge, and more—giving agents rich, queryable memories instead of loose text blobs.
- Hybrid Retrieval and Agentic Recall: Combines BM25 keyword search via Elasticsearch, vector retrieval via Milvus, reciprocal‑rank‑fusion (RRF), and optional LLM‑guided multi‑round retrieval, letting agents surface relevant memory while ignoring noise.
- Living Profiles and Personalization: Maintains continuously updated user profiles that learn preferences, habits, and relationships over time, so agents respond like a colleague who truly remembers previous chats.
- Benchmark‑Driven Memory Evaluation: Ships with an evaluation stack aligned with EverMind’s EverMemBench and related tools, and has reported state‑of‑the‑art scores such as 92.3 on LoCoMo and 82 on LongMemEval‑S for long‑term memory reasoning.
- Developer‑Friendly Infrastructure: Provides a Docker Compose file that spins up MongoDB, Elasticsearch, Milvus, and Redis, along with a Python API server offering REST endpoints for memorization and retrieval, plus ready‑to‑run demo applications.
03Use Cases & Considerations
- Shared Memory for Internal Agents: An AI infrastructure team embeds EverMemOS as the common memory layer so that multiple internal agents (HR, IT, project‑tracking) can share a consistent, evolving view of each employee’s background, past questions, and preferences.
- Persistent Co‑pilot Assistants: A product team building a coding co‑pilot uses EverMemOS to store a developer’s past decisions, coding conventions, and open problems, allowing the assistant to provide context‑aware suggestions across sessions.
- Long‑Conversation Customer Support: A support automation provider integrates EverMemOS to give bots access to a user’s full conversation history and account details, so each new ticket is handled with full context instead of starting from scratch.
- Memory Architecture Research: Academic labs and research groups leverage EverMemOS together with EverMemBench to explore long‑context reasoning, retrieval‑augmented memory, and objective evaluation of agent recall.
- Emotionally Consistent Companion Agents: Digital therapeutics startups use the living profiles and multi‑level memories to create wellness assistants that remember a user’s emotional patterns and past conversations, enabling more personalized and sensitive interactions.
- Employee Enablement Bots: Internal enablement teams deploy HR or IT assistants that recall each employee’s previous interactions, reducing repetitive information requests and delivering a more personalized help experience.
- Nontrivial infrastructure footprint: Running the full stack requires Docker plus MongoDB, Elasticsearch, Milvus, and Redis, which can feel heavy for small teams or hobby projects.
- Early ecosystem maturity: While the project is actively developed, it currently has fewer off‑the‑shelf integrations and community plugins compared to more established search or vector store platforms.
- External LLM dependency for advanced modes: Agentic recall and some profile‑building steps rely on third‑party LLM APIs, introducing latency and vendor costs that are outside the scope of EverMemOS itself.
- Operational overhead: Self‑hosted deployments mean you are responsible for updates, scaling, and maintenance of the underlying databases, which may require DevOps expertise.
- Quality depends on tuning: Achieving the benchmarked performance requires careful configuration of retrieval modes, indexing, and prompt templates; out‑of‑the‑box results may vary across domains.
- Data privacy considerations: While self‑hosting gives full control, the system stores detailed user profiles and conversation histories; teams must implement their own data retention policies and access controls.
04How to use EverMemOS
- Clone the repository and start the infrastructure:
git clonethe official EverMemOS repo, then rundocker-compose upto launch the required backing services (MongoDB, Elasticsearch, Milvus, Redis) in one command. - Launch the API server: Start the Python‑based memory API server, which provides REST endpoints for storing memories, querying them, and managing user profiles.
- Choose a retrieval mode: Configure the system to use BM25‑only, vector‑only, hybrid RRF, or LLM‑guided multi‑round retrieval depending on your latency, cost, and accuracy requirements.
- Ingest raw conversations: Feed agent‑user dialogues through the
/memorizeendpoint. EverMemOS automatically converts them into MemCells, builds episodes, and updates user profiles. - Query memories in your agent: In your LLM‑agent code, call the retrieval API with a user ID and a natural language query to obtain a curated, context‑rich memory payload that can be injected into the model prompt.
- Evaluate and iterate: Use the built‑in evaluation stack and EverMemBench benchmarks to measure memory accuracy and adjust retrieval strategies or memory‑building rules for your specific domain.
05Pricing & Plans
The core of EverMemOS is open source and released under the Apache 2.0 license, meaning it is free to use, modify, and deploy in both personal and commercial self‑hosted projects. There are no usage limits or license fees for the open source components. For organizations that want managed services, dedicated enterprise support, or private cloud deployments, EverMind offers custom enterprise plans. Those plans are handled directly through EverMind and do not have publicly listed price tiers at this time. Disclaimer: Pricing information may not be up to date. For the most accurate and current details, refer to the official EverMemOS website.
06Platforms
- Self‑hosted via Docker Compose: The complete stack (MongoDB, Elasticsearch, Milvus, Redis, API server) runs on your own infrastructure using a single Docker Compose file.
- Python API server with REST endpoints: The memory API exposes
/memorize,/retrieve, and profile management endpoints, making it easy to integrate with any language that can call HTTP services. - MCP (Memory Control Protocol) interface: A dedicated integration layer allows MCP‑compatible agent frameworks to use EverMemOS as a plug‑and‑play memory provider.
- Local demo applications: Ready‑to‑run CLI and chat demos let you experiment and debug memory behavior before integrating into a production agent.
- Platform‑agnostic core: Because the logic is containerized and API‑driven, EverMemOS can be deployed on cloud VMs, on‑prem servers, or even local development machines.
07Tips & Best Practices
- Start with the quickstart demo: Use the included interactive chat demo to understand the full memory loop—ingestion, profile updates, and retrieval—within an hour before customizing.
- Tune retrieval mode to the task: For low‑latency scenarios, stick with BM25 or single‑stage vector search; save the more costly agentic multi‑round retrieval for complex, long‑context reasoning where precision is critical.
- Clean and archive old MemCells: Regularly review profiles and obsolete memories to keep retrieval fast and focused, especially when agents interact with hundreds of users over months.
- Leverage multi‑level memories deliberately: If your agent only needs episodic recall, you can skip profile updates or semantic knowledge to reduce storage and processing; enable the full stack only when personalization adds real value.
- Monitor infrastructure costs: The Docker stack runs MongoDB, Elasticsearch, Milvus, and Redis—plan resource allocation and scaling strategies early, particularly for high‑throughput production deployments.
- Test with your own benchmarks: While EverMemOS scores well on LoCoMo and LongMemEval‑S, create domain‑specific evaluation sets to ensure the memory system aligns with your exact user expectations.
08Who is EverMemOS for?
- AI infrastructure teams that need a shared, versioned memory backbone for multiple internal agents, with full control over data and deployment.
- Product teams building agentic assistants, co‑pilots, or chatbots where remembering user context across sessions is a core requirement.
- Customer support automation providers who want bots to recall entire conversation histories and account details, rather than treating each ticket in isolation.
- Research labs and academic groups studying long‑term memory, retrieval‑augmented reasoning, and evaluation, especially those already working with benchmarks like EverMemBench.
- Security‑conscious organizations that prefer an open source, Apache‑2.0‑licensed solution they can deploy on‑premises or in their own VPC without vendor lock‑in.
- Developers comfortable with Docker and Python who want a memory layer that is transparent, inspectable, and fits into existing MCP‑based or REST‑based agent architectures.
09Alternatives
View all
A lightweight, developer‑focused memory layer for LLM apps that adds personalized memory via simple API calls; less opinionated about multi‑level memory architecture.
Built‑in memory classes in the LangChain ecosystem that offer conversation buffer, summary, and vector‑store‑backed memory, but without a dedicated operating‑system‑like structure.
An open source memory server for conversational AI that stores and summarizes chat history with vector search; designed specifically for fast, scalable, production‑grade chat memory.
A system that gives LLMs a virtual memory management layer, allowing agents to page in long‑term context as needed; focuses on autonomous memory management rather than structured multi‑level profiles.
General‑purpose vector databases that can be used to build a simple memory store, but lack the MemCell‑style structuring, profile building, and benchmark‑driven evaluation that EverMemOS provides out of the box.
10FAQ
Q1. What exactly does EverMemOS “remember”?
EverMemOS stores structured memories at multiple levels. It breaks conversations into MemCells (atomic units), then organizes them into episodes, user profiles, preferences, semantic facts, and relationships. This means it remembers not just raw text, but meaningful patterns and personal details that evolve over time.
Q2. Can I use EverMemOS for free in a commercial product?
Yes. The open source core is licensed under Apache 2.0, allowing you to use, modify, and embed it in commercial self‑hosted applications without paying license fees. Enterprise managed services or direct support from EverMind may involve separate commercial agreements.
Q3. What infrastructure do I need to run it?
You need a server or machine capable of running Docker. The official setup uses Docker Compose to launch MongoDB, Elasticsearch, Milvus, and Redis, plus the Python API server. For production, you may need to scale these services independently.
Q4. Is EverMemOS tied to a specific LLM provider?
No. While some advanced retrieval and profile‑building functions use LLM calls, the system is model‑agnostic. You can configure it to use any LLM provider that offers a compatible API, giving you control over costs and model selection.
Q5. How is EverMemOS different from a vector database like Pinecone?
A vector database primarily stores and searches embeddings. EverMemOS is a higher‑level memory operating system that uses vector search as one component, but also handles structuring raw dialogues into MemCells, building living user profiles, performing hybrid retrieval (keyword + vector + re‑ranking), and offering a built‑in evaluation framework—features a vector database alone does not provide.
Know a similar tool?
Help others discover great AI tools by submitting it









