Memori vs past.dev

Memori 33

SDK 3.3.6 on 27 May 2026, 163 days before the check (10). No release in the 90 days to 6 November (0). Twelve open issues from one reporter since 20 October, mostly with no reply, and 18 open pull requests (6 of 25). Python and TypeScript SDKs, last released in May 2026 (12 of 15). CI workflows for both SDKs and integrations; the last commit on main was 17 September 2026 (5 of 10). Total 33.

past.dev 77

Read for a closed service. The changelog's newest entry is the week of 19 October 2026, with framework connectors, MCP deletion tools and a breaking refusal of / in data point ids (30). Seven dated weekly entries in the 90 days from 4 August (weeks of 24 August, 14, 21 and 28 September, and 5, 12 and 19 October), and the integrations post of 28 October (20). A public changelog, a community Slack and email support on Flex, none of which we tested (10 of 15). The MCP server is in the official MCP registry as dev.past/past under the past.dev domain namespace, published 30 September 2026, and official framework packages now exist on npm and PyPI, but there is no general-purpose SDK (12 of 15; was 5). The Claude Code and Codex plugin repositories are MIT with a check.yml workflow, with CI results unchecked, per the 19 October check (5 of 10). 30 + 20 + 10 + 12 + 5 = 77.

Memori 28

Hosted lines, since both modes call Memori's API. No status page found; status.memorilabs.ai did not answer and none is linked (0). No readable incident history (5). Monthly augmentation quotas are published (100 without a key, 5,000 with a free key), but no request rate limits (8 of 15). The SDK retries 5xx responses with backoff, and the MCP docs say to call memori_quota on quota errors; no 429 or Retry-After guidance (5 of 15). SLA only as a custom Enterprise term (0). No beta label on the cloud or MCP endpoint (10). Total 28.

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.

Memori 45

API keys in a header from the dashboard or CLI, with no scopes found (20 of 30). No read-only mode or per-tool restrictions (4 of 20). Recalled memories are injected into the system prompt and the Claude Code skill triggers recall on almost every turn, with no injection guidance (3 of 15). A dashboard shows memories, retrieval and usage (8 of 15). SECURITY.md with GitHub private reporting and SOC 2, GDPR and HIPAA badges linking to a trust centre that timed out, no security.txt. Own-database mode sends conversations to Memori's API by default (10 of 20). Total 45.

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.

Memori 68

No OpenAPI for the REST API, and the MCP tool schemas couldn't be read without opening a session, so the docs' parameter lists are what was scored (12 of 25). llms.txt with Markdown docs for both modes (10). Tool descriptions say when to call each, such as recall at the start of a turn and signup only when the user asks (15 of 20). Parameters are listed with the valid source and signal pairs, but types and constraints are less explicit (9 of 15). Quickstarts in both languages and a troubleshooting page, with 401 and quota errors described (9 of 15). Keep a Changelog with semantic versioning (13 of 15). Total 68.

past.dev 86

OpenAPI 3.1.0 at past.dev/openapi.json with 34 operations on 27 paths, re-read on 2 November (25). llms.txt with a "When to use" section, llms-full.txt, a Markdown copy of every page and a docs MCP server (10). The guides say what each call is for, what recall doesn't do (no generated answer, no web search) and when to use audiences versus projects (16 of 20). 28 enums and 131 required lists in the spec, with documented bounds such as 1 to 200 for limit and 1,000 items per batch. metadata is a free-form object that never filters recall (13 of 15). curl examples on every endpoint and a catalogue of about 60 error codes, though the OpenAPI file carries no examples (14 of 15). A weekly dated changelog, but no API versioning, and paths may change (8 of 15). 25 + 10 + 16 + 13 + 14 + 8 = 86.

Memori 65

Seven MCP tools with short parameter lists (22 of 25). Recall filters by project, session, date range and source (14 of 20). 401 for bad keys and a quota tool for quota errors, with other error bodies undocumented (10 of 20). No idempotency guidance or tool annotations documented (4 of 20). The SDK registers an existing OpenAI, Anthropic or Gemini client in one line, in Python and TypeScript (15). Total 65.

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.

Memori 52

Apache-2.0 per the LICENSE text, though GitHub reports it as NOASSERTION (30). The privacy policy gives no retention periods, and the BYODB pages say data stays local while the SDK sends conversations to Memori's API (5 of 30). Changelog entries but no deprecation policy or notices (5 of 20). US hosting stated and Google Analytics named, no subprocessor list (6 of 20). Total 46.

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.