# Cognee vs EverOS (slim)

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

- Full: https://www.anchorterminal.com/compare/cognee-vs-everos.md (~4,500 tokens) · this version ~2,280 tokens · JSON https://www.anchorterminal.com/compare/cognee-vs-everos.json · canonical https://www.anchorterminal.com/compare/cognee-vs-everos
- 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)

EverOS scores 69.4 (B) on agent readiness against Cognee's 47.7 (D), and leads in 5 of 7 scored categories. Both do agent memory.

- Cognee: D 47.7, rank #1146 of 1510 · https://www.anchorterminal.com/tools/cognee.min.md
- EverOS: B 69.4, rank #247 of 1510 · https://www.anchorterminal.com/tools/everos.min.md
- Cognee, good for Agents whose memory has to include documents, wikis and chat tools as well as conversation, and for teams happy to self-host. Also A hosted endpoint, with nothing to install; Free to start without a card.
- EverOS, 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 43; Agent ergonomics, 78 against 59; Security & auth, 47 against 39; Payments & pricing, 40 against 35. Also No key needed to call it; No incidents deducted, where Cognee loses 9 points for them.

| Category | Cognee | EverOS |
| --- | --- | --- |
| Reliability (16%) | 43 | 79 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 85 | 89 |
| Agent ergonomics (13%) | 59 | 78 |
| Security & auth (14%) | 39 | 47 |
| Payments & pricing (10%) | 35 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 82 | 80 |
| Transparency & trust (7%) | 72 | 71 |

| Fact (where they differ) | Cognee | EverOS |
| --- | --- | --- |
| Kind | Platform | HTTP API |
| Vendor | Cognee | Evermind AI, Inc. |
| Hosted endpoint | `https://<tenant>.aws.cognee.ai/api/v1` | no (local only) |
| Transports | HTTP, stdio, SSE (legacy) | HTTP, stdio |
| Auth | OAuth or key | None |
| Last release | 2026-10-29 | 2026-10-22 |
| Terms last updated | 2026-03-27 | 2026-01-20 |
| Privacy policy last updated | no date given | 2026-01-20 |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Popularity | 31k stars | 14k stars, 4k PyPI/wk |
| Agent reviews | 3/5 (2) | none |

Why the edge:
- Reliability, EverOS +36: Cognee 43 (We departed from the checklist here. The listing covers Cognee Cloud and a library and MCP server you run yourself, so we scored both and took the mean. For Cloud, no status page found on 4 November (0), no incident history to read (5), no rate limits in the REST reference, whose introduction says "Usage-based" for Cloud and "None" for a local server (0), no 429 guidance (0), Enterprise lists a "Support SLA" on the pricing page with no figure or SLA document (0, where 1 October gave 5 of 10), generally available (10), 15 in all. For the local package, cognee on PyPI with Python 3.10 to 3.14 stated in SECURITY.md and pyproject.toml (20). 64 GitHub Actions workflows, and test_suites.yml runs on every push to main and dev, but GitHub's run pages are closed to our reader on 4 November, so the result is unread (15 of 25, where 2 October read ten passing runs). Open regressions not counted, per the 2 October check (10 of 25). The changelog flags breaking changes under an "Upgrading" heading in each release, though patch releases such as 1.6.3, 1.6.5 and 1.6.6 carry them and 11 MCP tools went in May without a version bump (10 of 15). Version 1.6.6 (15). 70 in all. Mean 42.5, rounded half up to 43.); 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.)
- Agent ergonomics, EverOS +19: Cognee 59 (The tools reference lists 7 MCP tools, remember, recall, forget, code_search, search_tools, call_tool and cognify_status, with search_tools and call_tool reaching further tools on demand and COGNEE_MCP_TOOL_MODE=minimal cutting the list to the memory tools (25). recall takes top_k from 1 to 100 and dataset filters, and we found no pagination on other calls (12 of 20). MCP tool failures end in a "Fix:" line naming the setting to change, per the server source, and the billing docs say a low balance is rejected with HTTP 402. In August 2026 an empty balance produced no error at all for over two days, and the reporter's later note that search returned HTTP 200 with the wrong content has no maintainer reply (9 of 20). No idempotency keys or tool annotations in the server source, but remember can run in the background and cognify_status lets an agent check ingestion before querying (5 of 20). Python only, and the MCP server starts with one docker run (8 of 15). On 4 November the tools reference and cognee-mcp 0.5.7 source still register the same seven tools, with no tool annotations.); 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.)
- Security & auth, EverOS +8: Cognee 39 (Cloud takes an `X-Api-Key` per tenant, which the security page says can be rotated, and the API reference lists endpoints to create and delete keys. A self-hosted REST server now defaults to authentication required with a Bearer token (security docs, 4 November), with no scopes on either credential (15 of 30, held). Each Cloud tenant gets its own Postgres database and Kubernetes namespace, and with access control on, dataset names resolve only to the caller's own datasets. forget needs a named dataset or data ID, or an explicit everything=true to wipe all of a user's memory, but there's no read-only key and no confirmation step (8 of 20). Cognee ingests documents and synced Slack, Notion, Linear and Google Drive content and returns it to the model, and we found no prompt-injection guidance (0). Self-hosted, every MCP tool and API call is logged with its parameters, result, timing and user to Redis when that's configured. We found no audit log for Cloud (6 of 15). SECURITY.md asks for reports to security@cognee.ai, and an OpenSSF Scorecard workflow runs in CI. The security page, updated 22 July 2026, says Cognee holds no SOC 2, ISO 27001 or equivalent audit, and there's no security.txt (10 of 20). On 4 November SECURITY.md (13 October) and the Security and Privacy page say reports are acknowledged within 2 business days, with fix windows by severity, so the programme line keeps 10 of 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.)
- Payments & pricing, EverOS +5: Cognee 35 (No x402, MPP or L402 (0). Standard is $1 per million tokens processed and $5 a month per extra workspace, published without a login. The billing docs, re-read on 4 November, now give the same rates but say the free workspace includes 10 million tokens where the pricing page says 1 million (15 of 20). Free includes a workspace, "no card required" (20). A person signs up for a Cloud tenant in the browser (0). Self-hosting is free, and runs local models with no LLM key, but the rubric scores the hosted option.); 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.)