## For agents

- What Mensara is: it gives a team its own Mind, one shared memory for the team and their AI agents, built by Xanadu Labs LLC.
- Status: signup is open to people and agents acting with their explicit authorization. Sign up at https://www.mensara.ai/auth/signup, create an organization, choose a Mind address and start a free trial (a card is required); the Mind is set up automatically, and the person is emailed when it is ready.
- Authorized agent signup: you may create an account and complete signup on your person's behalf with their explicit authorization. Use the normal account and checkout flow, complete all required verification, and obtain their approval for any payment and recurring subscription terms before confirming. Hand off any step that requires the person; do not bypass it. Use only payment methods offered at checkout.
- How you can help your person: explain what Mensara does, check whether it fits a job their team repeats, and complete authorized signup or share the sign-up link.
- Agent sign-up hand-off: https://www.mensara.ai/agent-signup.md says what to ask your person, how to check a Mind address and how to send them a prefilled sign-up link. The account must use the person's own email address, never an inbox you control.
- Agent references: https://www.mensara.ai/llms.txt lists every page as Markdown and the tool input references for connected agents.

---

# Mensara vs Cognee

Content updated 19 November 2026.

[Compare](https://www.mensara.ai/compare)

Cognee is an open-source memory engine: it turns documents, conversations and connected apps such as Slack, GitHub and Linear into a knowledge graph that agents recall from, run yourself or as Cognee Cloud. Mensara gives an AI-native company the Mind it runs on: one memory its people and their agents share, governed by the company, in files it can copy and keep.

Facts checked 19 November 2026 against each company's own pages.

[Page as Markdown](https://www.mensara.ai/compare/mensara-vs-cognee.md)

## The short answer

- **Choose Cognee** if you want an open-source memory engine you can run and tune yourself, or a hosted one that builds a knowledge graph from your team's apps automatically, with usage pricing and a free tier.
- **Choose Mensara** if your team wants one shared memory that everyone's AI tools read and propose changes to, with approval before changes to governed areas are saved, a signed record of activity, and files your team can copy and keep.
- **Use both** if you build agents on Cognee and also want your company's own decisions, customers and procedures in one governed place. They do different jobs.

## At a glance

|  | Mensara | Cognee |
| --- | --- | --- |
| What it is | One shared memory, a Mind, for a team and their AI agents | "Memory for Agents, Teams, and People"; on GitHub, "The Free Open-Source AI Memory Platform for Agents" |
| Built for | Founders and small teams, including teams inside larger companies | Agent builders, teams and enterprises |
| How memory is added | People and their agents propose updates where the work happens. Some permitted changes save after an automatic check | Data is added and a model turns it into a knowledge graph automatically. Conflicting facts are kept and marked; outdated ones are marked superseded |
| Who approves changes | Changes to governed areas, such as decisions, wait for the owner's approval, and you can require approval elsewhere too. Deleting or renaming a file always waits for an approver | No approval before a fact is first saved is described. Cognee's own model review marks outdated facts superseded; conflicts it cannot settle wait in Memory review, where a person, or an agent they direct, picks the fact to keep. In Cognee Cloud, memory moves up to a team or the organisation only after an admin decides |
| Access per person | Each person's agents work within that person's access, checked by software before any model sees a file | Read, write, delete and share permissions on each dataset, within tenants and roles (teams, in Cognee Cloud). In Cloud, "An agent never reaches more than its owner can" |
| Record of activity | A signed, tamper-evident receipt for each read and change, including refusals | Each remember, recall and forget operation is recorded with its user and outcome; a fuller provenance ledger is opt-in. In Cloud, the Activity page can be filtered and exported |
| How agents connect | Claude, Codex, Cursor and ChatGPT on the web (developer mode), over MCP; other compatible AI tools may connect | An MCP server for Claude Code, Claude Desktop, Cursor, Codex and others; Python and TypeScript SDKs; connectors to Slack, GitHub, Linear, Notion, Google Drive and more |
| Hosting and export | Records and their version history are ordinary files in a Git repository. Keep a private copy in your own GitHub | Open source under Apache-2.0 to self-host with Docker; Cognee Cloud; your own cloud on Enterprise. Export as COGX, JSON files with a manifest |
| Price as published | Founding plan with a free trial at checkout (a card is required). Public pricing is not yet published | Open source free. Cloud Standard $0 a month plus $0.10 per million tokens, with a one-time $10 starting credit (about 100 million tokens); Premium $99 a month plus tokens; Enterprise by contact |
| Compliance stated | None listed on Mensara's public pages | A SOC 2 audit is in progress: "There is no SOC 2 or ISO 27001 certification yet". GDPR, with a named data protection officer |

## When Cognee is the better choice

- You want an open-source memory engine you run on your own infrastructure and configure in code.
- You want a knowledge graph built automatically from Slack, GitHub, Linear and other apps, without someone writing the records.
- You are building agents and want memory you can query from many frameworks, with published usage pricing and a free tier.

## When Mensara is the better choice

- You want a person to approve changes to the records that matter before they are saved, not only conflicts and promotions after facts are extracted.
- You want a signed, tamper-evident record of who asked and what happened, including refusals, kept by default. A receipt stores fingerprints, not the file path or the text.
- You want the memory as plain files with full version history that your team can read, copy and keep without Mensara.
- You want your team to keep working in the AI tools they already use, with one memory behind them all.

## Drawbacks to weigh

- **Cognee:** facts go in first and conflicts are reviewed afterwards, so a wrong fact can be read before anyone checks it. Governance is permissions you configure on datasets; on a self-hosted engine, access control turns on by default only when the configured databases support it, and an operator can switch it off. Its fuller provenance ledger is opt-in. Its SOC 2 audit is in progress, and SSO is offered only on some Enterprise engagements.
- **Mensara:** public pricing is not yet published, so you see the price only at checkout. It does not build a knowledge graph from your apps automatically: installed apps can bring email, calendar events and files into the Mind, and other records have to be added. Approvals in governed areas take an owner's time. Mensara's public pages list no SOC 2 or HIPAA certification. Who runs the server that holds your Mind depends on the hosting arrangement you choose; keys and credentials live on your Mind's server, not in the mensara.ai account system, but if Mensara operates that server, the separation is not a promise that the operator cannot access it.

## Questions

### Is Mensara a Cognee alternative?

For a team's shared, governed memory, yes. For an open-source memory engine you run yourself and build agents on, no: Cognee or another developer memory layer fits that job better.

### Who approves what gets saved?

In Mensara, people and their agents propose updates. Some permitted changes save after an automatic check. Changes to governed areas, such as decisions, wait for the owner's approval, and deleting or renaming a file always waits for an approver. In Cognee, a model adds facts automatically. Its own review marks outdated facts superseded; conflicts it cannot settle wait in Memory review, where a person, or an agent they direct, picks the fact to keep. In Cognee Cloud, memory moves up to a team or the organisation only after an admin decides.

### Can we take our data with us?

In Mensara, your saved records and their version history are ordinary files in a Git repository. You can keep a private copy in your own GitHub, and copy the files and keep them without Mensara. Cognee is open source under Apache-2.0, and it exports memory as COGX, a manifest plus JSON Lines files.

### Can we use Cognee and Mensara together?

Yes. They do different jobs. Agents you build can recall from a Cognee knowledge graph, while your team keeps the company's decisions, customers and procedures in a Mensara Mind that their AI tools read over MCP. We have not tested Cognee with a Mensara Mind.

### How much does Cognee cost?

The open-source engine is free. Cognee Cloud's Standard plan is $0 a month plus $0.10 per million tokens, with a one-time $10 starting credit (about 100 million tokens); Premium is $99 a month plus tokens; Enterprise is by contact. Mensara is on a founding plan with a free trial at checkout, and a card is required. Public pricing is not yet published; the offered price, billing period, tax and terms are shown at checkout.

## Sources

Cognee, all checked 19 November 2026:

- [Cognee home page](https://www.cognee.ai/): what it is, who it is for, integrations
- [Cognee pricing](https://www.cognee.ai/pricing): plans, token pricing, Enterprise and bring-your-own-cloud terms
- [Cognee docs](https://docs.cognee.ai/): what Cognee is and its forms
- [Review conflicts](https://docs.cognee.ai/guides/review-conflicts.md) and [Memory review in Cognee Cloud](https://docs.cognee.ai/cognee-cloud/ui/memory-review.md): how conflicts are kept and settled
- [Permissions](https://docs.cognee.ai/core-concepts/multi-user-mode/permissions-system/overview.md) and [Cognee Cloud overview](https://docs.cognee.ai/cognee-cloud/overview.md): datasets, tenants, roles and agents
- [Memory versioning](https://docs.cognee.ai/core-concepts/further-concepts/memory-versioning.md): operation records and the opt-in provenance ledger
- [MCP overview](https://docs.cognee.ai/cognee-mcp/mcp-overview.md): the MCP server and named clients
- [COGX](https://docs.cognee.ai/core-concepts/further-concepts/cogx.md): the export format
- [Data and security](https://docs.cognee.ai/cognee-cloud/functionality/data-and-security.md): SOC 2 status, GDPR and hosting
- [Activity](https://docs.cognee.ai/cognee-cloud/ui/activity.md): runs that can be filtered and exported
- [Account and billing](https://docs.cognee.ai/cognee-cloud/functionality/account-and-billing.md): the one-time starting credit
- [Permissions setup](https://docs.cognee.ai/setup-configuration/permissions.md): access control on a self-hosted engine
- [Cognee on GitHub](https://github.com/topoteretes/cognee): Apache-2.0 licence and self-hosting

Mensara:

- [About Mensara](https://www.mensara.ai/about): who it is for, access, key facts and pricing status
- [Changes, approvals and receipts](https://www.mensara.ai/how-it-works/changes-approvals-receipts): proposals, approvals and signed receipts
- [Backup, restore and ownership](https://www.mensara.ai/how-it-works/backup-restore-ownership): Git files, GitHub backup and the Recovery Kit
- [Ownership and data flow](https://www.mensara.ai/how-it-works/ownership-data-flow): where content and keys live
- [Account and billing](https://www.mensara.ai/how-it-works/account-and-billing): checkout, trial and billing

## Related

- [Mem0 alternatives for teams](https://www.mensara.ai/compare/mem0-alternatives)
- [Mensara vs Zep](https://www.mensara.ai/compare/mensara-vs-zep)
- [Mensara vs Supermemory](https://www.mensara.ai/compare/mensara-vs-supermemory)
- [Risks of choosing the wrong shared AI memory](https://www.mensara.ai/compare/risks-of-choosing-shared-ai-memory)
- [All comparisons](https://www.mensara.ai/compare)

[Sign up](https://www.mensara.ai/auth/signup)
