Preview. These maps are our reading of public sources and haven't been checked with the projects' maintainers yet.
LongMemory (formerly OpenMemory)
Local-first, self-hosted TypeScript memory engine: immutable, temporal, governed memory in SQLite with graph recall, served over npm, CLI, HTTP, MCP, dashboard and VS Code.
CaviraOSS/OpenMemory now redirects to CaviraOSS/LongMemory; commits through 2026-10-18; last GitHub release v1.3.0 2025-12-20. (checked 2026-10-25)
In Agent memory
Where it stands apart
- Which shared standard or format does it mainly build on? a SQL database (Postgres, SQLite) (14% of 21 others)
- By default, how do old or wrong memories mainly go away? they stay but are marked superseded (old facts are kept) (16% of 19 others)
- Where do memories live in the default setup the docs lead with? on the end user's own device (14% of 21 others)
What it shares with most of the community
- Is it actively maintained? active (67% of 21 others)
- How is the main thing licensed? permissive open source (MIT/Apache/BSD) (67% of 21 others)
- Can it run entirely on your own device or infrastructure, without the maker's servers? yes (67% of 21 others)
- Who is it for? developers (76% of 21 others)
- In the default setup, who mainly decides what gets remembered? the system, by extracting memories from conversations or data in the background (67% of 21 others)
- Does it work with models from different LLM vendors? yes, model-agnostic (86% of 21 others)
- Is there a first-party MCP server for it? yes (67% of 21 others)
- How is memory separated between users or tenants? built-in scoping by user, agent, session, or tenant IDs (62% of 21 others)
Not documented
The public sources we read don't say:
- How is it mainly sustained?
Nearest neighbors
- Graphiti 75% of 16 shared answers match
- Cognee 63% of 16 shared answers match
- MCP reference memory server 63% of 16 shared answers match
Every answer
| Question | Answer | Source |
|---|---|---|
| Is it actively maintained? | active | source 2026-10-25 |
| How is the main thing licensed? | permissive open source (MIT/Apache/BSD) Apache-2.0 | source 2026-10-25 |
| How is it mainly sustained? | Not documented Org-run OSS with no sponsors, pricing or paid offering listed; sustainability model unclear. | source 2026-10-26 |
| Can it run entirely on your own device or infrastructure, without the maker's servers? | yes | source 2026-10-25 |
| Do you need an account to use it? | no account Local SQLite default; no service or external database required. | source 2026-10-26 |
| Who is it for? | developers | source 2026-10-25 |
| Which shared standard or format does it mainly build on? | stands apart a SQL database (Postgres, SQLite) Memory engine over SQLite; MCP one of several interfaces. | source 2026-10-26 |
| In the default setup, who mainly decides what gets remembered? | the system, by extracting memories from conversations or data in the background ingest() extracts claims; integrations capture automatically. | source 2026-10-25 |
| How can the person the memories are about see and edit them? | directly, as readable files or in a UI they control Local dashboard and VS Code extension. | source 2026-10-25 |
| By default, how do old or wrong memories mainly go away? | stands apart they stay but are marked superseded (old facts are kept) Immutable memory with separate recorded/valid time; decay affects ranking but content is not rewritten. | source 2026-10-25 |
| Where do memories live in the default setup the docs lead with? | stands apart on the end user's own device | source 2026-10-25 |
| Does it work with models from different LLM vendors? | yes, model-agnostic | source 2026-10-25 |
| What is the main storage model for long-term memory? | knowledge graph (usually with vectors alongside) Graph over SQLite. | source 2026-10-25 |
| What shape does it mainly take (the one its docs lead with)? | library or API primitive you build into your app | source 2026-10-25 |
| Is there a first-party MCP server for it? | yes | source 2026-10-25 |
| How is memory separated between users or tenants? | built-in scoping by user, agent, session, or tenant IDs Project, tenant, user, team, role, agent scopes. | source 2026-10-25 |
| Does it publish scores on public memory benchmarks (LoCoMo, LongMemEval, BEAM, etc.)? | no Internal benchmark smoke gate only. | source 2026-10-25 |
Sources
This page was derived from:
- GitHub · github.com/CaviraOSS/LongMemory · read 2026-10-25
RSS for this project · Its own release feed
Are you a maintainer? Claiming and correcting projects is coming soon.