Alternatives
Products that do what Vektor memory launch does
Persistent graph memory for AI agents, self-hosted
- 1
- 2
- 3
- 4
- 5
- 6
- 7CO
I keep running in the same problem of each AI app “remembers” me in its own silo. ChatGPT knows my project details, Cursor forgets them, Claude starts from zero… so I end up re-explaining myself dozens of times a day across these apps. The deeper problem 1. Not portable – context is vendor-locked; nothing travels across tools. 2. Not relational – most memory systems store only the latest fact (“sticky notes”) with no history or provenance. 3. Not yours – your AI memory is sensitive first-party data, yet you have no control over where it lives or how it’s queried. Demo video:…
2025 · github.com
- 8
An agent that remembers across sessions can keep its memory as curated markdown files, as an auto-mined structured store, or as trained experience.
22d ago · pinglin.tw
- 9
- 10
- 11
- 12
An OKF-backed Model Context Protocol (MCP) server delivering persistent long-term memory and SQLite FTS5 search for AI agents. - fellowgeek/mcp-memory
24d ago · github.com
- 13
- 14
- 15
Open Source Context Infrastructure for AI Agents
May 2026 · ravbyte-ai.github.io
- 16
- 17
I've been working on Polign and built a small prototype around something I've been thinking about with agent memory. I have built a lightweight/stateless vector db + BM25 search which works really well with typed facts and structured queries. It uses your own S3, or GCS bucket as primary storage, and restarting a node is fairly quick. Demo + writeup: https://polign.com/blog-edge-agent-memory Live search demo: https://demo.polign.com Docs: https://polign.com
11d ago · polign.com
- 18BA
Tired of AI coding tools that forget everything between sessions? Every time I open a new chat with Claude or fire up Copilot, I'm back to square one explaining my codebase structure. So I built something to fix this. It's called In Memoria. Its an MCP server that gives AI tools persistent memory. Instead of starting fresh every conversation, the AI remembers your coding patterns, architectural decisions, and all the context you've built up. The setup is dead simple: `npx in-memoria server` then connect your AI tool. No accounts, no data leaves your machine. Under the hood it's TypeScript +…
2025 · github.com
- 19SM
Apr 2026 · github.com
- 20MO
Hey HN! I'm Arindam, part of the team behind Memori (https://memori.gibsonai.com/). Memori adds a stateful memory engine to AI agents, enabling them to stay consistent, recall past work, and improve over time. With Memori, agents don’t lose track of multi-step workflows, repeat tool calls, or forget user preferences. Instead, they build up human-like memory that makes them more reliable and efficient across sessions. We’ve also put together demo apps (a personal diary assistant, a research agent, and a travel planner) so you can see memory in action. Current LLMs are stateless…
2025 · github.com
- 21
- 22
- 23TA
Hi HN, There’s been a lot of discussion lately around context graphs, decision traces, and how AI systems reason. One thing we kept running into: when AI agents make real decisions, the why behind those decisions often disappears. The context is scattered across prompts, tools, policies, and approvals. Logs show what happened, but not why it was allowed. TraceMem is an attempt to make decision context durable. It records the reasoning, authority, and context behind AI actions as a system of record, not as monitoring data, but as memory. Happy to share more details or answer questions. - Tommi
Jan 2026 · tracemem.com
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →