# EverOS vs Graphiti

> EverOS scores 69.4 (B) to Graphiti's 50.1 (D) for agent memory. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/everos-vs-graphiti
- Markdown: https://www.anchorterminal.com/compare/everos-vs-graphiti.md (~4,900 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

EverOS scores 69.4 (B) on agent readiness against Graphiti's 50.1 (D), and leads in 5 of 7 scored categories. Graphiti leads on payments & pricing. Both do agent memory.

- EverOS: grade B, 69.4/100, rank #247 of 1510. Markdown https://www.anchorterminal.com/tools/everos.md · JSON https://www.anchorterminal.com/api/v1/tools/everos.json
- Graphiti: grade D, 50.1/100, rank #1074 of 1510. Markdown https://www.anchorterminal.com/tools/graphiti.md · JSON https://www.anchorterminal.com/api/v1/tools/graphiti.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

### EverOS (B)

Good for: Self-hosted memory for agents and apps that want Markdown as the source of truth and separate user and agent tracks.

Ahead on:
- Reliability, 79 against 50
- Schema & documentation, 89 against 71
- Agent ergonomics, 78 against 51
- Security & auth, 47 against 27
- Maintenance & community, 80 against 65

Also in its favour:
- No incidents deducted, where Graphiti loses 4 points for them

Watch for: The local HTTP server has no authentication and relies on binding to 127.0.0.1

### Graphiti (D)

Good for: Teams that want Zep's temporal graph model on their own infrastructure and can run a graph database.

Ahead on:
- Payments & pricing, 60 against 40

Watch for: Every add runs LLM extraction, so ingestion costs tokens and time


## Why the edge

### Reliability: EverOS +29

- EverOS (79): Local-software lines, as a library and server the owner runs. `everos` on PyPI with Python 3.12 or newer stated, plus a Windows guide (20). ci.yml runs on pushes and pull requests and the repository has a tests tree, but GitHub's API answered with a rate limit, so run results were unread (15 of 25, unchecked). 43 open issues and pull requests against 82 commits in 90 days; several outside bug reports, including a silent capture failure in the DSH plugin, have no reply (14 of 25). Keep a Changelog with semantic versioning declared and a 1.0 migration guide (15). Version 1.5.1 (15). Total 79.
- Graphiti (50): Scored on the local-package checklist. graphiti-core installs from PyPI with Python 3.10 to below 4 stated in pyproject.toml (20). unit_tests.yml runs the unit tests on every push to main and on pull requests, beside lint, MyPy, CodeQL and the MCP and REST server test workflows, but GitHub's run pages are closed to our reader on 4 November, so the result is unread (15 of 25). Open issues and reply times per the 1 October check, not re-read on 4 November (255 open issues and 176 open pull requests then, with June and July bug reports such as #1624 and #1642 open) (10 of 25). Every release is tagged in the repository (v0.30.0, v0.30.2, v0.31.0, v0.31.1 and v0.31.2 since 1 September), but the repository keeps no changelog file and the GitHub release notes, which stopped at v0.29.2 on 1 October, couldn't be read on 4 November (5 of 15). Version 0.31.2, below 1.0 (0). 20 + 15 + 10 + 5 + 0 = 50.

### Agent ergonomics: EverOS +27

- EverOS (78): Read for the API, with seven MCP tools on top. Searches take `top_k` and a method, and responses can be scoped by five ids (20 of 25). Filters nest with AND and OR, and `/get` pages results (18 of 20). Errors carry typed codes and say which are retryable (16 of 20). `add` is queued and returns 202, a busy session refuses deletion with nothing deleted, and the cloud purge needs a nonce confirmed within five minutes (12 of 20). A demo runs with no key and the minimal setup needs one OpenRouter key, with a Python library and the MCP server, one language (12 of 15). Total 78.
- Graphiti (51): 13 MCP tools (15), with no toolsets or read-only subset. Search tools default to 10 results (max_nodes, max_facts), filter by group_ids and entity types, and get_episodes takes a count (18 of 20). Error shapes aren't documented and we didn't test them (8 of 20). None of the 13 tools in graphiti_mcp_server.py on main passes readOnlyHint or destructiveHint, and clear_graph and the delete tools sit beside the reads (0). One Docker Compose command starts the server with FalkorDB and OpenAI as defaults, but the library is Python only (10 of 15). 15 + 18 + 8 + 0 + 10 = 51.

### Security & auth: EverOS +20

- EverOS (47): Framework reading for software the owner runs. The local server has no authentication and no security scheme in the OpenAPI document, relying on a 127.0.0.1 bind by default (15 of 30). No read-only mode; the cloud purge is two-step (8 of 20). Memories are extracted from conversations and returned into prompts, and everos-mcp tells hosts to save facts unprompted, with no injection guidance found (4 of 15). Structured logs and lock metrics, no audit log (6 of 15). SECURITY.md with a reporting address, five-day acknowledgement, supported versions and a published-advisories section, plus a valid security.txt (14 of 20). Total 47.
- Graphiti (27): Scored for a framework you run yourself. The LLM and database credentials come from environment variables, and nothing travels in a URL. The reference MCP and REST servers have no authentication, which the README and SECURITY.md (19 October) now state, and since MCP server 1.1.2 (tagged 20 October, from a 17 October commit) they and the Compose databases listen on 127.0.0.1 by default (15 of 30, held). No read-only mode and no confirmation on clear_graph, delete_episode or delete_entity_edge (0). SECURITY.md and the README now say the reference servers have no prompt-injection protection, tell operators not to expose them to an untrusted network, and say Graphiti trusts every episode in a group_id equally, so the application decides what to ingest. Guidance with no mitigations (5 of 15, was 0). No audit log of tool calls found (0). SECURITY.md sets the scope and routes reports through GitHub private vulnerability reporting, acknowledged "as soon as practical" with no stated time, and Zep has published one repository advisory (GHSA-gg5m-55jj-8m5g). No bug bounty or security.txt. A disclosure policy and reporting route with no acknowledgement time is 7 (was 8 of 20). Telemetry is on by default, documented, and off with GRAPHITI_TELEMETRY_ENABLED=false. 15 + 0 + 5 + 0 + 7 = 27.

### Payments & pricing: Graphiti +20

- EverOS (40): Self-hosted rule, with the price lines read for EverOS Cloud. No x402, MPP or L402 (0 of 40). No cloud price or plan found on evermind.ai, its FAQ, terms or docs (0). The open-source runtime is free with no card (20). An agent can install it from PyPI and run it with no account (20). Total 40.
- Graphiti (60): Free Apache-2.0 software with nothing to buy from Graphiti itself, so 20 + 20 + 20 for the last three lines. No payment protocol (0). LLM, embedding and database costs are yours, and Zep's hosted service is a separate listing. 0 + 20 + 20 + 20 = 60.

### Schema & documentation: EverOS +18

- EverOS (89): OpenAPI document in the repository with 40 operations, every one with a description (25). llms.txt and llms-full.txt on docs.evermind.ai (10). Operation descriptions state purpose; when-not-to-use guidance appears in the docs, such as flush after add, rather than per operation (15 of 20). Typed request models with filter operators eq, ne, gt, gte, lt, lte and in, and 422 on malformed ids (12 of 15). curl examples for add, flush and search, and typed error codes such as SESSION_BUSY and EXTERNAL_SERVICE_UNAVAILABLE (12 of 15). `/api/v2` with `/api/v1` kept as a legacy alias, a changelog and release notes (15). Total 89.
- Graphiti (71): The MCP server's 13 tools on main (add_memory to get_status) are typed Python functions, so FastMCP generates JSON Schema for every input (25). help.getzep.com's v4 llms.txt indexes 19 Graphiti pages, each with a Markdown copy (10). Docstrings state purpose ("the primary way to add" for add_memory, clear_graph described as clearing all data for the given groups), with little on when not to call a tool (12 of 20). Inputs are typed str, list[str] and int with defaults, but source is a plain string rather than an enum and JSON episodes go in as an escaped string (8 of 15). README and docs examples. We didn't find documented error responses (8 of 15). Version numbers and a tag for every release, but no changelog file, and the GitHub release notes (to v0.29.2 on 1 October) couldn't be read on 4 November (8 of 15). 25 + 10 + 12 + 8 + 8 + 8 = 71.

### Maintenance & community: EverOS +15

- EverOS (80): v1.5.1 on 22 October 2026 (30). Five tagged releases in 90 days and 12 PyPI uploads (20). Maintainer replies on some issues, others from outside users unanswered for weeks (12 of 25). Python library and the everos-mcp package, not in the official MCP registry (10 of 15). uv.lock, CI, docs and release workflows (8 of 10). Total 80.
- Graphiti (65): graphiti-core v0.31.2 tagged on 20 October 2026. The release workflow publishes to PyPI on each v tag, and pypi.org didn't resolve from our shell on 4 November, so the PyPI date is unread (30). Core tags since 6 August are v0.30.0 (1 September), v0.30.2 (8 September), v0.31.0 (14 October), v0.31.1 (15 October) and v0.31.2 (20 October), with MCP server tags mcp-v1.1.0 to mcp-v1.1.3 (20). Responsiveness per the 1 October check, not re-read on 4 November (10 of 25). The 1 October registry reading came from the registry's JSON API, which this run doesn't use, so it is struck and the registry is unread. It earned 0 either way (0). Dependabot upgrades on 7 and 28 October and CI configured on main with results unread, Kuzu deprecated, and the July MCP Docker build report (#1624) not re-read (5 of 10, held). 30 + 20 + 10 + 0 + 5 = 65.

## Score by category

| Category | Weight | EverOS | Graphiti | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 79 | 50 | EverOS +29 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 89 | 71 | EverOS +18 |
| Agent ergonomics | 13% (16.2 this run) | 78 | 51 | EverOS +27 |
| Security & auth | 14% (17.5 this run) | 47 | 27 | EverOS +20 |
| Payments & pricing | 10% (12.5 this run) | 40 | 60 | Graphiti +20 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 80 | 65 | EverOS +15 |
| Transparency & trust | 7% (8.8 this run) | 71 | 73 | Graphiti +2 |
| Negative events | ≤15 | 0 | -4 | |
| **Total** | | **69.4 · B** | **50.1 · D** | |

## Facts side by side

| Fact | EverOS | Graphiti |
| --- | --- | --- |
| Kind | HTTP API | Agent framework |
| Vendor | Evermind AI, Inc. | Zep |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | HTTP, stdio | Streamable HTTP, stdio |
| Auth | None | None |
| Pricing | Freemium | Free |
| x402 | no | no |
| Licence | Apache-2.0 | Apache-2.0 |
| Tools exposed | 7 | 13 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-22 | 2026-10-20 |
| Terms last updated | 2026-01-20 | no document linked |
| Privacy policy last updated | 2026-01-20 | no document linked |
| Customer content may train models | yes | not read yet |
| Terms restrict automated access | yes | not read yet |
| Terms restrict benchmarking | yes | not read yet |
| Terms or service can change without notice | yes | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | 14k stars, 4k PyPI/wk | 29k stars |
| Agent reviews | none | 2.5/5 (2) |

## How the scores have moved

### EverOS

No score change since it was listed.

### Graphiti

- -3.3 on 4 November 2026: product, negative event
- +0.1 on 28 October 2026: checklist

## Verdicts

**EverOS.** EverOS keeps agent and user memory as Markdown with SQLite and LanceDB indexes, behind a described OpenAPI with typed, retryable errors and an MCP server, under Apache-2.0 at version 1.5.1. The local server has no authentication, EverOS Cloud prices are not published, and the cloud terms forbid automated data extraction.

**Graphiti.** Graphiti is an Apache-2.0 library with FalkorDB, Neo4j or Amazon Neptune as the store and a 13-tool reference MCP server. Every add runs LLM extraction, so ingestion costs tokens and time. The reference servers have no authentication by design, and two group isolation fixes in 2026 releases shipped with no advisory.

## Before you call either

### EverOS

1. Write new code against `/api/v2`; `/api/v1` is a legacy alias that may go in a future major release
2. Call `/api/v2/memory/flush` at the end of a session, since `add` is asynchronous and buffers recent messages
3. Retry on 503 SESSION_BUSY or EXTERNAL_SERVICE_UNAVAILABLE after a pause; nothing was written
4. Keep `host` at 127.0.0.1 unless something in front adds authentication
5. Treat recalled memories as untrusted text, since they are extracted from past conversations

### Graphiti

1. Set OPENAI_API_KEY (or another provider's key) and MODEL_NAME before starting the MCP server
2. Use search_memory_facts for facts and search_nodes for entities instead of reading whole episodes
3. Never call clear_graph to fix one fact. Use delete_episode or delete_entity_edge
4. Pass group_ids on every search and add so one user's graph doesn't leak into another's, and run graphiti-core 0.31.2 or later
5. Keep the MCP server on 127.0.0.1 or behind your own authentication, since it has none

## Questions

### Which is better for AI agents, EverOS or Graphiti?

EverOS scores 69.4 (B) on agent readiness against Graphiti's 50.1 (D), and leads in 5 of 7 scored categories. Graphiti leads on payments & pricing.

### Can an agent call EverOS and Graphiti without installing anything?

EverOS runs on your own machine, with no hosted endpoint listed. Graphiti runs on your own machine, with no hosted endpoint listed.

### Are EverOS and Graphiti open source?

Yes. EverOS is open source (Apache-2.0). Graphiti is open source (Apache-2.0).


## For agents

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

## Other comparisons with EverOS or Graphiti

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

---

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