EverOS vs past.dev

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.

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.

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.

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.