Mem0 vs Airweave
open-source · free-tier · usage-based · enterprise-custom
·open-source · free-tier · subscription · enterprise-custom
Mem0 wins · 26–7 (17 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round to Mem0A probe confirms docs.mem0.ai/llms.txt returns HTTP 200 with a proper agent-oriented summary of Mem0, and the docs also expose an OpenAPI spec, MCP server, and CLI that an agent can consume directly. Missing for 10: independent/community confirmation that an agent successfully used llms.txt in practice.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.mem0.ai/llms.txt # Mem0 > Mem0 is a memory layer for LLM agents - persistent, self-improving conte…”
- [probe] “PROBE openapi: HTTP 200 at https://docs.mem0.ai/openapi.json — contains "openapi" key”
- [probe] “official MCP server documented at https://docs.mem0.ai/platform/mem0-mcp”
- [probe] “official CLI documented at https://docs.mem0.ai/platform/cli”
Airweave hosts a working llms.txt at docs.airweave.ai/llms.txt (HTTP 200, confirmed by probe) plus markdown-appendable docs pages explicitly designed for agent consumption, and also publishes official 'skills' for Cursor, Claude Code, Gemini CLI, OpenCode, etc. so agents can self-configure. missing for 10: no independent/community confirmation that an agent successfully used llms.txt end-to-end, and no evidence of additional agent-discovery standards (e.g. skills.json manifest validation).
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.airweave.ai/llms.txt # Airweave ## Instructions for AI Agents - For clean Markdown of any page, a…”
- [claimed-docs] “Airweave publishes official skills so that agents in Cursor, Claude Code, Gemini CLI, OpenCode, and other environments can set up integratio…”
- [claimed-docs] “Airweave publishes official skills so that agents in Cursor, Claude Code, Gemini CLI, OpenCode, and other environments can set up integratio…”
- [claimed-docs] “enabling your coding agents to instantly search across all your synced apps and databases with zero additional setup required”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round to Mem0Mem0 is fundamentally API/SDK-first and documents non-interactive setup: a terminal-only account/API-key flow explicitly designed for coding agents with no email or dashboard, a CLI for add/search/list/update/delete, and a self-hostable Docker/REST stack with API keys and audit logs — all of which are naturally scriptable in CI. missing for 10: an explicit CI/CD pipeline example or GitHub Actions integration doc, and independent (non-vendor) confirmation of headless CI usage.
- [claimed-docs] “a coding agent creates its own account from the terminal and starts storing memories immediately”
- [claimed-docs] “a coding agent creates its own account from the terminal and starts storing memories immediately.”
- [claimed-docs] “Let an AI agent create its own Mem0 account and API key in four commands, with no email or dashboard needed.”
- [claimed-docs] “Four terminal commands create an account and API key. No email, no dashboard.”
- [claimed-docs] “The mem0 CLI lets you add, search, list, update, and delete memories directly from the terminal.”
- [claimed-docs] “lets you add, search, list, update, and delete memories directly from the terminal”
- [claimed-docs] “Self-host Mem0 with full control over your infrastructure and data”
- [claimed-docs] “A Docker stack with a dashboard, per-user API keys, and a request audit log.”
- [claimed-docs] “As a self-hosted server. A Docker stack with a dashboard, per-user API keys, and a request audit log.”
- [probe] “PROBE openapi: HTTP 200 at https://docs.mem0.ai/openapi.json — contains "openapi" key”
Airweave exposes a full REST API (OpenAPI spec), a CLI, and self-hostable deployment via a shell script, plus webhooks for event-driven automation and Pipedream workflow actions—all of which support running it headlessly or wiring it into automation/CI. However, there is no explicit CI/CD example, GitHub Actions template, or documented headless test-mode workflow in the evidence. missing for 10: explicit CI pipeline example/docs, headless testing/automation guide.
- [claimed-docs] “The primary use case — search any collection from your terminal”
- [claimed-docs] “git clone https://github.com/airweave-ai/airweave.git cd airweave ./start.sh”
- [claimed-docs] “If you prefer to run Airweave yourself, you can deploy it locally on macOS, Linux or WSL.”
- [claimed-docs] “Webhooks are real-time notifications that Airweave sends when things happen in your organization: syncs completing, source connections being…”
- [claimed-docs] “Instead of constantly polling the API, you register a webhook endpoint and Airweave pushes updates to you the moment they occur.”
- [claimed-docs] “The Airweave integration provides a set of actions that enable you to search your synced data to retrieve relevant context, manage your coll…”
- [probe] “PROBE openapi: HTTP 200 at https://docs.airweave.ai/openapi.json — contains "openapi" key”
- [probe] “official CLI documented at https://docs.airweave.ai/cli”
ai-native userConnect an agent via an official MCP server
weight 3 · round drawnMem0 documents an official hosted MCP server that exposes memory tools (add/search/update) to any agent, with a one-command connection setup, corroborated by a probe hit confirming the docs page exists. Missing for 10: independent/hands-on third-party verification of the MCP server working in practice beyond vendor docs.
- [claimed-docs] “The Mem0 MCP server hands your agent a set of memory tools, so it can decide for itself when to save something, look something up, or update…”
- [claimed-docs] “Connect any AI client to Mem0 using Model Context Protocol in minutes”
- [claimed-docs] “Point your clients at the hosted server with a single command”
- [probe] “official MCP server documented at https://docs.mem0.ai/platform/mem0-mcp”
Airweave is not itself an agent but a data-integration/search platform, so shipping an official MCP server is a fair axis; docs and a probe confirm a first-party MCP server implementing the Model Context Protocol so AI assistants/agents can search synced data, plus community confirmation it works well with Cursor. Missing for 10: independent hands-on verification of the MCP server's reliability/performance beyond one community anecdote.
- [claimed-docs] “The Airweave MCP server implements the Model Context Protocol to let AI assistants search your synced data.”
- [probe] “official MCP server documented at https://docs.airweave.ai/mcp-server”
- [community] “Onyx co-founder: Congratulations on the launch. It looks like Airweave works well with Cursor, something we don't have nailed down yet!”
ai-native userUse an official CLI
weight 2 · round drawnMem0 documents an official CLI that lets users add, search, list, update, and delete memories directly from the terminal, explicitly for both humans and AI agents, plus a related agent-signup flow via terminal commands. missing for 10: independent/hands-on verification of the CLI beyond vendor docs, and more detail on CLI command coverage/versioning.
- [claimed-docs] “The mem0 CLI lets you add, search, list, update, and delete memories directly from the terminal.”
- [claimed-docs] “lets you add, search, list, update, and delete memories directly from the terminal”
- [claimed-docs] “The mem0 CLI lets you add, search, list, update, and delete memories directly from the terminal. It works with the Mem0 Platfor”
- [claimed-docs] “Manage memories from your terminal, for both humans and AI agents.”
- [claimed-docs] “Let an AI agent create its own Mem0 account and API key in four commands, with no email or dashboard needed.”
- [probe] “official CLI documented at https://docs.mem0.ai/platform/cli”
Airweave documents an official CLI whose primary use case is searching any collection directly from the terminal, confirmed both in docs and via a dedicated CLI docs page probe. Missing for 10: independent/hands-on community verification of the CLI itself and more detail on its full command surface beyond search.
- [claimed-docs] “The primary use case — search any collection from your terminal”
- [probe] “official CLI documented at https://docs.airweave.ai/cli”
ai-native userDrive the product through a documented public API
weight 3 · round to Mem0Mem0 provides a well-documented REST/SDK API (openapi.json confirmed live, quickstart with Python/JS SDKs, add/search operations), plus a CLI and MCP server enabling agents to programmatically create accounts and drive memory operations without human intervention. Coverage spans platform and self-hosted API surfaces with concrete request/response examples. Missing for 10: independent third-party benchmark or hands-on verification of API robustness beyond vendor docs.
- [claimed-docs] “In about five minutes you will get an API key, store your first memory, and search it back.”
- [claimed-docs] “get an API key, then save and search a memory in Python or JavaScript”
- [claimed-docs] “client.add(messages, user_id="user123")”
- [claimed-docs] “a coding agent creates its own account from the terminal and starts storing memories immediately.”
- [claimed-docs] “Let an AI agent create its own Mem0 account and API key in four commands, with no email or dashboard needed.”
- [probe] “PROBE openapi: HTTP 200 at https://docs.mem0.ai/openapi.json — contains "openapi" key”
- [probe] “official MCP server documented at https://docs.mem0.ai/platform/mem0-mcp”
- [probe] “official CLI documented at https://docs.mem0.ai/platform/cli”
- [claimed-docs] “The mem0 CLI lets you add, search, list, update, and delete memories directly from the terminal.”
Airweave exposes a documented OpenAPI spec (openapi.json), an llms.txt for AI-native consumption, a CLI, MCP server, and REST endpoints for collections/search/webhooks, all confirmed via probes and docs. missing for 10: independent hands-on validation of API completeness/stability and public API versioning/changelog details.
- [probe] “PROBE openapi: HTTP 200 at https://docs.airweave.ai/openapi.json — contains "openapi" key”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.airweave.ai/llms.txt # Airweave ## Instructions for AI Agents - For clean Markdown of any page, a…”
- [probe] “official MCP server documented at https://docs.airweave.ai/mcp-server”
- [probe] “official CLI documented at https://docs.airweave.ai/cli”
- [claimed-docs] “The primary use case — search any collection from your terminal”
- [claimed-docs] “Webhooks are real-time notifications that Airweave sends when things happen in your organization: syncs completing, source connections being…”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round to Mem0Mem0 supports per-user/agent API keys and lets an agent self-provision its own account and key via CLI, plus entity-scoped memory (user_id/agent_id/app_id/session_id) to isolate data access, which gives some least-privilege-like scoping. However there is no documented fine-grained permission model (e.g., read-only vs write, scope restrictions per key) beyond per-user key issuance and an audit log. Missing for 10: explicit permission/scope levels on API keys, revocation/rotation controls, and independent verification of least-privilege enforcement.
- [claimed-docs] “a coding agent creates its own account from the terminal and starts storing memories immediately”
- [claimed-docs] “a coding agent creates its own account from the terminal and starts storing memories immediately.”
- [claimed-docs] “Let an AI agent create its own Mem0 account and API key in four commands, with no email or dashboard needed.”
- [claimed-docs] “The self-hosted bundle ships the REST API and a web dashboard together... per-user API keys and a request audit log.”
- [claimed-docs] “A Docker stack with a dashboard, per-user API keys, and a request audit log.”
- [claimed-docs] “Mem0's Platform API lets you separate memories for different users, agents, and apps.”
- [claimed-docs] “Scope conversations by user, agent, app, and session so memories land exactly where they belong.”
- [claimed-docs] “Stand up the Mem0 REST server and dashboard in a few minutes, with an admin account, API keys, and a live audit log included.”
Airweavenone0/10Evidence covers source connections, auth providers, direct token injection, and MCP/CLI access, but there is no mention of issuing scoped or least-privilege API keys/credentials specifically for agents. missing for 10: any documentation of scoped API key creation, permission/role-based credential issuance, or least-privilege agent access controls.
ai-native userBuild against official SDKs
weight 2 · round to Mem0Mem0 provides official Python/JavaScript SDKs with quickstart docs, an OpenAPI-backed REST API, and documented setup guides for 22+ frameworks (LangChain, CrewAI, LlamaIndex, Vercel AI SDK), all core to AI-native agentic workflows. Missing for 10: independent hands-on developer reviews specifically validating SDK ergonomics/reliability beyond vendor docs.
- [claimed-docs] “In about five minutes you will get an API key, store your first memory, and search it back.”
- [claimed-docs] “Setup guides for 22 tools, including LangChain, CrewAI, LlamaIndex, and the Vercel AI SDK.”
- [claimed-docs] “get an API key, then save and search a memory in Python or JavaScript”
- [claimed-docs] “client.add(messages, user_id="user123")”
- [claimed-docs] “Set up your Mem0 Platform account, install the SDK, and store your first memory in under five minutes.”
- [probe] “PROBE openapi: HTTP 200 at https://docs.mem0.ai/openapi.json — contains "openapi" key”
Airweave exposes a documented OpenAPI spec (implying auto-generatable SDKs), an official LlamaIndex tool-spec package (llama-index-tools-airweave) giving agents direct API access, plus CLI and MCP server for agentic use, and integrations like Pipedream actions. However there is no explicit first-party Python/TypeScript SDK documentation beyond the LlamaIndex wrapper, so full 'build against official SDKs' coverage is unclear. missing for 10: dedicated language SDK docs (Python/JS/Go), independent developer confirmation of SDK usage beyond LlamaIndex.
- [claimed-docs] “The llama-index-tools-airweave package provides an AirweaveToolSpec that gives your LlamaIndex agents access to Airweave's search capabiliti…”
- [claimed-docs] “The Airweave integration provides a set of actions that enable you to search your synced data to retrieve relevant context, manage your coll…”
- [probe] “PROBE openapi: HTTP 200 at https://docs.airweave.ai/openapi.json — contains "openapi" key”
- [probe] “official MCP server documented at https://docs.airweave.ai/mcp-server”
- [probe] “official CLI documented at https://docs.airweave.ai/cli”
ai-native userSubscribe to events via webhooks
weight 2 · round drawnMem0 documents webhooks explicitly, letting users configure HTTP POST callbacks for memory created/updated/deleted/categorized events, which is exactly a webhook subscription mechanism for agentic event-driven workflows. Missing for 10: no independent/hands-on corroboration of webhook reliability and no detail on payload schema or retry/security guarantees.
- [claimed-docs] “Webhooks enable real-time notifications for memory events in your Mem0 project.”
- [claimed-docs] “You can configure webhooks to send HTTP POST requests to your specified URLs whenever memories are created, updated, deleted, or categorized…”
- [claimed-docs] “Configure and manage webhooks to receive real-time notifications about memory events”
- [claimed-docs] “Webhooks enable real-time notifications for memory events in your Mem0 projec”
Airweave documents a dedicated webhooks system: real-time notifications pushed on events like sync completion, source connection creation, and collection updates, explicitly positioned as an alternative to polling. This directly matches the story of subscribing to events via webhooks. Missing for 10: independent/hands-on confirmation of webhook reliability and detail on signature verification/retry semantics.
- [claimed-docs] “Webhooks are real-time notifications that Airweave sends when things happen in your organization: syncs completing, source connections being…”
- [claimed-docs] “Instead of constantly polling the API, you register a webhook endpoint and Airweave pushes updates to you the moment they occur.”
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round to Mem0Mem0 automatically extracts facts from conversations and builds a graph linking people, places, and concepts, and reranks results by semantic relevance — these are forms of AI-generated structuring of raw data, but there is no documented feature that proactively surfaces 'insights' or 'suggestions' to the end user (e.g., a dashboard summary or recommendation engine); the product is positioned as memory storage/retrieval infrastructure for agents rather than an insight-generation tool. missing for 10: explicit insights/suggestions surfacing feature, evidence of proactive recommendations, independent corroboration that graph connections are presented as user-facing insights.
- [claimed-docs] “Mem0 pulls the individual facts out of the conversation and stores each one separately”
- [claimed-docs] “Mem0 Platform builds a native graph linking people, places, and concepts across your memories, with no external graph database to provision.”
- [claimed-docs] “Mem0 Platform builds a native graph linking people, places, and concepts across your memories”
- [claimed-docs] “Reorders results using deep semantic understanding to put the most relevant memories first.”
- [claimed-docs] “You ask entity-centric questions like "what do we know about Alice?" and expect facts pulled from many different conversations”
Airweavenone0/10Airweave's documented capabilities center on search/retrieval — vector search, AI-agent tool-calling search, MCP server access — for AI agents to query synced data, not on Airweave itself surfacing proactive AI-generated insights or suggestions to the end user. No evidence shows an insights/suggestions feature or dashboard; missing for 10: any proactive insight-generation capability, any UI or output described as 'suggestions' rather than query-driven retrieval.
- [claimed-docs] “An AI agent iteratively searches your data using tool calling. It searches with multiple strategies, reads full documents, navigates entity …”
- [claimed-docs] “An AI agent iteratively searches your data using tool calling. It searches with multiple strategies, reads full documents, navigates entity …”
- [claimed-docs] “Airweave lets AI agents search across company knowledge bases, cloud drives, databases, and SaaS tools in a single query.”
ai-native userOperate the product with natural-language commands
weight 2 · round to AirweaveMem0 supports natural-language queries for its 'search' operation and exposes memory tools via MCP so an agent can decide in natural language when to save/retrieve/update memories, which covers the core NL-driven interaction pattern. However, other operations (add, update, delete, CLI commands) are structured API/CLI calls rather than free-form natural-language commands, so full conversational control of the product isn't evidenced. Missing for 10: a unified NL command interface covering all memory operations (not just search), and independent hands-on evidence of agents operating purely via natural language.
- [claimed-docs] “Mem0's search operation lets agents ask natural-language questions and get back the memories that matter most.”
- [claimed-docs] “Mem0's search operation lets agents”
- [claimed-docs] “The Mem0 MCP server hands your agent a set of memory tools, so it can decide for itself when to save something, look something up, or update…”
- [claimed-docs] “lets you add, search, list, update, and delete memories directly from the terminal”
- [claimed-docs] “Manage memories from your terminal, for both humans and AI agents.”
Airweave supports natural-language operation via its MCP server, CLI, and AI-agent tool-calling search, letting agents in Cursor, Claude Code, etc. issue natural-language queries against synced data, and community feedback confirms it works well with Cursor. Missing for 10: independent hands-on verification of natural-language control beyond search/retrieval (e.g., managing connections or collections via NL) and broader third-party corroboration.
- [claimed-docs] “An AI agent iteratively searches your data using tool calling. It searches with multiple strategies, reads full documents, navigates entity …”
- [claimed-docs] “The Airweave MCP server implements the Model Context Protocol to let AI assistants search your synced data.”
- [claimed-docs] “The primary use case — search any collection from your terminal”
- [claimed-docs] “Airweave publishes official skills so that agents in Cursor, Claude Code, Gemini CLI, OpenCode, and other environments can set up integratio…”
- [community] “Onyx co-founder: Congratulations on the launch. It looks like Airweave works well with Cursor, something we don't have nailed down yet!”
- [probe] “official MCP server documented at https://docs.airweave.ai/mcp-server”
- [probe] “official CLI documented at https://docs.airweave.ai/cli”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round drawnAn OpenAPI spec is exposed (mem0-probe-2) and quickstart docs include copyable Python/JS code snippets for add/search calls (mem0-docs-25, mem0-docs-35), which is consistent with an API reference, but there is no evidence of an interactive, in-browser 'try it now' console or runnable-example sandbox tied to that OpenAPI spec. Missing for 10: explicit interactive API explorer/playground UI, evidence of live request execution from docs, and independent confirmation that examples are runnable rather than just illustrative code blocks.
- [probe] “PROBE openapi: HTTP 200 at https://docs.mem0.ai/openapi.json — contains "openapi" key”
- [claimed-docs] “get an API key, then save and search a memory in Python or JavaScript”
- [claimed-docs] “client.add(messages, user_id="user123")”
- [claimed-docs] “Set up your Mem0 Platform account, install the SDK, and store your first memory in under five minutes.”
Airweave publishes a machine-readable OpenAPI spec (probe-2) and doc pages exist for code samples (airweave-comm-5 mentions code samples on the docs site), suggesting some form of API reference, but there is no direct evidence of an interactive 'try it' console or actually runnable examples within the docs — the community note only complains about static code sample formatting, not interactivity. missing for 10: explicit documentation or screenshot of an interactive API console (e.g., Swagger/Redoc 'Try it' UI), evidence that examples can be executed in-browser, independent confirmation of runnable examples working.
- [probe] “PROBE openapi: HTTP 200 at https://docs.airweave.ai/openapi.json — contains "openapi" key”
- [community] “Code samples on the site have broken whitespace on mobile (Android/Brave) so look a bit intense. Also, the pricing is complex to reason abou…”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round drawnA direct probe confirms https://docs.mem0.ai/openapi.json returns HTTP 200 and contains an 'openapi' key, i.e. a machine-readable OpenAPI spec is downloadable, and the API is documented elsewhere for developers. Missing for 10: no explicit vendor-side documentation page linking/describing the spec's versioning or completeness beyond the raw probe.
- [probe] “PROBE openapi: HTTP 200 at https://docs.mem0.ai/openapi.json — contains "openapi" key”
- [claimed-docs] “In about five minutes you will get an API key, store your first memory, and search it back.”
- [claimed-docs] “get an API key, then save and search a memory in Python or JavaScript”
Probe evidence confirms a machine-readable OpenAPI spec is directly downloadable at https://docs.airweave.ai/openapi.json returning HTTP 200 with an 'openapi' key, and the docs also expose an llms.txt for machine-readable navigation. Missing for 10: no independent third-party confirmation of the spec's completeness/versioning beyond the probe check.
ai-native userTest against a sandbox environment without touching production data
weight 1 · round drawnMem0none0/10No evidence pack items mention a sandbox, staging, or test-mode environment distinct from production for Mem0's Platform API; self-hosting (mem0-docs-4, mem0-docs-21) offers infrastructure control but is not described as a sandbox/test environment feature. This is a fair capability to expect from an API-based memory platform, but nothing in the docs or community evidence documents it.
Airweavenone0/10No evidence of a dedicated sandbox/test environment distinct from production data. Self-hosting (docs-11, docs-14) allows running a local instance, but this is not documented as a sandbox mode for safely testing against non-production data, and no staging/test-environment feature is mentioned anywhere in the evidence.
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round drawnMem0none0/10The evidence pack shows quickstart docs, an OpenAPI spec, and various feature docs, but nothing about API versioning scheme or a documented deprecation policy. No changelog, version headers, or deprecation notices are mentioned anywhere in the pack.
Airweavenone0/10There's evidence of an OpenAPI spec existing, but nothing about API versioning scheme, version history, or a documented deprecation policy. Missing for 10: versioning scheme documentation, deprecation policy, changelog/migration guides.
- [probe] “PROBE openapi: HTTP 200 at https://docs.airweave.ai/openapi.json — contains "openapi" key”
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round to AirweaveMem0's CLI and API document per-item add/search/list/update/delete, and the Memory Export feature lets users pull structured exports of memories at once, which is the closest evidence to a bulk operation, but there is no documented batch-add, bulk-delete, or multi-item transactional endpoint. missing for 10: explicit batch/bulk add or delete API, documented multi-item transaction support, evidence of performance/testing at scale for bulk operations.
- [claimed-docs] “The Memory Export feature allows you to create structured exports of memories using customizable Pydantic schemas.”
- [claimed-docs] “create structured exports of memories using customizable Pydantic schemas”
- [claimed-docs] “lets you add, search, list, update, and delete memories directly from the terminal”
- [claimed-docs] “The mem0 CLI lets you add, search, list, update, and delete memories directly from the terminal.”
Airweave's core sync and search architecture inherently processes many items at once (source connections auto-sync entire datasets, collections span multiple sources, single queries search across large data sets), but there is no explicit documentation of a bulk API for batch creating/updating/deleting many items or connections in one call. Missing for 10: explicit bulk/batch API endpoints, evidence of bulk item management (not just sync), and any hands-on confirmation of bulk operation performance at scale.
- [claimed-docs] “A collection is a group of different data sources that you can search using a single endpoint.”
- [claimed-docs] “A source connection links a specific app or database to your collection. It handles authentication and automatically syncs data.”
- [claimed-docs] “Airweave lets AI agents search across company knowledge bases, cloud drives, databases, and SaaS tools in a single query.”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to Mem0Mem0's webhooks let external systems receive real-time HTTP POST notifications when memories are created, updated, deleted, or categorized, which is the closest thing to event-driven automation — but this is a fixed notification hook, not a user-defined 'rules engine' that lets AI-native users specify custom conditions/actions to trigger. Missing for 10: no evidence of a rules/conditions builder, no support for arbitrary trigger logic beyond CRUD events, and no in-product action execution (only outbound POSTs for external systems to act on).
- [claimed-docs] “Webhooks enable real-time notifications for memory events in your Mem0 project.”
- [claimed-docs] “You can configure webhooks to send HTTP POST requests to your specified URLs whenever memories are created, updated, deleted, or categorized…”
- [claimed-docs] “Configure and manage webhooks to receive real-time notifications about memory events”
- [claimed-docs] “Webhooks enable real-time notifications for memory events in your Mem0 projec”
Airweave offers webhooks that push real-time event notifications (sync completed, connection created, collection updated) rather than a true rule engine where users define conditional triggers that automatically execute actions inside the product; actual automation logic must be built externally (e.g., via Pipedream workflows) that consume these events. missing for 10: a native rule/trigger-condition builder, support for user-defined conditional logic, and evidence of actions being executed automatically by Airweave itself rather than just notifying external systems.
- [claimed-docs] “Webhooks are real-time notifications that Airweave sends when things happen in your organization: syncs completing, source connections being…”
- [claimed-docs] “Instead of constantly polling the API, you register a webhook endpoint and Airweave pushes updates to you the moment they occur.”
- [claimed-docs] “The Airweave integration provides a set of actions that enable you to search your synced data to retrieve relevant context, manage your coll…”
Data lifecycle — stories about data lifecycle in this arenaData lifecycle
Stories about data lifecycle in this arena
Forgetting
platform-engineerDelete a user's memories on demand — single memory, per-entity, or full erasure — to satisfy privacy requirements
weight 2 · round to Mem0Mem0 documents a CLI and API that can add, search, list, update, and delete memories, and its entity-scoped memory model (user_id/agent_id/app_id) lets memories be scoped so a target audience can be identified for deletion. However, the evidence never explicitly documents a bulk 'delete all memories for a user_id' or full-erasure/right-to-be-forgotten endpoint distinct from per-memory delete, and expiration is explicitly called out as non-deletion ('Nothing is deleted'). Missing for 10: explicit bulk/per-entity erasure API or docs (e.g., delete_all by user_id), compliance-oriented erasure guarantees, and independent confirmation that full erasure actually removes underlying data/embeddings.
- [claimed-docs] “The mem0 CLI lets you add, search, list, update, and delete memories directly from the terminal.”
- [claimed-docs] “lets you add, search, list, update, and delete memories directly from the terminal”
- [claimed-docs] “The mem0 CLI lets you add, search, list, update, and delete memories directly from the terminal. It works with the Mem0 Platfor”
- [claimed-docs] “Manage memories from your terminal, for both humans and AI agents.”
- [claimed-docs] “Scope conversations by user, agent, app, and session so memories land exactly where they belong.”
- [claimed-docs] “Mem0's Platform API lets you separate memories for different users, agents, and apps.”
- [claimed-docs] “Set an expiration date on a Mem0 memory and it stops surfacing in search once that date passes. Nothing is deleted.”
- [claimed-docs] “Set an expiration date on a Mem0 memory and it stops surfacing in search once that date passes. Nothing is deleted. Works on Platform and Op…”
Airweavenone0/10No evidence of deletion capabilities for memories/entities/users — the pack covers syncing, search, MCP, CLI, webhooks, and connectors, but nothing about deleting or erasing synced data on demand. This is a fair capability for a data-sync/RAG platform to expose (e.g., for GDPR compliance) given it stores user data, so the axis applies, but no evidence supports it.
developerMake memories expire or decay — via TTL, expiration dates, or recency weighting — so stale facts stop surfacing
weight 2 · round to Mem0Mem0 documents a first-class expiration_date feature that stops memories from surfacing once the date passes without deleting them, working on both Platform and Open Source (mem0-docs-11, mem0-docs-19, mem0-docs-37, mem0-docs-50, mem0-docs-58). This directly satisfies the 'expiration date' part of the story. Missing for 10: explicit TTL (duration-based) configuration syntax, recency-weighting/decay scoring in search ranking, and independent/hands-on corroboration beyond vendor docs.
- [claimed-docs] “Set an expiration_date on a memory and Mem0 stops surfacing it once that date passes”
- [claimed-docs] “Set an expiration date on a Mem0 memory and it stops surfacing in search once that date passes. Nothing is deleted.”
- [claimed-docs] “Set an expiration_date on a memory and Mem0 stops surfacing it once that date passes, so you don't need a cleanup job hunting for rows to de…”
- [claimed-docs] “Set an expiration date on a Mem0 memory and it stops surfacing in search once that date passes. Nothing is deleted. Works on Platform and Op…”
- [claimed-docs] “Set an expiration date on a Mem0 memory and it stops surfacing in search once that date passes.”
Airweavenone0/10Airweave's docs cover data sync, search modes, MCP/CLI integrations, and connectors, but there is no mention of TTL, expiration dates, recency weighting, or any mechanism to decay or expire stale data/memories. Missing for 10: TTL/expiration configuration, recency-based scoring or decay, any lifecycle policy documentation.
Portability
platform-engineerExport memories in a machine-readable format so the memory store is portable and not a lock-in trap
weight 2 · round to Mem0Mem0 documents a dedicated Memory Export feature that creates structured exports of memories using customizable Pydantic schemas, and separately offers a self-hosted open-source deployment giving full ownership of the data and stack, both directly addressing the portability/lock-in concern. Missing for 10: no independent/hands-on verification of export fidelity or completeness, and no documented bulk import/migration tooling to move exported data between Platform and self-hosted stores.
- [claimed-docs] “The Memory Export feature allows you to create structured exports of memories using customizable Pydantic schemas.”
- [claimed-docs] “create structured exports of memories using customizable Pydantic schemas”
- [claimed-docs] “Export memories in a structured format using customizable Pydantic schemas”
- [claimed-docs] “Mem0 Open Source is the same memory engine as the Platform, running on your own infrastructure. You own the stack, the data, and every compo…”
- [claimed-docs] “Self-host Mem0 with full control over your infrastructure and data”
- [claimed-docs] “Mem0 Open Source is the same memory engine as the Platform, running on your own infrastructure. You own the stack”
Airweavenone0/10Evidence covers ingestion (source connections), search (vector/agentic), MCP server, CLI, webhooks, and self-hosting, but nothing describes an export mechanism or machine-readable dump of stored memories/collections for portability. Self-hosting (docker-compose) implies some data ownership but does not demonstrate an explicit export feature. missing for 10: documented export/dump endpoint or CLI command, evidence of a standard export format (e.g., JSON/CSV), any migration or data-portability guide.
- [claimed-docs] “If you prefer to run Airweave yourself, you can deploy it locally on macOS, Linux or WSL.”
- [claimed-docs] “git clone https://github.com/airweave-ai/airweave.git cd airweave ./start.sh”
- [probe] “PROBE openapi: HTTP 200 at https://docs.airweave.ai/openapi.json — contains "openapi" key”
Deployment self host — stories about deployment self host in this arenaDeployment self host
Stories about deployment self host in this arena
Self host
developerRun the memory layer fully locally — embedded in-process or against local models — without any cloud dependency
weight 1 · round to Mem0Mem0's open-source docs clearly support self-hosting the memory engine (Docker REST server, dashboard, own infrastructure) rather than relying on the Platform SaaS, per mem0-docs-4/21/22/46/28/54. However, none of the evidence confirms an embedded in-process mode or explicit support for local embedding/LLM backends (e.g., Ollama) that would eliminate all cloud calls — the quickstart and core examples default to hosted API keys and cloud model calls. Missing for 10: explicit documentation of local/offline model backends, confirmation that vector store and embedder can run fully in-process without any external API calls, and independent verification of a no-cloud-dependency deployment.
- [claimed-docs] “Mem0 Open Source is the same memory engine as the Platform, running on your own infrastructure. You own the stack, the data, and every compo…”
- [claimed-docs] “Self-host Mem0 with full control over your infrastructure and data”
- [claimed-docs] “A Docker stack with a dashboard, per-user API keys, and a request audit log.”
- [claimed-docs] “Mem0 Open Source is the same memory engine as the Platform, running on your own infrastructure. You own the stack”
- [claimed-docs] “Stand up the Mem0 REST server and dashboard in a few minutes, with an admin account, API keys, and a live audit log included.”
- [claimed-docs] “Stand up the Mem0 REST server and dashboard in a few minutes, with an admin account, API keys, and a live audit log”
- [claimed-docs] “The self-hosted bundle ships the REST API and a web dashboard together... per-user API keys and a request audit log.”
Airweave documents self-hosting via docker-compose (`./start.sh`) on macOS/Linux/WSL, showing a local deployment path, but there is no evidence it can run embedded in-process (as a library) or configured against local embedding/LLM models to avoid all cloud dependency — the docs describe it as a service with source connectors, vector DB, and search API rather than an embeddable local-only memory layer. missing for 10: evidence of in-process/embedded mode, evidence of local-model (non-cloud) embedding/LLM configuration, confirmation no external API calls are required once self-hosted.
- [claimed-docs] “git clone https://github.com/airweave-ai/airweave.git cd airweave ./start.sh”
- [claimed-docs] “If you prefer to run Airweave yourself, you can deploy it locally on macOS, Linux or WSL.”
platform-engineerSelf-host the memory layer from open-source code (e.g. via Docker) on infrastructure I control
weight 3 · round to AirweaveMem0 docs explicitly describe an open-source self-hosted bundle ('same memory engine as the Platform, running on your own infrastructure') delivered as a Docker stack with REST API, dashboard, per-user API keys, and audit log, giving platform engineers full infra control. Missing for 10: independent/hands-on confirmation of the Docker deployment working in practice and details on infra requirements (e.g., DB/vector store provisioning) beyond first-party docs.
- [claimed-docs] “Mem0 Open Source is the same memory engine as the Platform, running on your own infrastructure. You own the stack, the data, and every compo…”
- [claimed-docs] “Self-host Mem0 with full control over your infrastructure and data”
- [claimed-docs] “A Docker stack with a dashboard, per-user API keys, and a request audit log.”
- [claimed-docs] “The self-hosted bundle ships the REST API and a web dashboard together... per-user API keys and a request audit log.”
- [claimed-docs] “Stand up the Mem0 REST server and dashboard in a few minutes, with an admin account, API keys, and a live audit log included.”
- [claimed-docs] “As a self-hosted server. A Docker stack with a dashboard, per-user API keys, and a request audit log.”
- [claimed-docs] “Mem0 Open Source is the same memory engine as the Platform, running on your own infrastructure. You own the stack”
- [claimed-docs] “Stand up the Mem0 REST server and dashboard in a few minutes, with an admin account, API keys, and a live audit log”
Docs explicitly provide a git clone + ./start.sh workflow for local self-hosted deployment on macOS/Linux/WSL, indicating Docker-based open-source self-hosting is supported. Missing for 10: explicit confirmation of production-grade/cloud self-host guidance (beyond local dev) and independent hands-on verification of the self-hosted deployment succeeding.
- [claimed-docs] “git clone https://github.com/airweave-ai/airweave.git cd airweave ./start.sh”
- [claimed-docs] “If you prefer to run Airweave yourself, you can deploy it locally on macOS, Linux or WSL.”
Graph entity memory — stories about graph entity memory in this arenaGraph entity memory
Stories about graph entity memory in this arena
Knowledge graph
ml-engineerStore memories as a knowledge graph of entities and relationships so multi-hop and entity-centric questions are answerable
weight 3 · round to Mem0Mem0 Platform explicitly builds a native graph linking entities, places, and concepts across memories with no external graph database required, directly supporting multi-hop and entity-centric queries like what do we know about Alice. Docs describe automatic graph construction without schema definition, replacing earlier Neo4j-based integration. missing for 10: independent or hands-on verification of graph memory multi-hop retrieval accuracy, and no benchmark showing entity-relationship correctness
- [claimed-docs] “Mem0 Platform automatically organizes your memories into a graph... with no external graph database to provision.”
- [claimed-docs] “Graph Memory is built in. There is no Neo4j, Memgraph, or other graph store to deploy, no connection strings to manage, and nothing to enabl…”
- [claimed-docs] “Earlier versions connected an external graph database (Neo4j and others) and exposed a relations field. Mem0 now builds the graph itself fro…”
- [claimed-docs] “You ask entity-centric questions like "what do we know about Alice?" and expect facts pulled from many different conversations”
- [claimed-docs] “Mem0 Platform builds a native graph linking people, places, and concepts across your memories, with no external graph database to provision.”
- [claimed-docs] “You previously used an external graph store and want the same cross-memory connections with zero infrastructure”
- [claimed-docs] “Mem0 Platform automatically organizes your memories into a graph... without you defining any schema.”
- [claimed-docs] “Mem0 Platform builds a native graph linking people, places, and concepts across your memories”
Airweavenone0/10Airweave's docs describe vector search and an agent that can 'navigate entity hierarchies (parent/child/sibling)', but this is document/entity hierarchy navigation within a RAG pipeline, not a knowledge graph of entities and relationships designed for multi-hop, entity-centric reasoning. There is no mention of a graph database, relationship modeling, or multi-hop query capability.
- [claimed-docs] “An AI agent iteratively searches your data using tool calling. It searches with multiple strategies, reads full documents, navigates entity …”
- [claimed-docs] “An AI agent iteratively searches your data using tool calling. It searches with multiple strategies, reads full documents, navigates entity …”
- [claimed-docs] “Direct vector search. Use when speed is critical (~0.5sec).”
ml-engineerTrack when facts became valid or invalid (temporal reasoning) so the memory distinguishes current from outdated information
weight 2 · round to Mem0Mem0 supports manual expiration_date so a memory stops surfacing after a set date, and it can update existing facts, but there is no documented capability to automatically detect when a fact becomes invalid/outdated (e.g., contradiction detection, temporal versioning, or 'valid from/until' metadata) — the expiration mechanism is a manual TTL, not temporal reasoning. Missing for 10: automatic invalidation of superseded facts, tracking validity windows for graph relations, and any evidence of reasoning about fact recency versus outdatedness.
- [claimed-docs] “Set an expiration_date on a memory and Mem0 stops surfacing it once that date passes”
- [claimed-docs] “Set an expiration date on a Mem0 memory and it stops surfacing in search once that date passes. Nothing is deleted.”
- [claimed-docs] “Set an expiration_date on a memory and Mem0 stops surfacing it once that date passes, so you don't need a cleanup job hunting for rows to de…”
- [claimed-docs] “Set an `expiration_date` on a memory and Mem0 stops surfacing it once that date passes”
- [claimed-docs] “Set an expiration date on a Mem0 memory and it stops surfacing in search once that date passes. Nothing is deleted. Works on Platform and Op…”
- [claimed-docs] “Set an expiration date on a Mem0 memory and it stops surfacing in search once that date passes.”
- [claimed-docs] “Earlier versions connected an external graph database (Neo4j and others) and exposed a relations field. Mem0 now builds the graph itself fro…”
Airweavenone0/10No evidence Airweave tracks fact validity intervals or temporal versioning of entities; docs describe sync, search strategies, and entity hierarchy navigation but nothing about time-bound validity or invalidation of facts. Missing for 10: any mention of temporal metadata, valid/invalid time tracking, or versioned fact history.
Schema customization
ml-engineerCustomize the memory schema — entity types, edge types, or ontology — to match my domain
weight 1 · round drawnMem0none0/10Mem0's docs explicitly state Graph Memory is fully automatic and built 'without you defining any schema' (mem0-docs-42), with no external graph DB, connection strings, or relations field to configure (mem0-docs-23, mem0-docs-24). There is no evidence of any API, config, or ontology mechanism letting an ml-engineer define custom entity or edge types.
- [claimed-docs] “Mem0 Platform automatically organizes your memories into a graph... without you defining any schema.”
- [claimed-docs] “Graph Memory is built in. There is no Neo4j, Memgraph, or other graph store to deploy, no connection strings to manage, and nothing to enabl…”
- [claimed-docs] “Earlier versions connected an external graph database (Neo4j and others) and exposed a relations field. Mem0 now builds the graph itself fro…”
- [claimed-docs] “Mem0 Platform builds a native graph linking people, places, and concepts across your memories, with no external graph database to provision.”
Airweavenone0/10Airweave's evidence describes collections, source connections, vector/agentic search, MCP, CLI, and webhooks, but nothing addresses customizing entity types, edge types, or an ontology/schema for a graph-entity memory model — Airweave appears to use a fixed sync/search architecture rather than an editable knowledge-graph schema. Missing for 10: any mention of entity/edge type definitions, schema customization API, or ontology configuration.
- [claimed-docs] “A collection is a group of different data sources that you can search using a single endpoint.”
- [claimed-docs] “A source connection links a specific app or database to your collection. It handles authentication and automatically syncs data.”
- [claimed-docs] “An AI agent iteratively searches your data using tool calling. It searches with multiple strategies, reads full documents, navigates entity …”
Memory recall quality — stories about memory recall quality in this arenaMemory recall quality
Stories about memory recall quality in this arena
Agent memory
ai-native userMy agent can manage its own memory mid-conversation — adding, searching, updating, and deleting memories through tools or API calls it invokes itself
weight 3 · round to Mem0Mem0 documents an MCP server that hands agents add/search/update memory tools they can invoke themselves, a CLI supporting add/search/list/update/delete, and a flow for a coding agent to self-provision an account and start storing memories mid-session — directly matching the story of self-directed, tool-invoked memory management. Missing for 10: independent/hands-on verification that agents reliably invoke delete/update mid-conversation in practice, and explicit API-level delete examples beyond CLI mentions.
- [claimed-docs] “The Mem0 MCP server hands your agent a set of memory tools, so it can decide for itself when to save something, look something up, or update…”
- [claimed-docs] “The mem0 CLI lets you add, search, list, update, and delete memories directly from the terminal.”
- [claimed-docs] “lets you add, search, list, update, and delete memories directly from the terminal”
- [claimed-docs] “a coding agent creates its own account from the terminal and starts storing memories immediately.”
- [claimed-docs] “Let an AI agent create its own Mem0 account and API key in four commands, with no email or dashboard needed.”
- [probe] “official MCP server documented at https://docs.mem0.ai/platform/mem0-mcp”
- [claimed-docs] “You send conversation turns to `add`, then call `search` before the next model request to fetch relevant context.”
Airweavenone0/10Airweave's documented capability is agentic *search* over synced external data sources (docs-4, docs-5, docs-17) and syncing/connecting data, not an agent-writable memory store. There is no evidence of an agent invoking add/update/delete operations on memories mid-conversation — data flows in via source connections/syncs, not via agent tool calls for memory CRUD.
- [claimed-docs] “An AI agent iteratively searches your data using tool calling. It searches with multiple strategies, reads full documents, navigates entity …”
- [claimed-docs] “The Airweave MCP server implements the Model Context Protocol to let AI assistants search your synced data.”
- [claimed-docs] “A source connection links a specific app or database to your collection. It handles authentication and automatically syncs data.”
- [claimed-docs] “Webhooks are real-time notifications that Airweave sends when things happen in your organization: syncs completing, source connections being…”
Benchmarks
ml-engineerSee published memory-quality benchmark results (e.g. LongMemEval, LoCoMo) backing the product's recall-accuracy claims
weight 2 · round drawnMem0none0/10No evidence of any published benchmark results (LongMemEval, LoCoMo, or similar) or recall-accuracy metrics anywhere in the docs or community sources; the pack only covers feature descriptions and setup guides. missing for 10: any benchmark citation, LongMemEval/LoCoMo results, accuracy/recall metrics, third-party evaluation.
Airweavenone0/10No published benchmark results (e.g. LongMemEval, LoCoMo) or quantitative recall-accuracy metrics appear anywhere in the evidence; only a single anecdotal HN comment claims superior 'retrieval accuracy' with no data. missing for 10: published benchmark suite results, comparison methodology, any quantitative recall/accuracy numbers.
- [community] “Had meetings with a ton of MCP-server providers, no one came close to Airweave’s retrieval accuracy. I even tried Zapier and similar large c…”
Core memory
developerAdd memories from conversations and retrieve them later with semantic search, so context persists across sessions
weight 3 · round to Mem0Docs clearly describe the core add/search workflow (client.add, search by natural language, scoping by user/session) that persists memories across sessions, and this is corroborated by community reports of using it in production for exactly this purpose. Missing for 10: independent benchmarking of recall/semantic-search quality and long-term persistence beyond vendor docs.
- [claimed-docs] “Store facts once, then retrieve them by query”
- [claimed-docs] “Mem0's search operation lets agents ask natural-language questions and get back the memories that matter most.”
- [claimed-docs] “Mem0 pulls the individual facts out of the conversation and stores each one separately”
- [claimed-docs] “client.add(messages, user_id="user123")”
- [claimed-docs] “You send conversation turns to `add`, then call `search` before the next model request to fetch relevant context.”
- [claimed-docs] “Retrieve relevant memories from Mem0 using powerful semantic and filtered search capabilities.”
- [community] “Congrats on the launch. Adding a memory layer to LLMs is a real painpoint. I've been experimenting with mem0 and it solves a real problem th…”
- [community] “Memory is extremely useful and almost a requirement when it comes to building next level agents and Mem0 is probably the best designed/easie…”
- [community] “We looked at Mem0, Letta/MemGPT, and similar memory solutions. They all solve storing facts from conversations - key-value memory with seman…”
Airweavenone0/10Airweave's documented model is syncing external data sources (Slack, GitHub, Drive, databases) into collections and then searching them via vector/agentic search, not an explicit API for adding conversational memories and retrieving them for session persistence. None of the evidence describes a 'store this conversation turn' or memory-write primitive, or session-context persistence semantics — missing for 10: an add-memory/write API for conversational turns, evidence of session-scoped recall, and any first-party or community confirmation of using Airweave as a conversation memory layer.
- [claimed-docs] “A collection is a group of different data sources that you can search using a single endpoint.”
- [claimed-docs] “Direct vector search. Use when speed is critical (~0.5sec).”
- [claimed-docs] “An AI agent iteratively searches your data using tool calling. It searches with multiple strategies, reads full documents, navigates entity …”
- [claimed-docs] “Airweave lets AI agents search across company knowledge bases, cloud drives, databases, and SaaS tools in a single query.”
developerRely on the memory layer to update, supersede, or merge memories when new information contradicts what was stored
weight 2 · round to Mem0Docs confirm an 'update' operation exists (CLI and API can update/delete memories) and webhooks fire on update events, implying the system does modify stored memories over time, but there is no explicit documentation describing automatic contradiction detection, superseding, or merging logic when new facts conflict with old ones. missing for 10: explicit description of conflict/contradiction detection, merge algorithm details, and independent hands-on evidence that Mem0 correctly resolves contradictory facts.
- [claimed-docs] “The mem0 CLI lets you add, search, list, update, and delete memories directly from the terminal.”
- [claimed-docs] “lets you add, search, list, update, and delete memories directly from the terminal”
- [claimed-docs] “The mem0 CLI lets you add, search, list, update, and delete memories directly from the terminal. It works with the Mem0 Platfor”
- [claimed-docs] “Manage memories from your terminal, for both humans and AI agents.”
- [claimed-docs] “You can configure webhooks to send HTTP POST requests to your specified URLs whenever memories are created, updated, deleted, or categorized…”
- [claimed-docs] “Configure and manage webhooks to receive real-time notifications about memory events”
- [claimed-docs] “Mem0 pulls the individual facts out of the conversation and stores each one separately”
Airweavenone0/10Airweave is a data-sync/search platform that indexes and syncs source data via connectors and search endpoints; the evidence describes syncing, webhooks, and search strategies but contains no mention of a memory layer that detects contradictions, supersedes, or merges conflicting stored facts. This is an applicable axis for a retrieval/knowledge system, but no evidence shows such conflict-resolution or memory-update logic exists.
- [claimed-docs] “A source connection links a specific app or database to your collection. It handles authentication and automatically syncs data.”
- [claimed-docs] “Webhooks are real-time notifications that Airweave sends when things happen in your organization: syncs completing, source connections being…”
- [claimed-docs] “Instead of constantly polling the API, you register a webhook endpoint and Airweave pushes updates to you the moment they occur.”
Retrieval controls
developerSteer retrieval with metadata filters, keyword/hybrid search modes, or reranking instead of accepting a single fixed similarity search
weight 2 · round to Mem0Mem0 docs confirm metadata-style filtering (user/agent/app/session scoping) and a dedicated reranking feature ('Advanced memory search with intelligent reranking') alongside 'semantic and filtered search capabilities', showing retrieval can be steered beyond plain similarity search. However, there is no documented keyword or hybrid (lexical+vector) search mode, and no independent benchmark validating reranking quality. Missing for 10: explicit keyword/hybrid search mode, third-party evidence of retrieval-tuning effectiveness.
- [claimed-docs] “Reorders results using deep semantic understanding to put the most relevant memories first.”
- [claimed-docs] “Reranking Reorders results using deep semantic understanding to put the most relevant memories first.”
- [claimed-docs] “Advanced memory search with intelligent reranking for precise results”
- [claimed-docs] “Retrieve relevant memories from Mem0 using powerful semantic and filtered search capabilities.”
- [claimed-docs] “Mem0's Platform API lets you separate memories for different users, agents, and apps.”
- [claimed-docs] “Scope conversations by user, agent, app, and session so memories land exactly where they belong.”
Airweave documents two retrieval modes—fast direct vector search and an agentic iterative search that reads full documents and navigates entity hierarchies—giving developers some steering beyond a single fixed similarity search, but there is no explicit documentation of metadata filters, keyword/hybrid search, or a reranking step. missing for 10: metadata filter parameters, keyword/hybrid search mode, explicit reranking mechanism, independent verification of these controls.
- [claimed-docs] “Direct vector search. Use when speed is critical (~0.5sec).”
- [claimed-docs] “An AI agent iteratively searches your data using tool calling. It searches with multiple strategies, reads full documents, navigates entity …”
- [claimed-docs] “An AI agent iteratively searches your data using tool calling. It searches with multiple strategies, reads full documents, navigates entity …”
- [claimed-docs] “Direct vector search. Use when speed is critical (\~0.5sec).”
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round drawnMem0 is API/CLI/MCP-first: docs show a full REST API (OpenAPI spec), a CLI that can add/search/list/update/delete memories, and an MCP server exposing memory tools to agents, suggesting core operations (add, search, update, delete, scope by user/agent, webhooks, export, expiration) are all reachable via API rather than only through the dashboard. However, the dashboard is described as offering audit logs and API-key management, and there's no explicit evidence enumerating every UI-only feature and confirming full parity, so full API/UI equivalence isn't directly demonstrated. Missing for 10: an explicit comparison or docs statement confirming every dashboard feature (e.g., audit log viewing, key management, graph visualization) is also exposed via API, and independent confirmation of parity.
- [claimed-docs] “The mem0 CLI lets you add, search, list, update, and delete memories directly from the terminal.”
- [claimed-docs] “lets you add, search, list, update, and delete memories directly from the terminal”
- [probe] “PROBE openapi: HTTP 200 at https://docs.mem0.ai/openapi.json — contains "openapi" key”
- [probe] “official MCP server documented at https://docs.mem0.ai/platform/mem0-mcp”
- [probe] “official CLI documented at https://docs.mem0.ai/platform/cli”
- [claimed-docs] “The self-hosted bundle ships the REST API and a web dashboard together... per-user API keys and a request audit log.”
- [claimed-docs] “Stand up the Mem0 REST server and dashboard in a few minutes, with an admin account, API keys, and a live audit log included.”
Airweave's docs describe collections, source connections, search, and sync management as API/CLI-first concepts, and an OpenAPI spec plus CLI and MCP server are documented, implying most functionality is API-accessible. However, no evidence explicitly confirms full parity between UI and API (e.g., whether every dashboard action like billing, org settings, or Airweave Connect widget configuration is also API-exposed). Missing for 10: an explicit parity statement or audit showing all UI features are API-reachable, and independent confirmation from users exercising the API directly.
- [probe] “PROBE openapi: HTTP 200 at https://docs.airweave.ai/openapi.json — contains "openapi" key”
- [probe] “official CLI documented at https://docs.airweave.ai/cli”
- [claimed-docs] “A collection is a group of different data sources that you can search using a single endpoint.”
- [claimed-docs] “A source connection links a specific app or database to your collection. It handles authentication and automatically syncs data.”
- [claimed-docs] “The primary use case — search any collection from your terminal”
ai-native userExport all of my data in open formats and leave
weight 3 · round to Mem0Mem0 offers a Memory Export feature using customizable Pydantic schemas, a CLI to list/export memories, and self-hosted open-source deployment giving full data ownership, which together support exporting and leaving with your data. However, the export feature is schema-based/structured rather than a documented fully-open standard format, and there's no explicit bulk 'export all data and delete account' workflow or independent confirmation of export completeness. missing for 10: evidence of a full bulk export in a standard open format (e.g., JSON/CSV dump of entire account), confirmation of data portability across the graph/vector layers, and independent/hands-on verification that exports are complete and truly open.
- [claimed-docs] “The Memory Export feature allows you to create structured exports of memories using customizable Pydantic schemas.”
- [claimed-docs] “create structured exports of memories using customizable Pydantic schemas”
- [claimed-docs] “Export memories in a structured format using customizable Pydantic schemas”
- [claimed-docs] “The mem0 CLI lets you add, search, list, update, and delete memories directly from the terminal.”
- [claimed-docs] “Manage memories from your terminal, for both humans and AI agents.”
- [claimed-docs] “Mem0 Open Source is the same memory engine as the Platform, running on your own infrastructure. You own the stack, the data, and every compo…”
- [claimed-docs] “Self-host Mem0 with full control over your infrastructure and data”
- [claimed-docs] “Mem0 Open Source is the same memory engine as the Platform, running on your own infrastructure. You own the stack”
Airweave is open-source and self-hostable (git clone, ./start.sh) and exposes a documented OpenAPI/CLI surface, giving some data portability and avoiding lock-in, but there is no explicit documented bulk-export feature or open-format export tooling for a user's synced data. missing for 10: explicit data export/backup feature, documented open export formats, evidence of a 'leave and take your data' workflow.
- [claimed-docs] “git clone https://github.com/airweave-ai/airweave.git cd airweave ./start.sh”
- [claimed-docs] “If you prefer to run Airweave yourself, you can deploy it locally on macOS, Linux or WSL.”
- [probe] “PROBE openapi: HTTP 200 at https://docs.airweave.ai/openapi.json — contains "openapi" key”
- [probe] “official CLI documented at https://docs.airweave.ai/cli”
ai-native userRead the product's source under an open license
weight 2 · round to AirweaveDocs confirm a genuine 'Mem0 Open Source' offering that runs on your own infrastructure and gives you 'the stack, the data, and every component,' implying source availability, but no evidence pack item names the actual license (e.g., Apache/MIT) or links to a public repository for verification. missing for 10: explicit license name, link to source repository, independent confirmation of license terms.
- [claimed-docs] “Mem0 Open Source is the same memory engine as the Platform, running on your own infrastructure. You own the stack, the data, and every compo…”
- [claimed-docs] “Self-host Mem0 with full control over your infrastructure and data”
- [claimed-docs] “Mem0 Open Source is the same memory engine as the Platform, running on your own infrastructure. You own the stack”
The docs show a public GitHub repo (airweave-ai/airweave) that can be cloned and self-hosted (airweave-docs-11, airweave-docs-14), implying the source is publicly readable, but no evidence specifies an actual open-source license (e.g., MIT/Apache) or license file. Missing for 10: explicit license declaration, confirmation of license terms, and independent corroboration that the repo is fully open (not just source-available for self-hosting).
- [claimed-docs] “git clone https://github.com/airweave-ai/airweave.git cd airweave ./start.sh”
- [claimed-docs] “If you prefer to run Airweave yourself, you can deploy it locally on macOS, Linux or WSL.”
ai-native userSelf-host the core product
weight 3 · round drawnMem0 documents a distinct Open Source self-hosted bundle that runs the same memory engine as the Platform, deployable via Docker with REST API, dashboard, per-user API keys, and audit log, giving full ownership of stack and data. Missing for 10: independent/hands-on verification of self-hosting (all evidence is first-party docs) and details on feature parity limits (e.g., graph memory) between Platform and self-hosted version.
- [claimed-docs] “Mem0 Open Source is the same memory engine as the Platform, running on your own infrastructure. You own the stack, the data, and every compo…”
- [claimed-docs] “The self-hosted bundle ships the REST API and a web dashboard together... per-user API keys and a request audit log.”
- [claimed-docs] “Self-host Mem0 with full control over your infrastructure and data”
- [claimed-docs] “A Docker stack with a dashboard, per-user API keys, and a request audit log.”
- [claimed-docs] “Stand up the Mem0 REST server and dashboard in a few minutes, with an admin account, API keys, and a live audit log included.”
- [claimed-docs] “As a self-hosted server. A Docker stack with a dashboard, per-user API keys, and a request audit log.”
- [claimed-docs] “Mem0 Open Source is the same memory engine as the Platform, running on your own infrastructure. You own the stack”
- [claimed-docs] “Stand up the Mem0 REST server and dashboard in a few minutes, with an admin account, API keys, and a live audit log”
Docs explicitly provide a self-host path via git clone and ./start.sh, and note it can run on macOS, Linux, or WSL, confirming the core product can be self-hosted rather than only used as SaaS. Missing for 10: independent hands-on report of a successful self-hosted deployment and more detail on production-grade self-host configuration/scaling.
- [claimed-docs] “git clone https://github.com/airweave-ai/airweave.git cd airweave ./start.sh”
- [claimed-docs] “If you prefer to run Airweave yourself, you can deploy it locally on macOS, Linux or WSL.”
Pricing plans — plan structure and value — what each tier costs and what it unlocksPricing plans
Plan structure and value — what each tier costs and what it unlocks
Pricing
platform-engineerSee published pricing with a free tier and per-unit rates so I can project memory costs before committing
weight 2 · round drawnMem0none0/10No evidence in the pack mentions pricing, free tier, or per-unit rates anywhere in the docs, community, or probes; all citations concern product features (memory ops, MCP, CLI, graph memory) rather than pricing plans.
Airweavenone0/10No evidence pack item documents a published pricing page, free tier, or per-unit rates; the only pricing-related mentions are community complaints that pricing is 'complex to reason about' and 'prohibitive,' with a direct ask for usage-based per-unit pricing that goes unanswered, indicating no clear published rate structure exists for cost projection.
- [community] “Code samples on the site have broken whitespace on mobile (Android/Brave) so look a bit intense. Also, the pricing is complex to reason abou…”
- [community] “Your pricing currently seems prohibitive for that kind of use case. Shouldn't it be usage-based so one can build a product where users can c…”
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userChoose where my data is stored (region/residency)
weight 2 · round to Mem0Mem0 does not document any explicit region/residency selection for its hosted Platform, but the Open Source self-hosted option lets users run 'on your own infrastructure' and 'own the stack, the data, and every component,' which indirectly lets a user choose where data lives by choosing their own hosting location. Missing for 10: explicit region-selection controls in the hosted Platform, documented data-residency guarantees, and any compliance/geo-location settings.
- [claimed-docs] “Mem0 Open Source is the same memory engine as the Platform, running on your own infrastructure. You own the stack, the data, and every compo…”
- [claimed-docs] “Self-host Mem0 with full control over your infrastructure and data”
- [claimed-docs] “Mem0 Open Source is the same memory engine as the Platform, running on your own infrastructure. You own the stack”
- [claimed-docs] “A Docker stack with a dashboard, per-user API keys, and a request audit log.”
Airweavenone0/10There is no mention anywhere in the evidence pack of data residency, region selection, or self-hosting for compliance/geographic control (the self-host option is framed as a deployment preference, not a residency feature). Missing for 10: any documentation of region choice, data residency guarantees, or compliance-driven storage location controls.
ai-native userPrevent my data from being used to train AI models
weight 3 · round drawnMem0none0/10No evidence anywhere in the pack addresses opting out of AI-model-training use of data, data-training policies, or contractual/privacy commitments about training; the docs focus entirely on memory storage/retrieval features. This is a fair privacy-posture question for a data-storing SaaS product, but nothing in the evidence confirms or denies such a control exists, so it defaults to none.
ai-native userControl data retention and deletion
weight 2 · round to Mem0Mem0 documents CLI/API delete and update operations, expiration_date to stop surfacing memories, and self-hosted deployments giving 'full control over your infrastructure and data', plus audit logs for tracking changes — all supporting retention/deletion control. However, expiration explicitly states 'nothing is deleted' (soft suppression, not erasure), and there's no documented hard-delete/right-to-be-forgotten workflow, data export-then-purge guarantee, or retention policy enforcement (e.g., GDPR compliance statements). missing for 10: explicit hard-delete/purge guarantees, compliance-grade retention policy documentation, independent verification that deletion is permanent.
- [claimed-docs] “The mem0 CLI lets you add, search, list, update, and delete memories directly from the terminal.”
- [claimed-docs] “lets you add, search, list, update, and delete memories directly from the terminal”
- [claimed-docs] “Manage memories from your terminal, for both humans and AI agents.”
- [claimed-docs] “Set an expiration date on a Mem0 memory and it stops surfacing in search once that date passes. Nothing is deleted.”
- [claimed-docs] “Set an expiration date on a Mem0 memory and it stops surfacing in search once that date passes. Nothing is deleted. Works on Platform and Op…”
- [claimed-docs] “Set an expiration_date on a memory and Mem0 stops surfacing it once that date passes, so you don't need a cleanup job hunting for rows to de…”
- [claimed-docs] “Self-host Mem0 with full control over your infrastructure and data”
- [claimed-docs] “A Docker stack with a dashboard, per-user API keys, and a request audit log.”
- [claimed-docs] “Stand up the Mem0 REST server and dashboard in a few minutes, with an admin account, API keys, and a live audit log included.”
Airweavenone0/10Evidence pack covers syncing, search, MCP, and connectors but contains no mention of data retention policies, deletion controls, or user-initiated data purging/export for collections or synced data. This is an applicable axis for a data-sync/RAG platform handling third-party app data, so absence of evidence yields 'none'.
ai-native userOpt out of telemetry and usage tracking
weight 2 · round drawnMem0none0/10No evidence in the pack discusses telemetry, usage tracking, or any opt-out/privacy configuration setting for Mem0; the docs cover memory features, self-hosting, MCP, and CLI but never mention telemetry controls.
Retrieval performance — stories about retrieval performance in this arenaRetrieval performance
Stories about retrieval performance in this arena
Latency
platform-engineerSee documented retrieval-latency targets or measured numbers (e.g. p50/p95) backing the product's speed claims
weight 2 · round to AirweaveMem0none0/10No evidence pack items mention latency numbers, p50/p95 metrics, or any documented performance/speed targets for retrieval; docs focus on features (search, graph memory, reranking) but never quantify speed.
Airweave documents a single rough latency figure ("~0.5sec" for direct vector search) but provides no p50/p95 breakdown, no methodology, benchmark environment, or measured distributions, and no independent corroboration of this number. Missing for 10: documented p50/p95 percentile targets, benchmark methodology/environment details, and independent verification of the latency claim.
- [claimed-docs] “Direct vector search. Use when speed is critical (~0.5sec).”
- [claimed-docs] “Direct vector search. Use when speed is critical (\~0.5sec).”
Scale
platform-engineerIngest at scale with async or batch processing and check the status of background memory operations
weight 2 · round to AirweaveMem0none0/10The evidence pack shows single add/search operations, CLI, webhooks, and quickstart flows, but nothing about async/batch ingestion APIs or a way to poll/check status of background memory operations. This is a fair capability for a memory platform at scale, so absence of evidence yields 'none' rather than 'na'.
- [claimed-docs] “Store facts once, then retrieve them by query”
- [claimed-docs] “client.add(messages, user_id="user123")”
- [claimed-docs] “You send conversation turns to `add`, then call `search` before the next model request to fetch relevant context.”
- [claimed-docs] “The mem0 CLI lets you add, search, list, update, and delete memories directly from the terminal.”
- [claimed-docs] “Webhooks enable real-time notifications for memory events in your Mem0 project.”
Airweave's source connections 'automatically sync data' in the background, and webhooks notify when 'syncs completing' occur, with docs noting this is an alternative to 'constantly polling the API' — implying an async sync/status mechanism exists. However, there is no explicit documentation of batch/large-scale ingestion controls, job-status endpoints, or throughput guarantees for platform-engineer-scale operations. Missing for 10: explicit batch/async ingestion API docs, sync job status endpoint documentation, scale/throughput benchmarks or SLAs.
- [claimed-docs] “A source connection links a specific app or database to your collection. It handles authentication and automatically syncs data.”
- [claimed-docs] “Webhooks are real-time notifications that Airweave sends when things happen in your organization: syncs completing, source connections being…”
- [claimed-docs] “Instead of constantly polling the API, you register a webhook endpoint and Airweave pushes updates to you the moment they occur.”
Sdk integrations — stories about sdk integrations in this arenaSdk integrations
Stories about sdk integrations in this arena
Agent memory
ai-native userConnect off-the-shelf assistants (Claude, ChatGPT, Cursor) to the same memory so every tool I use shares what it knows about me
weight 2 · round drawnMem0 documents an official MCP server that lets any MCP-compatible client (Claude, Cursor, etc.) connect to the same hosted memory store, plus explicit plugins for Claude Code, Cursor, and Codex, and a one-command way to point multiple clients at the hosted server, all backed by user/agent/app-scoped memory so different tools share the same persistent memory. Missing for 10: independent hands-on confirmation that ChatGPT specifically integrates via MCP/plugin (only Claude/Cursor/Codex are named) and no third-party report validating cross-tool memory sharing in practice.
- [claimed-docs] “The Mem0 MCP server hands your agent a set of memory tools, so it can decide for itself when to save something, look something up, or update…”
- [claimed-docs] “Plugins that let Claude Code, Cursor, Codex, and other harnesses remember your project.”
- [claimed-docs] “Connect any AI client to Mem0 using Model Context Protocol in minutes”
- [claimed-docs] “Point your clients at the hosted server with a single command”
- [claimed-docs] “Scope conversations by user, agent, app, and session so memories land exactly where they belong.”
- [probe] “official MCP server documented at https://docs.mem0.ai/platform/mem0-mcp”
Airweave ships an official MCP server that lets assistants like Claude and Cursor search synced data, plus published skills for Cursor, Claude Code, Gemini CLI, and OpenCode that enable setup/search without re-explaining, all pointing to a single shared 'collection' as the underlying memory. Community evidence corroborates real-world use with Cursor. Missing for 10: explicit first-party ChatGPT connector docs and independent evidence of multiple assistants simultaneously sharing state in practice.
- [claimed-docs] “The Airweave MCP server implements the Model Context Protocol to let AI assistants search your synced data.”
- [claimed-docs] “Airweave publishes official skills so that agents in Cursor, Claude Code, Gemini CLI, OpenCode, and other environments can set up integratio…”
- [claimed-docs] “Airweave publishes official skills so that agents in Cursor, Claude Code, Gemini CLI, OpenCode, and other environments can set up integratio…”
- [claimed-docs] “A collection is a group of different data sources that you can search using a single endpoint.”
- [probe] “official MCP server documented at https://docs.airweave.ai/mcp-server”
- [community] “Onyx co-founder: Congratulations on the launch. It looks like Airweave works well with Cursor, something we don't have nailed down yet!”
Frameworks
developerDrop the memory layer into agent frameworks like LangChain, LangGraph, CrewAI, or the Vercel AI SDK via documented first-party integrations
weight 2 · round to Mem0Docs reference setup guides covering 22 tools including LangChain, CrewAI, LlamaIndex, and the Vercel AI SDK, which directly supports the story, but the evidence pack only gives a top-level index reference rather than detailed per-framework integration docs or independent confirmation that these integrations work as advertised. Missing for 10: concrete per-framework code samples/docs excerpts (e.g. LangGraph-specific), independent/hands-on verification of the integrations, and any community confirmation of successful use with these specific frameworks.
- [claimed-docs] “Setup guides for 22 tools, including LangChain, CrewAI, LlamaIndex, and the Vercel AI SDK.”
Airweave documents a framework-integration pattern (e.g., LlamaIndex's AirweaveToolSpec, Pipedream actions, and MCP server/CLI/skills for coding agents), showing the product does ship first-party SDK-style hooks into agent tooling — but none of the specific frameworks named in the story (LangChain, LangGraph, CrewAI, Vercel AI SDK) appear anywhere in the evidence pack. missing for 10: documented LangChain integration, LangGraph integration, CrewAI integration, Vercel AI SDK integration.
- [claimed-docs] “The llama-index-tools-airweave package provides an AirweaveToolSpec that gives your LlamaIndex agents access to Airweave's search capabiliti…”
- [claimed-docs] “The Airweave integration provides a set of actions that enable you to search your synced data to retrieve relevant context, manage your coll…”
- [claimed-docs] “The Airweave MCP server implements the Model Context Protocol to let AI assistants search your synced data.”
- [claimed-docs] “Airweave publishes official skills so that agents in Cursor, Claude Code, Gemini CLI, OpenCode, and other environments can set up integratio…”
developerWire memory into real-time voice pipelines (e.g. LiveKit, Pipecat, ElevenLabs) with documented integrations fast enough for live conversation
weight 1 · round drawnMem0none0/10The evidence pack lists integrations for LangChain, CrewAI, LlamaIndex, Vercel AI SDK, and coding-agent harnesses (Claude Code, Cursor, Codex), but never mentions LiveKit, Pipecat, ElevenLabs, or any real-time voice pipeline integration or latency guarantees for live conversation use.
- [claimed-docs] “Setup guides for 22 tools, including LangChain, CrewAI, LlamaIndex, and the Vercel AI SDK.”
- [claimed-docs] “Plugins that let Claude Code, Cursor, Codex, and other harnesses remember your project.”
Airweavenone0/10No evidence mentions LiveKit, Pipecat, ElevenLabs, or any voice pipeline integration; Airweave's documented integrations are limited to MCP, CLI, coding agents, LlamaIndex, and Pipedream. Latency claims (~0.5s vector search) exist but are not tied to any voice/real-time conversational framework. missing for 10: any mention of LiveKit/Pipecat/ElevenLabs, voice pipeline docs, real-time conversation latency benchmarks specific to voice use cases.
- [claimed-docs] “Direct vector search. Use when speed is critical (~0.5sec).”
- [claimed-docs] “The Airweave MCP server implements the Model Context Protocol to let AI assistants search your synced data.”
- [claimed-docs] “The llama-index-tools-airweave package provides an AirweaveToolSpec that gives your LlamaIndex agents access to Airweave's search capabiliti…”
- [claimed-docs] “The Airweave integration provides a set of actions that enable you to search your synced data to retrieve relevant context, manage your coll…”
Sdks
developerBuild against official SDKs in at least Python and TypeScript with equivalent memory APIs
weight 2 · round to Mem0Docs indicate both Python and JavaScript/TypeScript SDKs exist and expose the same core operations (add, search) via a common quickstart flow, and code snippets show `client.add()` usage. However, there is no dedicated documentation confirming feature parity between the two SDKs, no independent/hands-on verification of the TypeScript SDK, and most of the pack is Python-centric examples. Missing for 10: explicit TypeScript SDK reference/API docs, confirmation of full method parity across languages, and independent developer corroboration of TS SDK usage.
- [claimed-docs] “get an API key, then save and search a memory in Python or JavaScript”
- [claimed-docs] “client.add(messages, user_id="user123")”
- [claimed-docs] “Set up your Mem0 Platform account, install the SDK, and store your first memory in under five minutes.”
- [claimed-docs] “Setup guides for 22 tools, including LangChain, CrewAI, LlamaIndex, and the Vercel AI SDK.”
Airweavenone0/10No evidence pack item mentions official Python or TypeScript SDKs at all; documentation references an OpenAPI spec, MCP server, CLI, and framework integrations (LlamaIndex, Pipedream) but not dedicated Python/TypeScript client libraries with memory APIs. Missing for 10: any mention of an official Python SDK, an official TypeScript SDK, or parity of memory/search APIs between them.
Session context — stories about session context in this arenaSession context
Stories about session context in this arena
Context assembly
developerRetrieve a token-budgeted, prompt-ready context block assembled from relevant memories in one call
weight 2 · round to Mem0Mem0's search operation retrieves and reranks relevant memories in a single call (mem0-docs-7, mem0-docs-10, mem0-docs-56), and quickstart flow shows add/search used to fetch context before the next model call (mem0-docs-43). However, there is no evidence of token-budget control, truncation, or an explicit prompt-ready formatted context block being assembled — search returns raw memory results, not a pre-packaged prompt string sized to a token limit. Missing for 10: token-budget parameter or context-length control, explicit prompt-template/context-block formatting output, and any independent confirmation of this packaging behavior.
- [claimed-docs] “Mem0's search operation lets agents ask natural-language questions and get back the memories that matter most.”
- [claimed-docs] “Reorders results using deep semantic understanding to put the most relevant memories first.”
- [claimed-docs] “You send conversation turns to `add`, then call `search` before the next model request to fetch relevant context.”
- [claimed-docs] “Retrieve relevant memories from Mem0 using powerful semantic and filtered search capabilities.”
- [claimed-docs] “Advanced memory search with intelligent reranking for precise results”
Airweavenone0/10Airweave's docs describe search endpoints (direct vector search and agentic search) returning results from connected sources, but there is no mention of a token-budgeted or prompt-ready context assembly feature. Missing for 10: any documentation of token-limit controls, context-window formatting, or a single-call 'assemble context' endpoint.
- [claimed-docs] “Direct vector search. Use when speed is critical (~0.5sec).”
- [claimed-docs] “An AI agent iteratively searches your data using tool calling. It searches with multiple strategies, reads full documents, navigates entity …”
- [claimed-docs] “Airweave lets AI agents search across company knowledge bases, cloud drives, databases, and SaaS tools in a single query.”
Ingestion
developerIngest documents, JSON, and business data into memory — not just chat transcripts
weight 2 · round to AirweaveMem0none0/10All evidence describes Mem0's add/search API in terms of conversation messages (client.add(messages, user_id=...)) and fact extraction from chat turns; there is no mention of ingesting documents, PDFs, JSON payloads, or arbitrary business data as a memory source. Memory Export uses Pydantic schemas for output, not input ingestion of external structured data.
- [claimed-docs] “Store facts once, then retrieve them by query”
- [claimed-docs] “Mem0 pulls the individual facts out of the conversation and stores each one separately”
- [claimed-docs] “client.add(messages, user_id="user123")”
- [claimed-docs] “You send conversation turns to `add`, then call `search` before the next model request to fetch relevant context.”
- [claimed-docs] “Mem0 sits between your application and your model. You send conversation turns to `add`, then call `sear”
- [claimed-docs] “The Memory Export feature allows you to create structured exports of memories using customizable Pydantic schemas.”
Airweave connects and syncs diverse sources — cloud drives, databases, SaaS tools, knowledge bases — into searchable collections, explicitly going beyond chat transcripts to documents, JSON/business data, and structured app data (docs-2, docs-12, docs-16). Community feedback corroborates strong retrieval across integrations. Missing for 10: independent hands-on verification of ingesting raw JSON/business data specifically (beyond documented app connectors), and detailed schema/normalization docs for non-document structured data.
- [claimed-docs] “A source connection links a specific app or database to your collection. It handles authentication and automatically syncs data.”
- [claimed-docs] “Airweave lets AI agents search across company knowledge bases, cloud drives, databases, and SaaS tools in a single query.”
- [claimed-docs] “If your favorite tool or API is not yet supported, you can build a connector and either use it locally or contribute it back to the communit…”
- [claimed-docs] “Webhooks are real-time notifications that Airweave sends when things happen in your organization: syncs completing, source connections being…”
- [community] “Had meetings with a ton of MCP-server providers, no one came close to Airweave’s retrieval accuracy. I even tried Zapier and similar large c…”
- [community] “Yes, a lot MCP servers are just api wrappers. Airweave looks like it copies the data and has a RAG that is processing your queries.”
developerStore images, PDFs, or other files as memory inputs and recall information from them later
weight 1 · round drawnMem0none0/10All evidence describes Mem0 storing and retrieving text-based conversational facts (add/search operations, graph memory, expiration, etc.); nothing in the docs or community evidence mentions ingesting images, PDFs, or other file types as memory inputs.
- [claimed-docs] “Store facts once, then retrieve them by query”
- [claimed-docs] “Mem0 pulls the individual facts out of the conversation and stores each one separately”
- [claimed-docs] “client.add(messages, user_id="user123")”
- [claimed-docs] “You send conversation turns to `add`, then call `search` before the next model request to fetch relevant context.”
- [claimed-docs] “Mem0 sits between your application and your model. You send conversation turns to `add`, then call `sear”
Airweavenone0/10Airweave's docs describe syncing structured data from apps/databases and cloud drives (Slack, GitHub, Google Drive, Notion) into searchable collections, but no evidence shows direct ingestion of images, PDFs, or arbitrary files as memory inputs, nor multimodal parsing/recall of such files. missing for 10: explicit file/image/PDF upload API, multimodal parsing or OCR capability, and any documentation or example of recalling content from a stored image/PDF.
- [claimed-docs] “A source connection links a specific app or database to your collection. It handles authentication and automatically syncs data.”
- [claimed-docs] “Airweave Connect is a hosted, embeddable UI widget that lets end users connect their apps (Slack, GitHub, Google Drive, Notion, and more) di…”
- [claimed-docs] “Airweave lets AI agents search across company knowledge bases, cloud drives, databases, and SaaS tools in a single query.”
Tenancy permissions — stories about tenancy permissions in this arenaTenancy permissions
Stories about tenancy permissions in this arena
Governance
platform-engineerGovern who and what can read or write memory with roles, policies, or access-control lists, and audit that access
weight 2 · round to Mem0Mem0 documents per-user API keys and a request audit log in the self-hosted bundle, plus entity-scoped memory (user/agent/app/session) that could support basic access separation, but there is no evidence of role-based access control, granular permission policies, or ACLs governing who can read/write specific memories. missing for 10: RBAC/permission policies, ACL enforcement on read/write, admin console for managing roles, independent verification of audit log completeness.
- [claimed-docs] “The self-hosted bundle ships the REST API and a web dashboard together... per-user API keys and a request audit log.”
- [claimed-docs] “A Docker stack with a dashboard, per-user API keys, and a request audit log.”
- [claimed-docs] “Stand up the Mem0 REST server and dashboard in a few minutes, with an admin account, API keys, and a live audit log included.”
- [claimed-docs] “Scope conversations by user, agent, app, and session so memories land exactly where they belong.”
- [claimed-docs] “As a self-hosted server. A Docker stack with a dashboard, per-user API keys, and a request audit log.”
Isolation
developerScope memories per user, agent, or application so one tenant's memories never leak into another's retrieval
weight 3 · round to Mem0Docs explicitly describe entity-scoped memory with user_id, agent_id, app_id, and session scoping so memories 'land exactly where they belong' and are separated across users/agents/apps, matching the tenancy story directly (mem0-docs-9, mem0-docs-30, mem0-docs-35). Missing for 10: independent/hands-on verification that isolation is enforced at retrieval time (no cross-tenant leakage tested), and no detail on access-control enforcement (e.g., can a request with wrong user_id still retrieve another user's memories) beyond first-party docs.
- [claimed-docs] “Mem0's Platform API lets you separate memories for different users, agents, and apps.”
- [claimed-docs] “Scope conversations by user, agent, app, and session so memories land exactly where they belong.”
- [claimed-docs] “client.add(messages, user_id="user123")”
Airweavenone0/10Airweave's docs describe collections, source connections, and organizations as organizational units, but nothing in the evidence pack describes per-user/agent/application scoping guarantees or tenant-isolation enforcement in retrieval. No mention of access control, row-level security, or per-tenant query filtering that would prevent cross-tenant leakage.
- [claimed-docs] “A collection is a group of different data sources that you can search using a single endpoint.”
- [claimed-docs] “A source connection links a specific app or database to your collection. It handles authentication and automatically syncs data.”
- [claimed-docs] “Webhooks are real-time notifications that Airweave sends when things happen in your organization: syncs completing, source connections being…”
Sharing
developerShare selected memory across multiple agents or users (team or group memory) while keeping private memory private
weight 1 · round to Mem0Mem0's entity-scoped memory lets you scope by user_id, agent_id, app_id, and session, which can be used to segregate private memory per user while sharing memory under a common agent_id or app_id — a workable pattern for group/team memory. However, the docs never explicitly describe a 'team' or 'group' memory concept, permission model, or access-control rules distinguishing private vs shared visibility across users/agents. Missing for 10: explicit team/group memory feature, role-based access control or sharing permissions, and any documentation of enforcing privacy boundaries between scoped entities.
- [claimed-docs] “Mem0's Platform API lets you separate memories for different users, agents, and apps.”
- [claimed-docs] “Scope conversations by user, agent, app, and session so memories land exactly where they belong.”
Airweavenone0/10Airweave's docs describe collections, source connections, and search endpoints, but nothing addresses per-user/per-agent memory scoping, shared vs. private data boundaries, or team/tenant isolation. The evidence pack has no mention of access control, multi-tenant permissions, or selective sharing of synced data between agents/users.
Not comparable on these axes
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparableMem0n/aMem0 is a memory-layer backend that itself exposes an MCP server for agents to consume (docs-2, docs-18, probe-3) rather than an agentic client that consumes other MCP servers' tools; plugging external MCP servers into Mem0 so it can use their tools is a category mismatch for this product's role.
- [claimed-docs] “The Mem0 MCP server hands your agent a set of memory tools, so it can decide for itself when to save something, look something up, or update…”
- [claimed-docs] “Connect any AI client to Mem0 using Model Context Protocol in minutes”
- [probe] “official MCP server documented at https://docs.mem0.ai/platform/mem0-mcp”
Airweavenone0/10Airweave documents itself as an MCP *server* that lets external AI assistants query its data (airweave-docs-5, airweave-probe-3), and its integrations (auth-providers, connectors) are proprietary, not MCP-based consumption of external servers. There is no evidence Airweave itself acts as an MCP client that plugs in and uses tools from other MCP servers.
- [claimed-docs] “The Airweave MCP server implements the Model Context Protocol to let AI assistants search your synced data.”
- [claimed-docs] “Authentication providers let you reuse existing authenticated connections from third-party platforms such as Composio or Pipedream.”
- [probe] “official MCP server documented at https://docs.airweave.ai/mcp-server”
ai-native userSet up automations that run autonomously in the background
weight 2 · not comparableMem0n/aMem0 is a memory-layer API/service for storing and retrieving facts for LLM agents; it does not offer a workflow/automation-scheduling capability where users configure tasks to run autonomously in the background. Webhooks (event notifications) are the closest feature but they are outbound notifications tied to memory CRUD events, not user-configured autonomous automations, so this axis is a category mismatch for the product type.
Source connections automatically sync data in the background and webhooks push real-time updates instead of requiring polling, showing some autonomous background operation, but there's no evidence of a general-purpose automation/workflow engine (scheduled tasks, conditional triggers, multi-step actions) within Airweave itself—automation-style triggering is delegated to third-party tools like Pipedream. Missing for 10: native scheduling/trigger configuration UI, evidence of autonomous multi-step task execution, and independent confirmation that background syncs run reliably at scale.
- [claimed-docs] “A source connection links a specific app or database to your collection. It handles authentication and automatically syncs data.”
- [claimed-docs] “Webhooks are real-time notifications that Airweave sends when things happen in your organization: syncs completing, source connections being…”
- [claimed-docs] “Instead of constantly polling the API, you register a webhook endpoint and Airweave pushes updates to you the moment they occur.”
- [claimed-docs] “The Airweave integration provides a set of actions that enable you to search your synced data to retrieve relevant context, manage your coll…”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · not comparableMem0n/aMem0 is a memory-layer infrastructure product (API/SDK/MCP server) for other agents to use, not itself an AI assistant with a task-delegation UI; this axis is a category error for its product type.
Airweaven/aAirweave is a data-integration/search backend designed to be queried by external AI agents (via MCP, API, CLI, skills) — it is not itself a product with an embedded assistant UI that end-users delegate tasks to inside the product. The 'agentic search' feature (docs-4, docs-17) is a retrieval strategy, not a built-in assistant, so this axis is a category mismatch for this kind of infrastructure product.
ai-native userSchedule recurring jobs or workflows
weight 2 · not comparableMem0n/aMem0 is a memory layer/API for LLM agents, not a workflow/job orchestration or scheduling product; no evidence pack content relates to recurring jobs or scheduled workflows, and this capability is outside its product category.
Airweave's source connections 'automatically sync data' and it pushes webhook updates instead of polling, implying some recurring background sync exists, but there's no documented scheduling interface, cron-like controls, or ability to schedule arbitrary recurring jobs/workflows beyond source sync. Missing for 10: explicit scheduling/cron configuration options, user-defined recurring workflow triggers, and any evidence of customizable sync intervals.
- [claimed-docs] “A source connection links a specific app or database to your collection. It handles authentication and automatically syncs data.”
- [claimed-docs] “Webhooks are real-time notifications that Airweave sends when things happen in your organization: syncs completing, source connections being…”
- [claimed-docs] “Instead of constantly polling the API, you register a webhook endpoint and Airweave pushes updates to you the moment they occur.”
ai-native userVersion, review, and roll back my automations
weight 1 · not comparableMem0n/aMem0 is a memory layer for LLM agents, not an automation/workflow platform with version-controlled automations to review or roll back; this axis is a category error for this product type.
Airweaven/aAirweave is a data-sync/search platform for connecting and querying data sources, not an automation/workflow builder; there is no concept of 'automations' with versioning, review, or rollback in the evidence pack. This story targets workflow-automation tools and is a category error for Airweave's product type.
ai-native userThe memory layer decides for itself what is worth remembering — extracting salient facts from raw conversation and consolidating them in the background
weight 2 · not comparableDocs show Mem0 automatically extracts individual facts from raw conversation and organizes them into a graph without user-defined schema (mem0-docs-26, mem0-docs-8, mem0-docs-38, mem0-docs-42), and the search/retrieval flow lets the system decide what's salient (mem0-docs-7, mem0-docs-43). However, evidence of true background 'self-improving' consolidation (deduping, merging over time) is thin, and one independent report notes Mem0 doesn't implicitly learn behavioral patterns beyond stored facts (mem0-comm-7), tempering the 'decides for itself' framing. Missing for 10: explicit documentation/evidence of background consolidation jobs or memory merging over time, and independent hands-on validation of extraction quality.
- [claimed-docs] “Mem0 pulls the individual facts out of the conversation and stores each one separately”
- [claimed-docs] “Store facts once, then retrieve them by query”
- [claimed-docs] “Mem0 Platform automatically organizes your memories into a graph... with no external graph database to provision.”
- [claimed-docs] “Mem0 Platform builds a native graph linking people, places, and concepts across your memories, with no external graph database to provision.”
- [claimed-docs] “Mem0 Platform automatically organizes your memories into a graph... without you defining any schema.”
- [claimed-docs] “You send conversation turns to `add`, then call `search` before the next model request to fetch relevant context.”
- [community] “We looked at Mem0, Letta/MemGPT, and similar memory solutions. They all solve storing facts from conversations - key-value memory with seman…”
Airweaven/aAirweave is a data-source sync and search/RAG platform (collections, source connections, vector/agent search over connected apps) — it is not a conversational memory layer that autonomously extracts salient facts from chat and consolidates them in the background. This capability is a different product category (conversational memory systems) and is a category error for Airweave's connector/search architecture.
developerGet summaries of past sessions or threads so an agent can pick up where the last conversation left off
weight 3 · not comparableMem0's core design explicitly targets cross-session continuity — memories persist and are scoped by session/user/agent, and search retrieves the relevant facts before the next model call so an agent can resume context (mem0-docs-30, mem0-docs-43, mem0-probe-1). However, Mem0 stores discrete extracted facts rather than producing an actual 'summary' of a past thread/session, so the story's specific 'summary' framing is only approximated by fact retrieval, not a dedicated summarization feature. Missing for 10: an explicit session/thread summarization API or feature, and independent hands-on evidence that retrieved facts effectively reconstruct 'where we left off' in practice.
- [claimed-docs] “Scope conversations by user, agent, app, and session so memories land exactly where they belong.”
- [claimed-docs] “You send conversation turns to `add`, then call `search` before the next model request to fetch relevant context.”
- [claimed-docs] “Mem0 sits between your application and your model”
- [claimed-docs] “Mem0's search operation lets agents ask natural-language questions and get back the memories that matter most.”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.mem0.ai/llms.txt # Mem0 > Mem0 is a memory layer for LLM agents - persistent, self-improving conte…”
Airweaven/aAirweave is a data-integration/search platform that syncs external sources (Slack, Drive, databases) and exposes them via search/MCP endpoints; it has no documented feature for storing, summarizing, or resuming an agent's own conversation/session history. This story targets conversational memory/session continuity, which is a different product category than Airweave's data-sync-and-search focus.