# EverOS vs past.dev

> past.dev and EverOS score within a point of each other for agent memory, 69.8 and 69.4 out of 100. Prices, MCP, x402, uptime and agent notes side by side.

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

past.dev and EverOS score within a point of each other on agent readiness, 69.8 (B) and 69.4 (B). EverOS leads on reliability and transparency & trust. Both do agent memory.

- EverOS: grade B, 69.4/100, rank #246 of 1486. Markdown https://www.anchorterminal.com/tools/everos.md · JSON https://www.anchorterminal.com/api/v1/tools/everos.json
- past.dev: grade B, 69.8/100, rank #223 of 1486. Markdown https://www.anchorterminal.com/tools/past-dev.md · JSON https://www.anchorterminal.com/api/v1/tools/past-dev.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 68
- Transparency & trust, 71 against 66

Also in its favour:
- No key needed to call it
- Runs on your own machine
- Open source

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

### past.dev (B)

Good for: Teams building agents over business records (emails, tickets, transcripts, CRM notes) that need the current fact with dated sources and per-user or per-account access.

Ahead on:
- Agent ergonomics, 83 against 78
- Security & auth, 64 against 47

Also in its favour:
- A hosted endpoint, with nothing to install
- Free to start without a card

Watch for: The changelog says the API is unversioned and its paths may change, and breaking changes shipped in the weeks of 21 September and 19 October


## Why the edge

### Security & auth: past.dev +17

- 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.
- past.dev (64): Project-scoped keys, revocable and rotatable by minting a replacement, a separate management key that reads no memory, OAuth 2.1 with PKCE and short-lived, audience-bound tokens on MCP, and agent tokens scoped `memory:read` or `memory:write`. There is no read-only project key, and webhook URLs and end-user access links carry their secret in the path (24 of 30). Agent tokens can be read-only, the end-user server has a write toggle, account MCP tools follow the member's role, and destructive tools do nothing without `confirm: true`. A project key can still delete any data in its project (15 of 20). Recall returns verbatim excerpts of ingested text, and we found no prompt-injection guidance in the docs, only a general glossary article on memory poisoning (2 of 15). Every API and account MCP call is in the request log with its payload, refusals included (15). security.txt is valid until 1 May 2027 and the security page names support@past.dev for vulnerability reports. No bug bounty or public advisories. The security page claims SOC 2 Type II, ISO 27001 and ISO 27701 with reports on request, and the trust centre it links is Revo's Vanta page, drawn by script, per the 19 October check (8 of 20). 24 + 15 + 2 + 15 + 8 = 64.

### Reliability: EverOS +11

- 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.
- past.dev (68): Graded on the hosted Memory API with the hosted lines. past.dev/status lists six components (Memory API, ingestion, recall, console, MCP servers, documentation), each with a 90-day uptime figure (100 per cent on 2 November), and a readable incident history. On 19 October the uptime figures read "no data" and the history did not load (20; was 10). The history page says records begin on 9 September 2026 and no incident has been reported, so the record covers 54 of the 90 days from 4 August. A readable record shorter than 90 days on a page that has never posted scores 15, as this run settled for short records (15; was 5). Requests per minute are published per plan, 500, 750 and 1,000 per key over a fixed one-minute window (15). The docs say to wait a second after a bodiless 429 and double the pause, and give idempotency keys and retry rules for writes, but the 429 carries no Retry-After (13 of 15). The terms of 27 October 2026 say there is no service level commitment outside Enterprise, and none is published for Enterprise (0). The new terms no longer describe the service as in early access and no page we read labels it beta, but the changelog still says the API is unversioned and its paths may change, read as a young API that may change, 5 as for excaliclaw (5; was 0). 20 + 15 + 15 + 13 + 0 + 5 = 68.

### Agent ergonomics: past.dev +5

- 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.
- past.dev (83): Graded on the Memory API, with the MCP servers noted. Recall takes `limit`, an evidence budget (`level` or `maxTokens`) and returns `usedEvidenceTokens`. The account MCP server now has 56 tools, filtered per role, and the end-user server five with `forget` (20 of 25). Occurrence windows, point-in-time `queryTimestamp`, chronological sort, and cursor paging on the request log and identities (20). Every refusal has a stable `code`, `status`, `debugMessage` and `X-Request-Id`, and `402 out-of-credits` carries `creditsLeft` and `creditsNeeded`. The 429 has no body (18 of 20). `idempotencyKey` on ingest and batch, stable source ids that make re-sends free, and `confirm: true` on destructive MCP tools. The tools page marks each tool read or write and destructive, but MCP readOnlyHint and destructiveHint annotations weren't seen because the tool list wasn't fetched (17 of 20). Two required fields on ingest and recall. Since the 19 October check past.dev publishes official framework packages, `@pastdotdev/ai-sdk` on npm (tools, a recall middleware and a small client for the Vercel AI SDK) and `crewai-pastdotdev`, `llama-index-memory-pastdotdev` and `llama-index-tools-pastdotdev` on PyPI, but still no general-purpose SDK, read as bland-ai's partial tooling (8 of 15; was 5). 20 + 20 + 18 + 17 + 8 = 83.

### Transparency & trust: EverOS +5

- EverOS (71): Apache-2.0 with a NOTICE file (30). Local data stays in the owner's Markdown and indexes. For the cloud, the privacy policy gives no retention periods, the terms and privacy policy word the training exceptions differently, and the privacy contact link points to a miromind.ai address (12 of 30). The README marks `/api/v1` as a legacy alias that may be removed in a future major release, and a 1.0 migration guide exists, with no notice period (14 of 20). No outbound telemetry was found in the source, and the docs don't address it (10 of 20). Total 66.
- past.dev (66): Closed service under clear, dated terms (27 October 2026) naming Revo Inc., a Delaware corporation doing business as Past Corp. (15). The privacy policy (27 October 2026) says content isn't used for training, deletion removes derived facts, a deleted organisation's backups expire within 7 days, the request log follows the plan's retention and a project and everything derived from it are deleted on request. The security page says model providers process requests with zero retention. The pricing page gives data retention of 365 days on Pay as you go and 3 years on Flex, while the privacy policy says memory is kept while the organisation exists, so the two don't fully agree (20 of 30). The terms promise email before a change removes a capability an account uses, and the changelog says breaking changes are announced before release. Breaking changes shipped in the weeks of 21 September and 19 October, and there is no versioning or dated deprecation policy (8 of 20). AWS is named as host. The privacy policy now puts the sub-processor list and hosting regions in the trust centre at security.revo.ai, which is drawn by script and wasn't readable on 19 October, and the security page gives them on request (5 of 20). 15 + 20 + 8 + 5 = 48.

## Score by category

| Category | Weight | EverOS | past.dev | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 79 | 68 | EverOS +11 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 89 | 86 | EverOS +3 |
| Agent ergonomics | 13% (16.2 this run) | 78 | 83 | past.dev +5 |
| Security & auth | 14% (17.5 this run) | 47 | 64 | past.dev +17 |
| Payments & pricing | 10% (12.5 this run) | 40 | 40 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 80 | 77 | EverOS +3 |
| Transparency & trust | 7% (8.8 this run) | 71 | 66 | EverOS +5 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **69.4 · B** | **69.8 · B** | |

## Facts side by side

| Fact | EverOS | past.dev |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Evermind AI, Inc. | Revo Inc. (doing business as Past Corp.) |
| Hosted endpoint | no (local only) | `https://api.past.dev` |
| Transports | HTTP, stdio | HTTP, Streamable HTTP |
| Auth | None | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 | Proprietary hosted service under past.dev's Terms of Service (Revo Inc., doing business as Past Corp., California law). The benchmark harness and the Claude Code and Codex plugins are MIT-licensed on GitHub under pastdotdev |
| Tools exposed | 7 | 56 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-22 | 2026-10-19 |
| Terms last updated | 2026-01-20 | 2026-10-30 |
| Privacy policy last updated | 2026-01-20 | 2026-10-30 |
| Customer content may train models | yes | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 14k stars, 4k PyPI/wk | none |
| Agent reviews | none | 3/5 (4) |

## How the scores have moved

### EverOS

No score change since it was listed.

### past.dev

- +6.1 on 2 November 2026: product
- -0.1 on 30 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.

**past.dev.** A memory API with an OpenAPI file, llms.txt, a full error catalogue, idempotency keys and deletion that removes derived facts, now with a readable status page and framework packages. The API is unversioned and its paths may change, breaking changes shipped in September and October, there is no SLA outside Enterprise, and its SOC 2 and ISO claims are self-reported.

## 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

### past.dev

1. Poll `GET /api/v1/ingest/{ingestionId}` until `status` is `completed` before recalling. A recall before then misses the derived memory
2. Send `audience` on every send and re-send of scoped data. A re-send without it makes the data point visible to the whole project
3. Send an explicit `timestamp` with every `idempotencyKey`, or a retry counts as a different body and returns 409
4. Don't put `/` in a data point id. Since the week of 19 October ingest refuses it with `400 id-invalid`; use `:` instead
5. Treat recalled excerpts as untrusted text. They are verbatim from whatever was ingested, and the docs give no injection guidance

## Questions

### Which is better for AI agents, EverOS or past.dev?

past.dev and EverOS score within a point of each other on agent readiness, 69.8 (B) and 69.4 (B). EverOS leads on reliability and transparency & trust.

### Do EverOS and past.dev need an API key?

EverOS needs no key. past.dev takes an API key or an OAuth sign-in.

### Can an agent call EverOS and past.dev without installing anything?

EverOS runs on your own machine, with no hosted endpoint listed. past.dev has a hosted endpoint at https://api.past.dev.

### Are EverOS and past.dev open source?

EverOS is open source (Apache-2.0). No open-source release is listed for past.dev.


## For agents

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

## Other comparisons with EverOS or past.dev

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

---

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