# Beacon vs MemMachine (slim)

> Beacon scores 70.8 (BB) to MemMachine's 60.5 (C) for agent memory. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/beacon-sh-vs-memmachine.md (~4,450 tokens) · this version ~780 tokens · JSON https://www.anchorterminal.com/compare/beacon-sh-vs-memmachine.json · canonical https://www.anchorterminal.com/compare/beacon-sh-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-18
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Beacon scores 70.8 (BB) on agent readiness against MemMachine's 60.5 (C), and leads in 4 of 7 scored categories. MemMachine leads on maintenance & community. Both do agent memory.

- Beacon: BB 70.8, rank #290 of 1557 · https://www.anchorterminal.com/tools/beacon-sh.min.md
- MemMachine: C 60.5, rank #768 of 1557 · https://www.anchorterminal.com/tools/memmachine.min.md
- Beacon, good for Developers running several coding-agent harnesses who want one local record of sessions and a reviewed memory their agents can recall. Ahead on Reliability, 78 against 51; Security & auth, 64 against 41; Payments & pricing, 75 against 60; Transparency & trust, 68 against 57. Also Agent-ready, a grade of BB or better.
- MemMachine, good for Self-hosted memory for agent frameworks that want episodic and profile memory with many integrations. Ahead on Maintenance & community, 83 against 68.

| Category | Beacon | MemMachine |
| --- | --- | --- |
| Reliability (16%) | 78 | 51 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 77 | 79 |
| Agent ergonomics (13%) | 63 | 65 |
| Security & auth (14%) | 64 | 41 |
| Payments & pricing (10%) | 75 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 68 | 83 |
| Transparency & trust (7%) | 68 | 57 |

| Fact (where they differ) | Beacon | MemMachine |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | Asymptote Labs | MemVerge, Inc. |
| Transports | stdio | HTTP, stdio, Streamable HTTP |
| Licence | MIT | Apache-2.0 |
| Tools exposed | 11 | 3 |
| Read-only variant documented | yes | no |
| Last release | 2026-11-18 | 2026-10-08 |
| Terms last updated | 2026-10-15 | no date given |
| Privacy policy last updated | 2026-10-15 | 2026-05-20 |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Popularity | 3.6k stars | 3.1k stars, 28 npm/wk, 581 PyPI/wk |

Why the edge:
- Reliability, Beacon +27: Beacon 78 (Local-software lines, as a CLI and stdio MCP server the owner runs.); MemMachine 51 (Local-software lines, as a server the owner runs.)
- Security & auth, Beacon +23: Beacon 64 (Over stdio the server runs with the user's own permissions and needs no secret.); MemMachine 41 (Framework reading for software the owner runs.)
- Payments & pricing, Beacon +15: Beacon 75 (Self-hosted rule, with the price lines read for Beacon Cloud.); MemMachine 60 (Self-hosted rule, with the price lines read for the hosted platform.)
- Maintenance & community, MemMachine +15: Beacon 68 (v1.3.64 on 18 November 2026 (30).); MemMachine 83 (v0.4.0 on PyPI on 8 October 2026, 29 days before the check (30).)
- Transparency & trust, Beacon +11: Beacon 68 (MIT, an OSI licence (30).); MemMachine 57 (Apache-2.0 (30).)
