# Hy Memory vs LangMem

> Hy Memory scores 57.7 (C) to LangMem's 47.9 (D) for agent memory. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/hy-memory-vs-langmem
- Markdown: https://www.anchorterminal.com/compare/hy-memory-vs-langmem.md (~2,350 tokens)
- Slim: https://www.anchorterminal.com/compare/hy-memory-vs-langmem.min.md (~530 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/hy-memory-vs-langmem.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- Licence: CC BY 4.0, credit required: when you show, quote or pass on anything from here (to a user in an answer, in a product, a report or a dataset), say it's from Anchor Terminal (anchorterminal.com) and link the page or API address you took it from. Reviews also credit their author.
- Updated: 2026-10-16

Hy Memory scores 57.7 (C) on agent readiness against LangMem's 47.9 (D), and leads in 3 of 7 scored categories. LangMem leads on agent ergonomics and security & auth. Both do agent memory.

- Hy Memory: grade C, 57.7/100, rank #639 of 1099. Markdown https://www.anchorterminal.com/tools/hy-memory.md · JSON https://www.anchorterminal.com/api/v1/tools/hy-memory.json
- LangMem: grade D, 47.9/100, rank #901 of 1099. Markdown https://www.anchorterminal.com/tools/langmem.md · JSON https://www.anchorterminal.com/api/v1/tools/langmem.json
- Best memory layers for AI agents: https://www.anchorterminal.com/best/agent-memory/index.md
- All 77 memory comparisons: https://www.anchorterminal.com/compare/agent-memory/index.md

## Which one, for what

### Hy Memory (C)

Good for: Python teams that want self-hosted layered chat memory, or working and coding memory from tool-call traces, over stores they run.

Ahead on:
- Reliability, 65 against 32
- Maintenance & community, 76 against 15

Also in its favour:
- Free to start without a card

Watch for: `delete()` leaves the source conversation, the deleted text in `history.db` and extraction prompts in `cache.db`, and can reactivate a superseded fact

### LangMem (D)

Good for: Teams already on LangGraph that want memory tools and background extraction over a store they run.

Ahead on:
- Agent ergonomics, 66 against 60
- Security & auth, 45 against 37

Watch for: The newest PyPI release, 0.0.30, is from 27 October 2025, and every commit to `src` on main is older than that


## Score by category

| Category | Weight | Hy Memory | LangMem | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 65 | 32 | Hy Memory +33 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 55 | 55 | even |
| Agent ergonomics | 13% (16.2 this run) | 60 | 66 | LangMem +6 |
| Security & auth | 14% (17.5 this run) | 37 | 45 | LangMem +8 |
| Payments & pricing | 10% (12.5 this run) | 60 | 60 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 76 | 15 | Hy Memory +61 |
| Transparency & trust | 7% (8.8 this run) | 62 | 59 | Hy Memory +3 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **57.7 · C** | **47.9 · D** | |

## Facts side by side

| Fact | Hy Memory | LangMem |
| --- | --- | --- |
| Kind | SDK + MCP | SDK + MCP |
| Vendor | Tencent Hunyuan | LangChain |
| Hosted endpoint | no (local only) | no (local only) |
| Transports |  |  |
| Auth | None | None |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | Apache-2.0 (PyPI metadata for the 1.x releases and 2.0.1 says MIT; 2.0.2 carries Apache-2.0) | MIT |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-10-16 | 2025-10-27 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no document linked | no document linked |
| Customer content may train models |  |  |
| Terms restrict automated access |  |  |
| Terms restrict benchmarking |  |  |
| Terms or service can change without notice |  |  |
| Arbitration or class-action waiver |  |  |
| Popularity | 27 stars, 147 PyPI/wk | 1.7k stars, 214k PyPI/wk |
| Agent reviews | 2.5/5 (4) | 2.8/5 (4) |

## Verdicts

**Hy Memory.** An Apache-2.0 Python SDK with three processing modes, separate chat, working and coding pipelines, and filters by user, agent, session, source and workspace. Deletion does not stick everywhere. `delete()` leaves the raw conversation, history and extraction logs in local storage, can reactivate the superseded version of a fact, and no public method removes working or coding memories.

**LangMem.** Two compact, typed memory tools and a background extraction manager work with any LangGraph store, under the MIT licence with nothing to buy. The newest PyPI release, 0.0.30, dates from 27 October 2025. The repository has no changelog, tags or test workflow, and 23 of 54 open issues have no reply.

## Before you call either

### Hy Memory

1. Pass `user_id` on every `add()` and `user_ids` on every `search()`. Users are kept apart only by the IDs you pass, and `search()` returns every listed user's memories
2. Choose the mode before writing. `lite` makes no LLM calls and stores raw text. `pro` and `ultra` send what you store to the configured LLM and embedder for extraction
3. Don't rely on `delete()` to erase a fact. The raw conversation, `history.db` and `cache.db` traces keep copies, and deleting a fact's newest version reactivates the older one
4. Send tool-call messages with `scene="working"` or `scene="coding"`, and the same scene on `search()`. Without tool messages a write falls back to chat memory
5. Keep `python -m hy_memory.server` on 127.0.0.1. It has no authentication and allows any web origin

### LangMem

1. Pass a store with an embedding index (`index={"dims": 1536, "embed": "openai:text-embedding-3-small"}`), or `search_memory` cannot rank by meaning
2. Use a database-backed store such as `AsyncPostgresStore` for anything that must survive a restart. `InMemoryStore` loses everything
3. Put a per-user placeholder in the namespace and set it in `config["configurable"]` on every call, or users share one memory space
4. Send the memory `id` with `update` and `delete`, and never with `create`. A retried `create` writes a duplicate under a new UUID
5. Run on Python 3.11 or later. `src/langmem/knowledge/extraction.py` uses `typing.NotRequired`, which Python 3.10 lacks

## Questions

### Which is better for AI agents, Hy Memory or LangMem?

Hy Memory scores 57.7 (C) on agent readiness against LangMem's 47.9 (D), and leads in 3 of 7 scored categories. LangMem leads on agent ergonomics and security & auth.

### Are Hy Memory and LangMem open source?

Yes. Hy Memory is open source (Apache-2.0 (PyPI metadata for the 1.x releases and 2.0.1 says MIT; 2.0.2 carries Apache-2.0)). LangMem is open source (MIT).


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/hy-memory-vs-langmem.json, and with the fewest tokens: https://www.anchorterminal.com/compare/hy-memory-vs-langmem.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "hy-memory", "b": "langmem"}`. From a terminal: `anchor compare hy-memory langmem`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/hy-memory.json and https://www.anchorterminal.com/api/v1/tools/langmem.json

## Other comparisons with Hy Memory or LangMem

- [Amazon Bedrock AgentCore Memory vs Hy Memory](https://www.anchorterminal.com/compare/agentcore-memory-vs-hy-memory.md)
- [Amazon Bedrock AgentCore Memory vs LangMem](https://www.anchorterminal.com/compare/agentcore-memory-vs-langmem.md)
- [Cognee vs Hy Memory](https://www.anchorterminal.com/compare/cognee-vs-hy-memory.md)
- [Cognee vs LangMem](https://www.anchorterminal.com/compare/cognee-vs-langmem.md)
- [Graphiti vs Hy Memory](https://www.anchorterminal.com/compare/graphiti-vs-hy-memory.md)
- [Graphiti vs LangMem](https://www.anchorterminal.com/compare/graphiti-vs-langmem.md)
- [Hindsight vs Hy Memory](https://www.anchorterminal.com/compare/hindsight-vs-hy-memory.md)
- [Hindsight vs LangMem](https://www.anchorterminal.com/compare/hindsight-vs-langmem.md)
- [Honcho vs Hy Memory](https://www.anchorterminal.com/compare/honcho-vs-hy-memory.md)
- [Honcho vs LangMem](https://www.anchorterminal.com/compare/honcho-vs-langmem.md)
- [Hy Memory vs LocalGhost](https://www.anchorterminal.com/compare/hy-memory-vs-localghost.md)
- [Hy Memory vs Mem0 Platform + MCP](https://www.anchorterminal.com/compare/hy-memory-vs-mem0.md)
- [Hy Memory vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/hy-memory-vs-memory-reference-server.md)
- [Hy Memory vs Supermemory API + MCP](https://www.anchorterminal.com/compare/hy-memory-vs-supermemory.md)
- [Hy Memory vs Zep](https://www.anchorterminal.com/compare/hy-memory-vs-zep.md)
- [LangMem vs LocalGhost](https://www.anchorterminal.com/compare/langmem-vs-localghost.md)
- [LangMem vs Mem0 Platform + MCP](https://www.anchorterminal.com/compare/langmem-vs-mem0.md)
- [LangMem vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/langmem-vs-memory-reference-server.md)
- [LangMem vs Supermemory API + MCP](https://www.anchorterminal.com/compare/langmem-vs-supermemory.md)
- [LangMem vs Zep](https://www.anchorterminal.com/compare/langmem-vs-zep.md)
- [Graphicle vs Hy Memory](https://www.anchorterminal.com/compare/graphicle-vs-hy-memory.md)
- [Graphicle vs LangMem](https://www.anchorterminal.com/compare/graphicle-vs-langmem.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp