Preview. These maps are our reading of public sources and haven't been checked with the projects' maintainers yet.
Redis Agent Memory
Redis's two-tier agent memory (session memory with TTL, plus extracted long-term facts with embeddings), now a managed Redis Cloud service.
redis.io/agent-memory/Changed direction
Repo README now presents Redis Agent Memory as a managed Redis Cloud service (part of 'Redis Iris'); the original open-source server is kept in V0/ 'as an open research artifact, not as the supported production distribution'. Last server release v0.15.2 on 2026-04-10. (checked 2026-10-25)
In Agent memory
Where it stands apart
- Is it actively maintained? active, but changed direction (pivot, fork, or rename) (0% of 21 others)
- How is the main thing licensed? proprietary or closed source (19% of 21 others)
- Can it run entirely on your own device or infrastructure, without the maker's servers? no, it needs the maker's servers (10% of 21 others)
- Do you need an account to use it? account required (10% of 20 others)
- What is the main storage model for long-term memory? vector store of extracted facts or chunks (20% of 20 others)
What it shares with most of the community
- How is it mainly sustained? company with a paid product, tier, or ads (75% of 20 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)
- How can the person the memories are about see and edit them? only through developer APIs or a developer dashboard (62% of 21 others)
- By default, how do old or wrong memories mainly go away? the system updates, merges, or decays them automatically (58% of 19 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)
- Does it publish scores on public memory benchmarks (LoCoMo, LongMemEval, BEAM, etc.)? yes (62% of 21 others)
Nearest neighbors
- Zep 82% of 17 shared answers match
- Honcho 65% of 17 shared answers match
- Supermemory 65% of 17 shared answers match
Every answer
| Question | Answer | Source |
|---|---|---|
| Is it actively maintained? | stands apart active, but changed direction (pivot, fork, or rename) Open-source server pivoted away to a managed service; repo stays active for benchmarks. | source 2026-10-25 |
| How is the main thing licensed? | stands apart proprietary or closed source Managed service; V0 server is Apache-2.0 but unsupported. | source 2026-10-25 |
| How is it mainly sustained? | company with a paid product, tier, or ads Redis Cloud product. | source 2026-10-25 |
| Can it run entirely on your own device or infrastructure, without the maker's servers? | stands apart no, it needs the maker's servers Supported path is Redis Cloud; V0 can still be self-hosted unsupported. | source 2026-10-25 |
| Do you need an account to use it? | stands apart account required Start on Redis Cloud (managed service); self-managed is only a private preview. | source 2026-10-26 |
| Who is it for? | developers | source 2026-10-25 |
| Which shared standard or format does it mainly build on? | none of these (its own format or interface) Redis's own service. | 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 | source 2026-10-25 |
| How can the person the memories are about see and edit them? | only through developer APIs or a developer dashboard | source 2026-10-25 |
| By default, how do old or wrong memories mainly go away? | the system updates, merges, or decays them automatically Session TTL and background promotion/extraction. | source 2026-10-25 |
| Where do memories live in the default setup the docs lead with? | in the vendor's cloud | 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? | stands apart vector store of extracted facts or chunks | source 2026-10-25 |
| What shape does it mainly take (the one its docs lead with)? | memory service (self-hosted server or hosted API) | source 2026-10-25 |
| Is there a first-party MCP server for it? | yes V0 server has an MCP interface; managed service docs list SDKs and REST. | source 2026-10-25 |
| How is memory separated between users or tenants? | built-in scoping by user, agent, session, or tenant IDs user_id and namespaces. | source 2026-10-25 |
| Does it publish scores on public memory benchmarks (LoCoMo, LongMemEval, BEAM, etc.)? | yes Own LongMemEval harness comparing vendors. | source 2026-10-25 |
Sources
This page was derived from:
- GitHub · github.com/redis/agent-memory-server · read 2026-10-25
- GitHub · github.com/redis/agent-memory-server/tree/main/V0 · read 2026-10-25
- Web page · redis.io/agent-memory/ · read 2026-10-25
Are you a maintainer? Claiming and correcting projects is coming soon.