# Hindsight vs MemMachine (slim)

> MemMachine scores 58 (C) to Hindsight's 47.8 (D) for agent memory. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/hindsight-vs-memmachine.md (~4,750 tokens) · this version ~2,430 tokens · JSON https://www.anchorterminal.com/compare/hindsight-vs-memmachine.json · canonical https://www.anchorterminal.com/compare/hindsight-vs-memmachine
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

MemMachine scores 58 (C) on agent readiness against Hindsight's 47.8 (D), and leads in 6 of 7 scored categories. Hindsight leads on security & auth. Both do agent memory.

- Hindsight: D 47.8, rank #1129 of 1486 · https://www.anchorterminal.com/tools/hindsight.min.md
- MemMachine: C 58, rank #767 of 1486 · https://www.anchorterminal.com/tools/memmachine.min.md
- Hindsight, good for Agents that should form opinions and summaries from what they stored, such as long-running assistants or copilots that reflect on past sessions. Ahead on Security & auth, 65 against 41. Also A hosted endpoint, with nothing to install.
- MemMachine, good for Self-hosted memory for agent frameworks that want episodic and profile memory with many integrations. Ahead on Reliability, 51 against 27; Agent ergonomics, 65 against 57; Payments & pricing, 40 against 30; Transparency & trust, 57 against 50. Also No key needed to call it; Runs on your own machine; No incidents deducted, where Hindsight loses 6 points for them.

| Category | Hindsight | MemMachine |
| --- | --- | --- |
| Reliability (16%) | 27 | 51 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 78 | 79 |
| Agent ergonomics (13%) | 57 | 65 |
| Security & auth (14%) | 65 | 41 |
| Payments & pricing (10%) | 30 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 80 | 83 |
| Transparency & trust (7%) | 50 | 57 |

| Fact (where they differ) | Hindsight | MemMachine |
| --- | --- | --- |
| Vendor | Vectorize | MemVerge, Inc. |
| Hosted endpoint | `https://api.hindsight.vectorize.io` | no (local only) |
| Transports | HTTP, Streamable HTTP | HTTP, stdio, Streamable HTTP |
| Auth | OAuth or key | None |
| Pricing | Pay per use | Freemium |
| Licence | MIT | Apache-2.0 |
| Tools exposed | 27 | 3 |
| Last release | 2026-11-03 | 2026-10-08 |
| Terms last updated | couldn't be read | no date given |
| Privacy policy last updated | couldn't be read | 2026-05-20 |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | yes |
| Terms restrict benchmarking | couldn't be read | yes |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | yes |
| Popularity | 43k stars, 44k npm/wk, 227k PyPI/wk | 3.1k stars, 28 npm/wk, 581 PyPI/wk |
| Agent reviews | 3/5 (2) | none |

Why the edge:
- Reliability, MemMachine +24: Hindsight 27 (Vectorize's footer now links a status page at status.hindsight.vectorize.io, but it draws its services and incidents by script, and its server-rendered page shows no component or history, so no component history could be read (0) and no incident record (5). No rate limits found in the docs, per the 1 October check, not re-read on 4 November (docs.hindsight.vectorize.io answers robots.txt with its app page) (0). The Hindsight Cloud 0.10.0 post (21 September 2026) says recall, reflect and retain return 503 with Retry-After when capacity is full, the Python and TypeScript clients retry recall and reflect honouring it, and synchronous retain isn't retried because it could write twice, so callers should handle the 503 or use async retain. Overload handling with safe-retry guidance and no idempotency keys (12). The pricing page lists a 99.9 per cent uptime guarantee on Cloud, but no SLA document was found, which this run scores 0 (0). Hindsight Cloud is sold as a generally available service (10).); MemMachine 51 (Local-software lines, as a server the owner runs. `memmachine-server` and `memmachine-client` on PyPI with Python versions stated, a Docker image and a compose script (20). pytest, integration and installation-test workflows exist, but GitHub's API answered with a rate limit, so run results were unread (15 of 25, unchecked). 292 open issues and pull requests; the newest bug reports, including a 429 from a provider surfacing as a 500 and a 0.4.0 configuration that no longer starts, have zero to two replies (10 of 25). No changelog file, release notes only on GitHub, which weren't read, and pre-1.0 tags (6 of 15). Version 0.4.0 (0). Total 51.)
- Security & auth, Hindsight +24: Hindsight 65 (Keys can be restricted to named banks, expire after an hour to a year or never, are revocable with child keys revoked alongside, and the docs give a rotation procedure. The hosted MCP uses OAuth with PKCE under RFC 9728, or a Bearer key (30). Bank scoping limits the blast radius, but there are no read-only keys and delete_memory sits in the default tool list with no confirmation (8 of 20). `Memory Defense` screens every retain before storage. The open-source server gets regex redaction of 44 key patterns, and Enterprise adds prompt-injection blocking, 176 more token patterns and LLM-based secret detection (12 of 15). Security audit trails and SIEM webhooks are Enterprise only (5 of 15). These four lines per the 1 October check, not re-read on 4 November (docs.hindsight.vectorize.io answers robots.txt with its app page). SECURITY.md in the repository routes reports through GitHub's private advisory form, promises a response within 48 hours and follows coordinated disclosure. No security.txt (404 on 4 November), SOC 2 report or bug bounty found, and the Vanta trust centre at trust.vectorize.io couldn't be read (10 of 20, this run's value for a disclosure policy with a stated response time).); MemMachine 41 (Framework reading for software the owner runs. The server has no authentication and no security scheme in its OpenAPI document (15 of 30). No read-only mode or confirmation for deletes (5 of 20). No guidance on recalled memories as untrusted text (4 of 15). No audit log on the self-hosted server; the hosted console shows usage (5 of 15). SECURITY.md with GitHub private reporting and a two-business-day acknowledgement, with security-audit and SBOM workflows; no security.txt or certification (12 of 20). Total 41.)
- Payments & pricing, MemMachine +10: Hindsight 30 (No x402, MPP or L402. Calls on an empty balance return 402 with no payment payload (0). Per-unit prices published without a login and re-read on 4 November, retain $10 per million tokens, recall $0.75 per million, reflect $0.05 a call, Iris Extract $7.50 per million, mental model retrieval $0.25 per million and refresh $0.05 a call, storage $0.25 per million tokens a month after the first 30 days (20). The pricing page says new accounts start with $5 of free credit; whether a card is needed isn't stated (10 of 20). A person signs up in the browser to get a key (0).); MemMachine 40 (Self-hosted rule, with the price lines read for the hosted platform. No x402, MPP or L402 (0 of 40). No hosted prices found on the site or docs (0). Free to self-host with no card (20). An agent can install it from PyPI with no account (20). Total 40.)
- Agent ergonomics, MemMachine +8: Hindsight 57 (27 MCP tools on a bank-scoped URL and 30 at the root (15), with no documented way to load a subset or a read-only set. List and recall calls exist with bank scoping, and we didn't confirm page-size or token-budget limits (12 of 20). 402 tells an agent it's out of credit and 403 that the key can't reach the bank (12 of 20). No idempotency keys and no readOnlyHint or destructiveHint on the MCP tools, though retain can run asynchronously (3 of 20). Clients for Python, TypeScript and Go, and one URL per bank keeps calls simple (15). MCP and key docs per the 1 October check, not re-read on 4 November (docs.hindsight.vectorize.io answers robots.txt with its app page).); MemMachine 65 (Searches take limit and filter options for episodic and semantic results (20 of 25). Memories can be listed and filtered by scope (15 of 20). Validation errors are typed; other failures are less clear, as the 429-to-500 issue shows (10 of 20). No idempotency keys or safe-retry guidance found (5 of 20). Python and TypeScript clients and a five-line quick start, once the import is fixed (15). Total 65.)
- Transparency & trust, MemMachine +7: Hindsight 50 (The server is MIT and runs the same engine, while Cloud adds closed Enterprise extras such as the advanced detectors in `Memory Defense` (20 of 30). The privacy policy and the terms are Termly embeds that load only by script, so neither could be read on 4 November. The pricing page says memories are free to store for 30 days, billed after that, and never deleted, and that Cloud keeps daily backups. The open-source server's defaults keep LLM request traces for 1 day and audit logs and operation records with no automatic pruning. The pricing page says the self-hosted server sends no telemetry, and the server code shows only operator-configured OpenTelemetry export (10 of 30). No deprecation policy found. The changelog marks deprecations and breaking changes per release but carries no dates of its own (0). No subprocessor list or data locations found, and the trust centre couldn't be read (0).); MemMachine 57 (Apache-2.0 (30). The terms say hosted customer data is destroyed on termination, with no period, and use usage data only in aggregate; the privacy policy wasn't read (12 of 30). No deprecation policy or notices found (3 of 20). No telemetry calls found in the server or client source, and the docs don't address it (10 of 20). Total 55.)