MemOS: what it remembers, who owns it, and what it costs
thecontinuitylayer.com/memory-systems/memosA self-described memory operating system for agents with composable memory cubes, hybrid retrieval and skill memory; an open-source server plus a cloud API.
- 1Yes
Is MemOS open source?
Yes, by MemTensor's own page.
The repository is Apache-2.0, and the open-source edition runs entirely in your own environment.
Yes means: The core is under an open-source license.
- 2Yes
Can you run MemOS yourself?
Yes, by MemTensor's own page.
Self-hosted with Docker Compose (Neo4j and Qdrant required) or directly; a local plugin uses SQLite.
Yes means: It runs on your own machine or server.
- 3Partly
Can you take your memory out of MemOS?
Partly, by MemTensor's own page.
Self-hosted memory sits in Neo4j and Qdrant that you run and is described as inspectable and editable; no export or dump is documented.
Yes means: An export, or the data sits in a standard store you own.
- 4Yes
Does MemOS work with more than one model provider?
Yes, by MemTensor's own page.
Model backends include Ollama, OpenAI or an OpenAI-compatible proxy, Qwen, DeepSeek and Hugging Face; Anthropic and Gemini are not listed.
Yes means: It is not tied to one provider's models.
- 5Yes
Is there a hosted MemOS?
Yes, by MemTensor's own page.
A fully managed cloud API with a console.
Yes means: A cloud or managed option exists.
- 6Partly
Does MemOS have a free tier, and what is the entry price?
Partly, by MemTensor's own page.
The cloud offers free trial quotas per developer account; no price in US dollars appears on any page checked.
Yes means: A free tier exists and the entry paid price is published.
- 7Yes
Does MemOS scope memory per user and per session?
Yes, by MemTensor's own page.
Requests carry a user id; memory cubes isolate or share memory across users, projects and agents; the cloud add call takes a conversation id.
Yes means: Both per-user and per-session or per-agent memory are supported.
- 8Yes
Can you delete a user's memories from MemOS?
Yes, by MemTensor's own page.
The cloud delete call with only a user id clears all of that user's memories in the project; the self-hosted server has a delete-memories-for-user endpoint.
Yes means: A documented way to delete everything for one user.
What these grades say about continuity, and what they do not.
Every grade on this site is read from the maker's own pages. The Continuity Framework asks five things of any system that carries state: that it carry, govern, evolve, prove and forget. These tests reach carry, govern and forget; they do not reach evolve or prove, which no maker's page documents in a gradeable way. A high letter is a good memory system, not a continuity layer.
- M1 Open sourceCarry
- Open source means the memory engine can outlive the vendor; the state is not hostage to a contract.
- M2 Self-hostCarry
- Self-hosting puts the store under the owner's control, which is the precondition for every other obligation.
- M3 ExportCarry
- An export is question C3: can the state leave in a form another system reads? A standard store you own answers it; a proprietary dump only partly.
- M4 Any modelCarry
- Working with more than one model provider is question C2: the memory, not the model, holds the state.
- M7 ScopingGovern
- Scoping per user, agent and session is question G2: who may read and write each item. It is the floor of governance, not the ceiling.
- M8 DeleteForget
- A documented delete for one user is rung 5 of the erasure ladder: the record leaves the store. Derived memories, the index and backups are not covered unless the maker says so. Rung 5 of the erasure ladder: delete the record.
License as stated: Apache-2.0. Every grade above is read from MemTensor's own page on the day shown. If a page has changed, tell us.