Alternatives
Products that do what Erioon does
Memory for AI
- 1
- 2
- 3
- 4
- 5
- 6IR
Hey HN! I built a proof-of-concept for AI memory using Git instead of vector databases. The insight: Git already solved versioned document management. Why are we building complex vector stores when we could just use markdown files with Git's built-in diff/blame/history? How it works: Memories stored as markdown files in a Git repo Each conversation = one commit git diff shows how understanding evolves over time BM25 for search (no embeddings needed) LLMs generate search queries from conversation context Example: Ask "how has my project evolved?" and it uses git diff to show actual…
2025 · github.com
- 7
- 8
- 9
An OKF-backed Model Context Protocol (MCP) server delivering persistent long-term memory and SQLite FTS5 search for AI agents. - fellowgeek/mcp-memory
25d ago · github.com
- 10
Captures and stores your chat from various AI platforms
Mar 2026 · ai-memory-beta.vercel.app
- 11AM
Most RAG setups fail because they treat memory like a static filing cabinet. When every transient bug fix or abandoned rule is stored forever, the context window eventually chokes on noise, spiking token costs and degrading the agent's reasoning. This implementation experiments with a biological approach by using the Ebbinghaus forgetting curve to manage context as a living substrate. Memories are assigned a "strength" score where each recall reinforces the data and flattens its decay curve (spaced repetition), while unused data eventually hits a threshold and is pruned. To solve the…
Apr 2026 · github.com
- 12
- 13
- 14
- 15
- 16
- 17YA
This is a project that I have been building for a while now, YourMemory is a solution to agentic memory which focuses on pruning of noise rather than hoarding of data. In the current state of agentic memory most of the context is stored in the form of a MD file or is derived through a RAG model where you store each and everything. Both of the solution leads to bloated context which does not optimize the usage of any tokens. In this system we only keep relevant data in our memory and prune all the unnecessary data. The relevance of a data is derived through multiple factors such as recall…
Jun 2026 · yourmemoryai.vercel.app
- 18
An agent that remembers across sessions can keep its memory as curated markdown files, as an auto-mined structured store, or as trained experience.
23d ago · pinglin.tw
- 19
- 20
- 21
- 22HO
Hey HN, It’s Vineeth from Plastic Labs. We've been building Honcho, an open-source memory library for stateful AI agents. Most memory systems are just vector search—store facts, retrieve facts, stuff into context. We took a different approach: memory as reasoning. (We talk about this a lot on our blog) We built Neuromancer, a model trained specifically for AI-native memory. Instead of naive fact extraction, Neuromancer does formal logical reasoning over conversations to build representations that evolve over time. Its both cheap ( $2/M tokens ingestion, unlimited retrieval), token…
Jan 2026 · github.com
- 23
I built a governed memory layer for AI assistants with deletion compaction, vector purge verification, tenant isolation, and audit evidence.
Jun 2026 · github.com
- 24CO
Hi HN, 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
Ranked by how close each launch is in meaning, then by votes. Refine with a description →