What each one has. With the source of every cell.
Sixteen capabilities, Niadra and ten memory systems. Every cell says what the vendor’s own documentation states, with the link to the page and the day it was read. Where a competitor has what Niadra does not, the row says so. For the measured numbers, see the benchmark.
- yesthe vendor’s documentation describes the whole capability
- partialit describes part of it; the note says which
- nothe documentation says it works another way
- not documentedthe page read says nothing about it, which does not mean it does not exist
Every mark is a link to the page read, on 2026-10-01. Documentation changes: a cell only changes after a new reading, with a new date.
| Capability | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Identity across channelsThe memory works out that the phone, the WhatsApp number, the e-mail and each system’s ID belong to the same person. The application does not hand over a ready-made ID. | yes | no | no | no | no | no | no | no | no | no | yes |
| One memory for agents from different vendorsAgents from different vendors read and feed the same customer memory, each with its own permission, and cutting one vendor off erases nothing. | yes | partial | partial | partial | partial | partial | partial | partial | partial | partial | partial |
| Events from the CRM and the ERPOrders, bills and tickets enter the memory through the events the system already emits, tied to the right customer by that system’s ID. | yes | not documented | not documented | partial | not documented | not documented | not documented | not documented | not documented | not documented | partial |
| Typed business state with freshnessAn order, a bill, a quote: every value reaches the agent with its type, the date it was last updated, the source and what may not be stated with it. | yes | no | partial | partial | no | partial | no | no | partial | no | partial |
| The claim checkBefore the answer goes out, every price, date and number the agent is about to say is checked against what it consulted. What has no source is flagged. | yes | not documented | not documented | not documented | not documented | not documented | not documented | not documented | not documented | not documented | not documented |
| Coordination between agentsBefore acting, the agent asks who holds the customer and what was already done. One business fact causes one effect. | yes | not documented | not documented | not documented | not documented | not documented | not documented | not documented | not documented | not documented | not documented |
| Turn records and replayWhat the agent read, called, showed and stated on every turn, with the build pinned, and the replay of a real conversation in your CI. | yes | not documented | not documented | not documented | partial | not documented | not documented | not documented | not documented | partial | not documented |
| Per-agent permissions and field accessEach agent reads only what its purpose allows, item by item, and a sensitive field reaches only who may see it. | yes | partial | partial | partial | partial | partial | partial | partial | partial | partial | not documented |
| Receipts of who read whatEvery read, the refused one included, leaves a record of which agent read what, for what and when, tamper-evident. | yes | partial | partial | partial | not documented | not documented | not documented | not documented | not documented | partial | partial |
| Erasure with a receiptErasing a customer walks through everything derived from their data and returns a receipt of what was erased. | yes | partial | partial | partial | partial | partial | yes | partial | partial | partial | partial |
| Prompt-ready compact contextThe agent receives text ready for the prompt, assembled before the request, with no AI on the read. | yes | partial | partial | yes | partial | yes | partial | yes | partial | partial | partial |
| Voice integrationsA documented adapter for voice platforms: LiveKit, Pipecat, Vapi, Retell, ElevenLabs, Twilio. | yes | yes | yes | yes | yes | yes | yes | not documented | not documented | not documented | yes |
| MCP serverThe memory as MCP tools, for any agent that speaks the protocol. | yes | yes | yes | yes | partial | yes | yes | yes | yes | partial | not documented |
| A published benchmarkThe vendor publishes measured results of its own memory, with the method. | yes | yes | yes | yes | yes | partial | yes | yes | yes | not documented | not documented |
| Open source and self-hostingThe memory engine is open and can run on the customer’s own infrastructure. | no | yes | no | partial | yes | yes | yes | yes | yes | no | no |
| Published priceThe list price as the vendor’s page states it, with no conversion. The cost per thousand conversations, measured by the same method for every system, is on the benchmark. | US$ 2 to 3 per thousand conversations or tasks, models included; US$ 500 a month minimumsource · 2026-10-01 | Free software; you pay for the model and the serverssource · 2026-10-01 | Hobby free; Starter US$ 19 a month; Pro US$ 249 a month (500,000 adds and 50,000 retrievals); Enterprise on requestsource · 2026-10-01 | Flex US$ 125 a month with 50,000 credits (1 credit per episode of up to 350 bytes); Flex Plus US$ 375; Enterprise on requestsource · 2026-10-01 | API US$ 20 a month, plus US$ 0.10 per active agent a month and US$ 0.00015 per second of tool execution; the model apartsource · 2026-10-01 | Pro US$ 19, Max US$ 100 and Scale US$ 399 a month; rate card of US$ 5 per million SM tokens and US$ 5 per million searchessource · 2026-10-01 | Usage-based: retain US$ 10 per million tokens, recall US$ 0.75 per million, reflect US$ 0.05 per call, storage US$ 0.25 per million a monthsource · 2026-10-01 | Ingestion US$ 2 per million tokens; context() unlimited; reasoning from US$ 0.001 to 0.50 per questionsource · 2026-10-01 | Free up to 1 million tokens; Standard US$ 1 per million tokens plus US$ 5 per extra workspace; Enterprise on requestsource · 2026-10-01 | US$ 0.25 per 1,000 events; US$ 0.75 per 1,000 records stored a month (US$ 0.25 with your own strategy); US$ 0.50 per 1,000 retrievalssource · 2026-10-01 | US$ 0.005 per profile used per day; US$ 0.0028 per 1,000 characters generated; US$ 0.007 per recallsource · 2026-10-01 |
Names and logos belong to their owners and appear here only to identify the systems compared.
See the benchmark, with the measured numbers and the result filesThe evidence behind every mark
System by system, what the page read says about each capability, with the link. It is what you need to check any cell.
NiadraOpen
- Identity across channels: yes
- Identifiers by type, with a weight, reversible merges and a verification level per conversation.
- source · 2026-10-01(opens docs.niadra.com)
- One memory for agents from different vendors: yes
- Each vendor has its own credential and permission; none reads the other’s memory or numbers.
- source · 2026-10-01(opens docs.niadra.com)
- Events from the CRM and the ERP: yes
- Webhook with a versioned mapping, batch and file; no AI in the path.
- source · 2026-10-01(opens docs.niadra.com)
- Typed business state with freshness: yes
- Types declared or derived from the database; freshness per field computed on the read.
- source · 2026-10-01(opens docs.niadra.com)
- The claim check: yes
- A contract per category; the check runs in the agent’s process, with no extra AI.
- source · 2026-10-01(opens docs.niadra.com)
- Coordination between agents: yes
- Ownership by declaration and observation, effect exactly once, a contact token for the gateway.
- source · 2026-10-01(opens docs.niadra.com)
- Turn records and replay: yes
- Captured in the agent’s process; replay in CI with the tools answering from the record.
- source · 2026-10-01(opens docs.niadra.com)
- Per-agent permissions and field access: yes
- Denied by default, granted by purpose; fixed sensitive categories; field access on the state.
- source · 2026-10-01(opens docs.niadra.com)
- Receipts of who read what: yes
- A receipt per read, chained by SHA-256, with a daily root in write-once storage.
- source · 2026-10-01(opens docs.niadra.com)
- Erasure with a receipt: yes
- Erasure by lineage, with a receipt and the list of what to erase in your exported copy.
- source · 2026-10-01(opens docs.niadra.com)
- Prompt-ready compact context: yes
- Compiled when the memory changes, per agent and task, in layers the provider reuses.
- source · 2026-10-01(opens docs.niadra.com)
- Voice integrations: yes
- LiveKit, Pipecat, Vapi, Retell, ElevenLabs and Twilio, with the context before the hello.
- source · 2026-10-01(opens docs.niadra.com)
- MCP server: yes
- Eight tools, with the customer bound out of the model’s reach.
- source · 2026-10-01(opens docs.niadra.com)
- A published benchmark: yes
- Cross-channel accuracy, privacy, cost and latency, with a public script and result files.
- source · 2026-10-01(opens niadra.com)
- Open source and self-hosting: no
- The SDKs are open (Apache 2.0); the service is fully managed by Niadra, by the company’s decision.
- source · 2026-10-01(opens github.com)
Mem0 (open source)Open
- Identity across channels: no
- Memory is kept under the user_id the application sends.
- source · 2026-10-01(opens github.com)
- One memory for agents from different vendors: partial
- Any agent with the key reads the same user_id. No permission per vendor.
- source · 2026-10-01(opens github.com)
- Events from the CRM and the ERP: not documented
- source · 2026-10-01(opens docs.mem0.ai)
- Typed business state with freshness: no
- Memory is text extracted from the conversation.
- source · 2026-10-01(opens github.com)
- The claim check: not documented
- source · 2026-10-01(opens github.com)
- Coordination between agents: not documented
- source · 2026-10-01(opens github.com)
- Turn records and replay: not documented
- source · 2026-10-01(opens github.com)
- Per-agent permissions and field access: partial
- An API key per server user; no purpose and no field.
- source · 2026-10-01(opens docs.mem0.ai)
- Receipts of who read what: partial
- A recent log of the server’s API calls.
- source · 2026-10-01(opens docs.mem0.ai)
- Erasure with a receipt: partial
- Deletion per memory or user; no receipt.
- source · 2026-10-01(opens docs.mem0.ai)
- Prompt-ready compact context: partial
- Search returns a list of memories; the application builds the prompt.
- source · 2026-10-01(opens github.com)
- Voice integrations: yes
- LiveKit, ElevenLabs and Pipecat.
- source · 2026-10-01(opens docs.mem0.ai)
- MCP server: yes
- OpenMemory MCP, local, on top of open-source Mem0.
- source · 2026-10-01(opens mem0.ai)
- A published benchmark: yes
- LoCoMo, LongMemEval and BEAM, with a paper on arXiv.
- source · 2026-10-01(opens mem0.ai)
- Open source and self-hosting: yes
- Apache 2.0, with a Docker server.
- source · 2026-10-01(opens github.com)
Mem0 PlatformOpen
- Identity across channels: no
- user_id, agent_id, app_id and run_id come from the application.
- source · 2026-10-01(opens docs.mem0.ai)
- One memory for agents from different vendors: partial
- Several agents filter the same user_id by agent_id. No permission per vendor.
- source · 2026-10-01(opens docs.mem0.ai)
- Events from the CRM and the ERP: not documented
- Mem0’s webhooks are outbound: they notify when a memory changes.
- source · 2026-10-01(opens docs.mem0.ai)
- Typed business state with freshness: partial
- A creation date and an expiry per memory; no typed object and no freshness per field.
- source · 2026-10-01(opens docs.mem0.ai)
- The claim check: not documented
- source · 2026-10-01(opens docs.mem0.ai)
- Coordination between agents: not documented
- source · 2026-10-01(opens docs.mem0.ai)
- Turn records and replay: not documented
- source · 2026-10-01(opens docs.mem0.ai)
- Per-agent permissions and field access: partial
- Reader and owner roles per project; no purpose and no field.
- source · 2026-10-01(opens docs.mem0.ai)
- Receipts of who read what: partial
- A project event feed (add, search, delete); audit logs on Enterprise.
- source · 2026-10-01(opens docs.mem0.ai)
- Erasure with a receipt: partial
- Deleting a user is asynchronous and returns an event_id; no receipt.
- source · 2026-10-01(opens docs.mem0.ai)
- Prompt-ready compact context: partial
- Search returns a list of memories; the application builds the prompt.
- source · 2026-10-01(opens docs.mem0.ai)
- Voice integrations: yes
- LiveKit, ElevenLabs and Pipecat.
- source · 2026-10-01(opens docs.mem0.ai)
- MCP server: yes
- A hosted server with eleven tools.
- source · 2026-10-01(opens docs.mem0.ai)
- A published benchmark: yes
- LoCoMo, LongMemEval and BEAM, with a paper on arXiv.
- source · 2026-10-01(opens mem0.ai)
- Open source and self-hosting: no
- A managed service; on-premises on Enterprise.
- source · 2026-10-01(opens mem0.ai)
ZepOpen
- Identity across channels: no
- The user_id "maps to your internal User ID".
- source · 2026-10-01(opens help.getzep.com)
- One memory for agents from different vendors: partial
- The company’s agent and the person’s MCP client share one user graph.
- source · 2026-10-01(opens help.getzep.com)
- Events from the CRM and the ERP: partial
- Business records go in as JSON through graph.add; no inbound webhook and no per-system ID.
- source · 2026-10-01(opens help.getzep.com)
- Typed business state with freshness: partial
- Facts with valid_at and invalid_at; no typed object per field.
- source · 2026-10-01(opens help.getzep.com)
- The claim check: not documented
- source · 2026-10-01(opens help.getzep.com)
- Coordination between agents: not documented
- source · 2026-10-01(opens help.getzep.com)
- Turn records and replay: not documented
- source · 2026-10-01(opens help.getzep.com)
- Per-agent permissions and field access: partial
- Policies on API keys and user groups; no purpose and no field.
- source · 2026-10-01(opens help.getzep.com)
- Receipts of who read what: partial
- Audit logs of API and dashboard activity; no receipt per read.
- source · 2026-10-01(opens help.getzep.com)
- Erasure with a receipt: partial
- Deletes the user, the threads and the graph; returns a success message.
- source · 2026-10-01(opens help.getzep.com)
- Prompt-ready compact context: yes
- A context block assembled as text; ingestion can take minutes.
- source · 2026-10-01(opens help.getzep.com)
- Voice integrations: yes
- ElevenLabs and LiveKit.
- source · 2026-10-01(opens help.getzep.com)
- MCP server: yes
- Memory MCP Server, with sign-in through the company’s identity provider.
- source · 2026-10-01(opens help.getzep.com)
- A published benchmark: yes
- DMR and LongMemEval, in Zep’s paper.
- source · 2026-10-01(opens arxiv.org)
- Open source and self-hosting: partial
- Graphiti is open; Zep Cloud is managed, with bring-your-own-cloud on Enterprise.
- source · 2026-10-01(opens help.getzep.com)
LettaOpen
- Identity across channels: no
- An identity carries the key the application chooses (identifier_key).
- source · 2026-10-01(opens docs.letta.com)
- One memory for agents from different vendors: partial
- Blocks shared between Letta agents, through git repositories. Other vendors are not mentioned.
- source · 2026-10-01(opens docs.letta.com)
- Events from the CRM and the ERP: not documented
- source · 2026-10-01(opens docs.letta.com)
- Typed business state with freshness: no
- Memory blocks in text, edited by the agent.
- source · 2026-10-01(opens docs.letta.com)
- The claim check: not documented
- source · 2026-10-01(opens docs.letta.com)
- Coordination between agents: not documented
- The shared memory page says nothing about locks or ownership.
- source · 2026-10-01(opens docs.letta.com)
- Turn records and replay: partial
- The steps API keeps the model, tokens and trace id of each step; replay is not documented.
- source · 2026-10-01(opens docs.letta.com)
- Per-agent permissions and field access: partial
- Role-based access control on the Enterprise plan.
- source · 2026-10-01(opens docs.letta.com)
- Receipts of who read what: not documented
- source · 2026-10-01(opens docs.letta.com)
- Erasure with a receipt: partial
- Deleting an agent returns an empty object.
- source · 2026-10-01(opens docs.letta.com)
- Prompt-ready compact context: partial
- The blocks live in the Letta agent’s prompt; they are not served to another agent.
- source · 2026-10-01(opens docs.letta.com)
- Voice integrations: yes
- LiveKit and Vapi, marked experimental.
- source · 2026-10-01(opens docs.letta.com)
- MCP server: partial
- Letta connects to MCP servers as a client; it is not documented as a server.
- source · 2026-10-01(opens docs.letta.com)
- A published benchmark: yes
- LoCoMo with Letta’s filesystem, on the blog.
- source · 2026-10-01(opens www.letta.com)
- Open source and self-hosting: yes
- Apache 2.0, with its own server.
- source · 2026-10-01(opens github.com)
SupermemoryOpen
- Identity across channels: no
- One profile per containerTag, set by the application.
- source · 2026-10-01(opens supermemory.ai)
- One memory for agents from different vendors: partial
- Keys restricted to containerTags; any agent with the key reads the profile.
- source · 2026-10-01(opens supermemory.ai)
- Events from the CRM and the ERP: not documented
- The connectors are knowledge sources: Drive, Gmail, Notion, OneDrive.
- source · 2026-10-01(opens supermemory.ai)
- Typed business state with freshness: partial
- Facts with update relations and expiry; no typed object per field.
- source · 2026-10-01(opens supermemory.ai)
- The claim check: not documented
- source · 2026-10-01(opens supermemory.ai)
- Coordination between agents: not documented
- source · 2026-10-01(opens supermemory.ai)
- Turn records and replay: not documented
- source · 2026-10-01(opens supermemory.ai)
- Per-agent permissions and field access: partial
- Keys restricted to containerTags; no purpose and no field.
- source · 2026-10-01(opens supermemory.ai)
- Receipts of who read what: not documented
- source · 2026-10-01(opens supermemory.ai)
- Erasure with a receipt: partial
- Forgetting is a soft delete; it returns the id and the forgotten flag.
- source · 2026-10-01(opens supermemory.ai)
- Prompt-ready compact context: yes
- A static and a dynamic profile, for the prompt.
- source · 2026-10-01(opens supermemory.ai)
- Voice integrations: yes
- LiveKit and Pipecat.
- source · 2026-10-01(opens supermemory.ai)
- MCP server: yes
- A hosted server; not available in the local version.
- source · 2026-10-01(opens supermemory.ai)
- A published benchmark: partial
- Publishes the open MemoryBench harness; the results are yours to run.
- source · 2026-10-01(opens supermemory.ai)
- Open source and self-hosting: yes
- An open local binary; no connectors and no MCP locally.
- source · 2026-10-01(opens supermemory.ai)
HindsightOpen
- Identity across channels: no
- One memory bank per user, project or agent, isolated from the others.
- source · 2026-10-01(opens docs.hindsight.vectorize.io)
- One memory for agents from different vendors: partial
- Keys restricted to banks; any agent with the key reads the bank.
- source · 2026-10-01(opens docs.hindsight.vectorize.io)
- Events from the CRM and the ERP: not documented
- source · 2026-10-01(opens docs.hindsight.vectorize.io)
- Typed business state with freshness: no
- Text items, with an optional timestamp.
- source · 2026-10-01(opens docs.hindsight.vectorize.io)
- The claim check: not documented
- source · 2026-10-01(opens docs.hindsight.vectorize.io)
- Coordination between agents: not documented
- source · 2026-10-01(opens docs.hindsight.vectorize.io)
- Turn records and replay: not documented
- source · 2026-10-01(opens docs.hindsight.vectorize.io)
- Per-agent permissions and field access: partial
- Keys restricted to banks; no purpose and no field.
- source · 2026-10-01(opens docs.hindsight.vectorize.io)
- Receipts of who read what: not documented
- The SIEM receives only Memory Defense violations, with the key that wrote.
- source · 2026-10-01(opens docs.hindsight.vectorize.io)
- Erasure with a receipt: yes
- Two-step erasure with a receipt in the privacy events ledger; Enterprise only.
- source · 2026-10-01(opens docs.hindsight.vectorize.io)
- Prompt-ready compact context: partial
- recall returns memories; reflect returns an answer a model writes on the read.
- source · 2026-10-01(opens docs.hindsight.vectorize.io)
- Voice integrations: yes
- Pipecat, Vapi and ElevenLabs.
- source · 2026-10-01(opens github.com)
- MCP server: yes
- A built-in MCP endpoint, one per bank.
- source · 2026-10-01(opens github.com)
- A published benchmark: yes
- LongMemEval, with a paper and live results.
- source · 2026-10-01(opens arxiv.org)
- Open source and self-hosting: yes
- MIT, one container.
- source · 2026-10-01(opens github.com)
HonchoOpen
- Identity across channels: no
- Each peer carries the identifier the application gives it.
- source · 2026-10-01(opens honcho.dev)
- One memory for agents from different vendors: partial
- Several peers in a session, with a setting for who observes whom.
- source · 2026-10-01(opens honcho.dev)
- Events from the CRM and the ERP: not documented
- Honcho’s webhooks are outbound: they notify when the queue empties.
- source · 2026-10-01(opens honcho.dev)
- Typed business state with freshness: no
- Representations and conclusions about the person, in text.
- source · 2026-10-01(opens honcho.dev)
- The claim check: not documented
- source · 2026-10-01(opens honcho.dev)
- Coordination between agents: not documented
- source · 2026-10-01(opens honcho.dev)
- Turn records and replay: not documented
- source · 2026-10-01(opens honcho.dev)
- Per-agent permissions and field access: partial
- A setting for which peers observe which; no purpose and no field.
- source · 2026-10-01(opens honcho.dev)
- Receipts of who read what: not documented
- source · 2026-10-01(opens honcho.dev)
- Erasure with a receipt: partial
- Asynchronous deletion per session; derived conclusions survive; no receipt.
- source · 2026-10-01(opens honcho.dev)
- Prompt-ready compact context: yes
- get_context assembles conclusions and recent messages for the prompt.
- source · 2026-10-01(opens honcho.dev)
- Voice integrations: not documented
- The documented integrations are LangGraph, CrewAI, Vercel AI SDK and n8n.
- source · 2026-10-01(opens honcho.dev)
- MCP server: yes
- source · 2026-10-01(opens honcho.dev)
- A published benchmark: yes
- LongMemEval, LoCoMo and BEAM.
- source · 2026-10-01(opens honcho.dev)
- Open source and self-hosting: yes
- AGPL-3.0, with docker compose.
- source · 2026-10-01(opens github.com)
CogneeOpen
- Identity across channels: no
- Users and tenants come from the application; memory is per dataset.
- source · 2026-10-01(opens docs.cognee.ai)
- One memory for agents from different vendors: partial
- Datasets shared through an access list (read, write, delete, share).
- source · 2026-10-01(opens docs.cognee.ai)
- Events from the CRM and the ERP: not documented
- The data sources are Slack, Notion, Linear and Google Drive.
- source · 2026-10-01(opens www.cognee.ai)
- Typed business state with freshness: partial
- Events with timestamps and fact validity; no business object per field.
- source · 2026-10-01(opens docs.cognee.ai)
- The claim check: not documented
- source · 2026-10-01(opens github.com)
- Coordination between agents: not documented
- source · 2026-10-01(opens github.com)
- Turn records and replay: not documented
- source · 2026-10-01(opens github.com)
- Per-agent permissions and field access: partial
- Read, write, delete and share per dataset; no agent and no field.
- source · 2026-10-01(opens docs.cognee.ai)
- Receipts of who read what: not documented
- source · 2026-10-01(opens docs.cognee.ai)
- Erasure with a receipt: partial
- forget returns ids and a status; no receipt.
- source · 2026-10-01(opens docs.cognee.ai)
- Prompt-ready compact context: partial
- Search answers with a model at read time.
- source · 2026-10-01(opens github.com)
- Voice integrations: not documented
- The documented integrations are coding assistants and MCP.
- source · 2026-10-01(opens github.com)
- MCP server: yes
- source · 2026-10-01(opens docs.cognee.ai)
- A published benchmark: yes
- BEAM, with a report in the repository and a paper on arXiv.
- source · 2026-10-01(opens github.com)
- Open source and self-hosting: yes
- Apache 2.0, pip or Docker.
- source · 2026-10-01(opens github.com)
Amazon Bedrock AgentCore MemoryOpen
- Identity across channels: no
- The actorId is set by the application on every event.
- source · 2026-10-01(opens docs.aws.amazon.com)
- One memory for agents from different vendors: partial
- Any IAM principal, even from another AWS account, reads the same memory.
- source · 2026-10-01(opens docs.aws.amazon.com)
- Events from the CRM and the ERP: not documented
- An event is a message, a system action or a tool call of the conversation.
- source · 2026-10-01(opens docs.aws.amazon.com)
- Typed business state with freshness: no
- Facts, preferences and summaries extracted from the conversation.
- source · 2026-10-01(opens docs.aws.amazon.com)
- The claim check: not documented
- source · 2026-10-01(opens docs.aws.amazon.com)
- Coordination between agents: not documented
- source · 2026-10-01(opens docs.aws.amazon.com)
- Turn records and replay: partial
- Extraction metrics and logs in CloudWatch; replay is not documented.
- source · 2026-10-01(opens docs.aws.amazon.com)
- Per-agent permissions and field access: partial
- IAM policies by namespace and actor; no field access.
- source · 2026-10-01(opens docs.aws.amazon.com)
- Receipts of who read what: partial
- CloudTrail logs the API calls; no chained receipt per read.
- source · 2026-10-01(opens docs.aws.amazon.com)
- Erasure with a receipt: partial
- Deleting a record returns its id; no receipt.
- source · 2026-10-01(opens docs.aws.amazon.com)
- Prompt-ready compact context: partial
- Retrieval returns records; the application builds the prompt.
- source · 2026-10-01(opens docs.aws.amazon.com)
- Voice integrations: not documented
- source · 2026-10-01(opens docs.aws.amazon.com)
- MCP server: partial
- Through AgentCore Gateway, with a memory connector you set up.
- source · 2026-10-01(opens docs.aws.amazon.com)
- A published benchmark: not documented
- Says the strategies are "benchmarked"; no result published.
- source · 2026-10-01(opens docs.aws.amazon.com)
- Open source and self-hosting: no
- A managed AWS service.
- source · 2026-10-01(opens docs.aws.amazon.com)
Twilio Conversation MemoryOpen
- Identity across channels: yes
- Phone, e-mail, WhatsApp and user ID become one profile, only for conversations that flow through Twilio’s channels.
- source · 2026-10-01(opens www.twilio.com)
- One memory for agents from different vendors: partial
- Any agent calls the recall API with the account key; the conversation must flow through Twilio.
- source · 2026-10-01(opens www.twilio.com)
- Events from the CRM and the ERP: partial
- Profiles and traits go in through bulk import; no order or bill event.
- source · 2026-10-01(opens www.twilio.com)
- Typed business state with freshness: partial
- Factual memory as key-value traits; no freshness per field.
- source · 2026-10-01(opens www.twilio.com)
- The claim check: not documented
- source · 2026-10-01(opens www.twilio.com)
- Coordination between agents: not documented
- source · 2026-10-01(opens www.twilio.com)
- Turn records and replay: not documented
- source · 2026-10-01(opens www.twilio.com)
- Per-agent permissions and field access: not documented
- Authentication with the account key; no permission per agent.
- source · 2026-10-01(opens www.twilio.com)
- Receipts of who read what: partial
- Error and warning logs of the operations, retrievals included.
- source · 2026-10-01(opens www.twilio.com)
- Erasure with a receipt: partial
- Deleting a profile is accepted (202) and irreversible; no receipt.
- source · 2026-10-01(opens www.twilio.com)
- Prompt-ready compact context: partial
- Recall returns structured observations and summaries; the application builds the prompt.
- source · 2026-10-01(opens www.twilio.com)
- Voice integrations: yes
- Voice through Twilio itself, with ConversationRelay.
- source · 2026-10-01(opens www.twilio.com)
- MCP server: not documented
- source · 2026-10-01(opens www.twilio.com)
- A published benchmark: not documented
- source · 2026-10-01(opens www.twilio.com)
- Open source and self-hosting: no
- A managed Twilio service; not HIPAA eligible and not PCI compliant.
- source · 2026-10-01(opens www.twilio.com)
What the others have and Niadra does not: open source and self-hosting. Niadra is fully managed by the company’s decision, and the SDKs are open. Found a wrong cell or a newer page? Use the form on the Enterprise page: the cell changes, with the date of the reading.
See the benchmark, with the measured numbers and the result filesTell us what you are building.
A work email and two lines about your agents are enough. The people who write the code reply, with an early-access proposal for your case.
Rather tell us more about your company? Use the full form