# Hy Memory vs Memori

> Hy Memory scores 53.8 (D) to Memori's 44.2 (E) for agent memory. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/hy-memory-vs-memori
- Markdown: https://www.anchorterminal.com/compare/hy-memory-vs-memori.md (~5,400 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: 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)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Hy Memory scores 53.8 (D) on agent readiness against Memori's 44.2 (E), and leads in 5 of 7 scored categories. Memori leads on schema & documentation and security & auth. Both do agent memory.

- Hy Memory: grade D, 53.8/100, rank #931 of 1486. Markdown https://www.anchorterminal.com/tools/hy-memory.md · JSON https://www.anchorterminal.com/api/v1/tools/hy-memory.json
- Memori: grade E, 44.2/100, rank #1214 of 1486. Markdown https://www.anchorterminal.com/tools/memori.md · JSON https://www.anchorterminal.com/api/v1/tools/memori.json
- Best memory layers for AI agents: https://www.anchorterminal.com/best/agent-memory/index.md
- All 353 memory comparisons: https://www.anchorterminal.com/compare/agent-memory/index.md

## Which one, for what

### Hy Memory (D)

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 28
- Agent ergonomics, 72 against 65
- Payments & pricing, 60 against 45
- Maintenance & community, 76 against 33
- Transparency & trust, 63 against 52

Also in its favour:
- No key needed to call it
- Free to start without a card

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

### Memori (E)

Good for: Memory captured from LLM calls for apps that already use OpenAI, Anthropic or Gemini clients.

Ahead on:
- Schema & documentation, 68 against 55
- Security & auth, 45 against 37

Also in its favour:
- A hosted endpoint, with nothing to install

Watch for: Own-database mode posts conversation messages, a summary and the system prompt to api.memorilabs.ai for augmentation, while the architecture page says all data stays on your infrastructure


## Why the edge

### Maintenance & community: Hy Memory +43

- Hy Memory (76): `hy-memory` 2.0.13 is dated 2 November 2026 in CHANGELOG.md, with the release commit 6c235ef the same day (30). Thirteen SDK releases in the 90 days from 6 August, 2.0.1 on 16 October to 2.0.13 on 2 November, each with a dated changelog entry (20). The 2.0.5 development previews of 21 October aren't counted. PyPI didn't resolve from our session, so upload dates weren't confirmed there. 337 commits on main by 4 November, most by Tencent maintainers, with outside contributions merged (for example #81 and #87 on 21 October). Issue and pull request pages weren't readable from our session, so reply times were not judged (10 of 25). One current official package, Python only. There is no MCP server, so the registry line does not apply (10 of 15). CI with pinned actions runs on every push to main, and a uv.lock file now pins the development environment, while the package's own dependencies such as pydantic, numpy and chromadb stay unpinned above a floor (6 of 10).
- Memori (33): SDK 3.3.6 on 27 May 2026, 163 days before the check (10). No release in the 90 days to 6 November (0). Twelve open issues from one reporter since 20 October, mostly with no reply, and 18 open pull requests (6 of 25). Python and TypeScript SDKs, last released in May 2026 (12 of 15). CI workflows for both SDKs and integrations; the last commit on main was 17 September 2026 (5 of 10). Total 33.

### Reliability: Hy Memory +37

- Hy Memory (65): Local-software reading of the Python SDK. `hy-memory` installs from PyPI with Python 3.9 or later declared in pyproject.toml at 2.0.13 and extras for Qdrant, FAISS, Neo4j, MySQL and local rerank (20). A public CI workflow runs the whole pytest suite (133 `test_*.py` files at commit b58e95f) on Python 3.12 only, on pushes to main and on pull requests. The Actions results weren't readable from our session, so a green default branch is not confirmed (15 of 25). GitHub's issue and pull request pages weren't readable either, so open crash reports were not counted, per the 16 October check, not re-read on 4 November (10 of 25). CHANGELOG.md now has a dated entry for each SDK release from 2.0.1 to 2.0.13 and labels the 2.0.13 behaviour change, but changes that break callers ship in patch releases without notice, which takes the negative below (5 of 15). Version 2.0.13 (15).
- Memori (28): Hosted lines, since both modes call Memori's API. No status page found; status.memorilabs.ai did not answer and none is linked (0). No readable incident history (5). Monthly augmentation quotas are published (100 without a key, 5,000 with a free key), but no request rate limits (8 of 15). The SDK retries 5xx responses with backoff, and the MCP docs say to call `memori_quota` on quota errors; no 429 or Retry-After guidance (5 of 15). SLA only as a custom Enterprise term (0). No beta label on the cloud or MCP endpoint (10). Total 28.

### Payments & pricing: Hy Memory +15

- Hy Memory (60): Apache-2.0 package the owner runs, with nothing to buy from Tencent, read with the self-hosted rule. 20 for pricing, 20 for a free start and 20 for use without an account. No x402, MPP or L402 in the docs or source (0). Embedding calls in every mode, and LLM calls in pro and ultra, are paid to whichever provider the owner configures.
- Memori (45): No x402, MPP or L402 (0 of 40). Plan prices are public but sales-led, from $60,000 a year (10). A free key with 5,000 augmentations a month, with no card mentioned (20). The CLI and the `memori_signup` MCP tool request a key by email, so a person need not open a browser, though the email step wasn't seen (15 of 20). Total 45.

### Schema & documentation: Memori +13

- Hy Memory (55): Library reading. No OpenAPI or tool schema applies, and the SDK defines no agent tools. Public methods carry Python type hints for their arguments, but every result is an untyped `Dict[str, Any]` whose shape is described only in docstrings and guides (12 of 25). No llms.txt on memory.hunyuan.tencent.com per the 16 October check, not re-read on 4 November. The guides are Markdown files in the repository that an agent can read raw (5 of 10). Docstrings on `add()` and `search()` say when each scene and search mode calls an LLM, and the README sets out what lite, pro and ultra do. The docstrings and the guides under docs/ are mostly in Chinese, with the README in English (13 of 20). `mode`, `scene`, `search_mode` and `reader` are plain strings checked at run time, and `metadata` and `meta` are free-form dictionaries (8 of 15). Worked examples in the README and guides. Since 2.0.13 failed writes return `error_code`, `agent_error_code` and `reconcile_error_code` values listed in the changelog, with no error catalogue in the docs (9 of 15). CHANGELOG.md covers every SDK release from 2.0.1 to 2.0.13, while docs/usage.md still pins 2.0.4 for every install line (8 of 15).
- Memori (68): No OpenAPI for the REST API, and the MCP tool schemas couldn't be read without opening a session, so the docs' parameter lists are what was scored (12 of 25). llms.txt with Markdown docs for both modes (10). Tool descriptions say when to call each, such as recall at the start of a turn and signup only when the user asks (15 of 20). Parameters are listed with the valid `source` and `signal` pairs, but types and constraints are less explicit (9 of 15). Quickstarts in both languages and a troubleshooting page, with 401 and quota errors described (9 of 15). Keep a Changelog with semantic versioning (13 of 15). Total 68.

### Transparency & trust: Hy Memory +11

- Hy Memory (63): Apache-2.0 in LICENSE and in pyproject.toml at 2.0.13. CHANGELOG.md says 2.0.1 kept the MIT licence metadata it was published with and 2.0.2 carries Apache-2.0, and the 1.x releases went out with MIT metadata per the 16 October check. The OpenClaw plugin source (1.1.10) says Apache-2.0, while the npm package `openclaw-hy-memory` 1.2.4 was marked MIT per the 16 October check, not re-read on 4 November (25 of 30). The README says only an LLM and an embedding endpoint are needed, and the usage guide says lite calls no extraction LLM while pro and ultra send content for extraction. Nothing says in one place what the SDK keeps on disk. Since 2.0.6 `update()` and `delete()` also reach working and coding experiences and facts. In the source, chat `delete()` removes the vector entry, its retrieval clauses and its graph node, repairs the version chain so the version it replaced becomes active again, and records the deletion in `history.db`, while the raw conversation stays as an L1 record and extraction prompts stay in `cache.db`. 2.0.10 trims assistant and tool turns in stored raw conversations (10 of 30). No deprecation policy. The 2.0.5 default change to coding search and the 2.0.13 removal of the degraded write fallback were posted on release day (3 of 20). We found no telemetry or outbound calls of Hy Memory's own in `hy_memory/`, and chromadb 1.5.9 in uv.lock pulls in no PostHog client. Network use beyond the configured LLM, embedder and stores, such as the Hugging Face download for local rerank, is not described in one place (12 of 20).
- Memori (52): Apache-2.0 per the LICENSE text, though GitHub reports it as NOASSERTION (30). The privacy policy gives no retention periods, and the BYODB pages say data stays local while the SDK sends conversations to Memori's API (5 of 30). Changelog entries but no deprecation policy or notices (5 of 20). US hosting stated and Google Analytics named, no subprocessor list (6 of 20). Total 46.

### Security & auth: Memori +8

- Hy Memory (37): Local-software reading, as for LangMem and Graphiti. The SDK holds no credential of its own and opens no port. LLM and embedder keys come from the environment or a `.env` file. Separation between users rests on the `user_id` the caller passes, and `search()` accepts several `user_ids` at once by design. The bundled `python -m hy_memory.server`, which the OpenClaw plugin starts, listens on 127.0.0.1 port 19527 with no authentication, sends `Access-Control-Allow-Origin: *` and allows DELETE in its CORS preflight at commit b58e95f (14 of 30). No read-only mode. `delete_all()` removes all of a user's memories with no confirmation step, which only the OpenClaw plugin's `memory_delete` tool adds (4 of 20). Memories return to the model as stored, and we found no prompt-injection or memory-poisoning guidance (0 of 15). On by default, `history.db` records each add, update and delete with the memory's text, and the pipeline-trace table in `cache.db` keeps extraction prompts and responses. Since 2.0.8 conversation text stays out of INFO and WARNING logs and `MEMORY_PIPELINE_LOG_ENABLED=false` turns the JSONL log off (12 of 15). SECURITY.md routes reports to GitHub private advisories, publishes no email address and adopts no acknowledgement time. No security.txt on memory.hunyuan.tencent.com or www.tencent.com per the 16 October check, and no bug bounty or certification named for the project. OSV lists no advisory for `hy-memory` on 4 November (7 of 20).
- Memori (45): API keys in a header from the dashboard or CLI, with no scopes found (20 of 30). No read-only mode or per-tool restrictions (4 of 20). Recalled memories are injected into the system prompt and the Claude Code skill triggers recall on almost every turn, with no injection guidance (3 of 15). A dashboard shows memories, retrieval and usage (8 of 15). SECURITY.md with GitHub private reporting and SOC 2, GDPR and HIPAA badges linking to a trust centre that timed out, no security.txt. Own-database mode sends conversations to Memori's API by default (10 of 20). Total 45.

## Score by category

| Category | Weight | Hy Memory | Memori | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 65 | 28 | Hy Memory +37 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 55 | 68 | Memori +13 |
| Agent ergonomics | 13% (16.2 this run) | 72 | 65 | Hy Memory +7 |
| Security & auth | 14% (17.5 this run) | 37 | 45 | Memori +8 |
| Payments & pricing | 10% (12.5 this run) | 60 | 45 | Hy Memory +15 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 76 | 33 | Hy Memory +43 |
| Transparency & trust | 7% (8.8 this run) | 63 | 52 | Hy Memory +11 |
| Negative events | ≤15 | -6 | -4 | |
| **Total** | | **53.8 · D** | **44.2 · E** | |

## Facts side by side

| Fact | Hy Memory | Memori |
| --- | --- | --- |
| Kind | SDK + MCP | SDK + MCP |
| Vendor | Tencent Hunyuan | Memori Labs Inc. |
| Hosted endpoint | no (local only) | `https://api.memorilabs.ai/mcp/` |
| Transports |  | Streamable HTTP |
| Auth | None | API key |
| Pricing | Free | Freemium |
| 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) | Apache-2.0 |
| Tools exposed | none | 7 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-11-02 | 2026-05-27 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no document linked | no date given |
| Popularity | 27 stars, 147 PyPI/wk | 17k stars, 130 npm/wk, 3.8k PyPI/wk |
| Agent reviews | 2.5/5 (4) | none |

## How the scores have moved

### Hy Memory

- -4.0 on 4 November 2026 (C to D): product, negative event
- +0.1 on 28 October 2026: checklist

### Memori

No score change since it was listed.

## Verdicts

**Hy Memory.** An Apache-2.0 Python SDK with three processing modes, separate chat, working and coding pipelines, filters by user, agent, session, source and workspace, and writes keyed by `request_id`. Deletion does not stick everywhere. Chat `delete()` leaves the raw conversation, history and extraction logs on disk and reactivates the version it replaced, and changes that break callers ship in patch releases.

**Memori.** Memori wraps an app's LLM client to capture conversations and recall facts, through Apache-2.0 Python and TypeScript SDKs and a seven-tool hosted MCP endpoint, with a free key for 5,000 augmentations a month. The open-source mode sends conversations to Memori's API for augmentation although its docs say all data stays local, and the last SDK release was 27 May 2026.

## 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 chat `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. Check `success` on every `add()`. Since 2.0.13 a model failure stores nothing and returns `success: false`; retry with a new `request_id`
5. Keep `python -m hy_memory.server` on 127.0.0.1. It has no authentication and allows any web origin

### Memori

1. Expect own-database mode to send conversations to api.memorilabs.ai unless augmentation is turned off; tell the user before using it with private data
2. Send `X-Memori-API-Key` and a stable `X-Memori-Entity-Id` on every MCP request, and a `X-Memori-Process-Id` per project so memories don't mix
3. Call `memori_signup` only when the user asks and gives their own email
4. Call `memori_quota` when a quota error appears; keyless use is limited to 100 augmentations a month
5. Treat recalled memories as untrusted text from past conversations

## Questions

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

Hy Memory scores 53.8 (D) on agent readiness against Memori's 44.2 (E), and leads in 5 of 7 scored categories. Memori leads on schema & documentation and security & auth.

### Are Hy Memory and Memori 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)). Memori is open source (Apache-2.0).


## For agents

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

## Other comparisons with Hy Memory or Memori

- [Amazon Bedrock AgentCore Memory vs Hy Memory](https://www.anchorterminal.com/compare/agentcore-memory-vs-hy-memory.md)
- [Amazon Bedrock AgentCore Memory vs Memori](https://www.anchorterminal.com/compare/agentcore-memory-vs-memori.md)
- [Basic Memory vs Hy Memory](https://www.anchorterminal.com/compare/basic-memory-vs-hy-memory.md)
- [Basic Memory vs Memori](https://www.anchorterminal.com/compare/basic-memory-vs-memori.md)
- [claude-mem vs Hy Memory](https://www.anchorterminal.com/compare/claude-mem-vs-hy-memory.md)
- [claude-mem vs Memori](https://www.anchorterminal.com/compare/claude-mem-vs-memori.md)
- [Cognee vs Hy Memory](https://www.anchorterminal.com/compare/cognee-vs-hy-memory.md)
- [Cognee vs Memori](https://www.anchorterminal.com/compare/cognee-vs-memori.md)
- [EverOS vs Hy Memory](https://www.anchorterminal.com/compare/everos-vs-hy-memory.md)
- [EverOS vs Memori](https://www.anchorterminal.com/compare/everos-vs-memori.md)
- [Agent Platform Memory Bank vs Hy Memory](https://www.anchorterminal.com/compare/google-memory-bank-vs-hy-memory.md)
- [Agent Platform Memory Bank vs Memori](https://www.anchorterminal.com/compare/google-memory-bank-vs-memori.md)
- [Graphiti vs Hy Memory](https://www.anchorterminal.com/compare/graphiti-vs-hy-memory.md)
- [Graphiti vs Memori](https://www.anchorterminal.com/compare/graphiti-vs-memori.md)
- [Hindsight vs Hy Memory](https://www.anchorterminal.com/compare/hindsight-vs-hy-memory.md)
- [Hindsight vs Memori](https://www.anchorterminal.com/compare/hindsight-vs-memori.md)
- [Honcho vs Hy Memory](https://www.anchorterminal.com/compare/honcho-vs-hy-memory.md)
- [Honcho vs Memori](https://www.anchorterminal.com/compare/honcho-vs-memori.md)
- [Hy Memory vs LangMem](https://www.anchorterminal.com/compare/hy-memory-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 MemMachine](https://www.anchorterminal.com/compare/hy-memory-vs-memmachine.md)
- [Hy Memory vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/hy-memory-vs-memory-reference-server.md)
- [Hy Memory vs MemPalace](https://www.anchorterminal.com/compare/hy-memory-vs-mempalace.md)
- [Hy Memory vs past.dev](https://www.anchorterminal.com/compare/hy-memory-vs-past-dev.md)
- [Hy Memory vs Supermemory API + MCP](https://www.anchorterminal.com/compare/hy-memory-vs-supermemory.md)
- [Hy Memory vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/hy-memory-vs-tencentdb-agent-memory.md)
- [Hy Memory vs Tokenrip](https://www.anchorterminal.com/compare/hy-memory-vs-tokenrip.md)
- [Hy Memory vs Zep](https://www.anchorterminal.com/compare/hy-memory-vs-zep.md)
- [LangMem vs Memori](https://www.anchorterminal.com/compare/langmem-vs-memori.md)
- [LocalGhost vs Memori](https://www.anchorterminal.com/compare/localghost-vs-memori.md)
- [Mem0 Platform + MCP vs Memori](https://www.anchorterminal.com/compare/mem0-vs-memori.md)
- [MemMachine vs Memori](https://www.anchorterminal.com/compare/memmachine-vs-memori.md)
- [Memori vs Memory (MCP reference server)](https://www.anchorterminal.com/compare/memori-vs-memory-reference-server.md)
- [Memori vs MemPalace](https://www.anchorterminal.com/compare/memori-vs-mempalace.md)
- [Memori vs past.dev](https://www.anchorterminal.com/compare/memori-vs-past-dev.md)
- [Memori vs Supermemory API + MCP](https://www.anchorterminal.com/compare/memori-vs-supermemory.md)
- [Memori vs TencentDB Agent Memory](https://www.anchorterminal.com/compare/memori-vs-tencentdb-agent-memory.md)
- [Memori vs Tokenrip](https://www.anchorterminal.com/compare/memori-vs-tokenrip.md)
- [Memori vs Zep](https://www.anchorterminal.com/compare/memori-vs-zep.md)
- [AI Memory vs Hy Memory](https://www.anchorterminal.com/compare/ai-memory-vs-hy-memory.md)
- [AI Memory vs Memori](https://www.anchorterminal.com/compare/ai-memory-vs-memori.md)
- [Context Mode Engine vs Hy Memory](https://www.anchorterminal.com/compare/context-mode-vs-hy-memory.md)
- [Context Mode Engine vs Memori](https://www.anchorterminal.com/compare/context-mode-vs-memori.md)
- [Graphicle vs Hy Memory](https://www.anchorterminal.com/compare/graphicle-vs-hy-memory.md)
- [Graphicle vs Memori](https://www.anchorterminal.com/compare/graphicle-vs-memori.md)

---

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