LangMem and LangGraph Store: what it remembers, who owns it, and what it costs
thecontinuitylayer.com/memory-systems/langmemLangGraph's Store (namespaced JSON documents in a database you choose) plus the LangMem toolkit that extracts and manages memories in it.
- 1Yes
Is LangMem and LangGraph Store open source?
Yes, by LangChain's own page.
The langmem repository is MIT, and its tools work in any LangGraph app.
Yes means: The core is under an open-source license.
- 2Yes
Can you run LangMem and LangGraph Store yourself?
Yes, by LangChain's own page.
A pip-installed library on top of a store you run: in-memory for development, Postgres, Redis, MongoDB or Upstash in production.
Yes means: It runs on your own machine or server.
- 3Yes
Can you take your memory out of LangMem and LangGraph Store?
Yes, by LangChain's own page.
Memories are saved as JSON documents under a namespace and key in a store you run.
Yes means: An export, or the data sits in a standard store you own.
- 4Yes
Does LangMem and LangGraph Store work with more than one model provider?
Yes, by LangChain's own page.
Examples use Google, OpenAI, Anthropic, OpenRouter, Fireworks, Baseten and Ollama.
Yes means: It is not tied to one provider's models.
- 5Yes
Is there a hosted LangMem and LangGraph Store?
Yes, by LangChain's own page.
The store is available by default in LangGraph Platform deployments, where the hosted server handles storage.
Yes means: A cloud or managed option exists.
- 6Yes
Does LangMem and LangGraph Store have a free tier, and what is the entry price?
Yes, by LangChain's own page.
The library is free; LangGraph Platform has a Developer plan at $0 a seat with pay-as-you-go, Plus at $39 a seat a month, and Enterprise custom.
Yes means: A free tier exists and the entry paid price is published.
- 7Yes
Does LangMem and LangGraph Store scope memory per user and per session?
Yes, by LangChain's own page.
Namespaces are tuples such as (user_id, "memories"); threads are scoped by the checkpointer for short-term memory while the store holds memory across threads.
Yes means: Both per-user and per-session or per-agent memory are supported.
- 8Partly
Can you delete a user's memories from LangMem and LangGraph Store?
Partly, by LangChain's own page.
The store interface deletes one item at a time by namespace and key; no per-user bulk delete is documented.
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: MIT. Every grade above is read from LangChain's own page on the day shown. If a page has changed, tell us.