Memanto; open-source memory agent that remembers, recalls and answers
1–10 of 12 posts
Re: Memanto; open-source memory agent that remembers, recalls and answers
#2I first tried it last week, since then i migrated to this seek thing, really good on recall and easy to manage and maintain. We definitely need our data to be owned by us!
Re: Memanto; open-source memory agent that remembers, recalls and answers
#3I first tried it last week, since then i migrated to this seek thing, really good on recall and easy to manage and maintain. We definitely need our data to be owned by us!
I am so glad you like it :) your comment made my day!
Re: Memanto; open-source memory agent that remembers, recalls and answers
#4I was impressed by their unique approach. They just use a vector store without any LLM for ingestion, and it still works.
Re: Memanto; open-source memory agent that remembers, recalls and answers
#5I was impressed by their unique approach. They just use a vector store without any LLM for ingestion, and it still works.
We have built our own infrastructure on moorcheh.ai, it was the first information-theoretic search engine before Google's research. Moorcheh whitepaper: https://arxiv.org/pdf/2601.11557
Re: Memanto; open-source memory agent that remembers, recalls and answers
#6migrating to Memanto.... it’s exactly the long-term memory layer we needed.
Re: Memanto; open-source memory agent that remembers, recalls and answers
#7migrating to Memanto.... it’s exactly the long-term memory layer we needed.
Thanks for your comment but Memanto is not a "memory layer" it is an active "memory agent". The difference is that memanto is not a passive layer it is an actual agent and it has its own intelligence and AI capabilities independent of your agents.
Re: Memanto; open-source memory agent that remembers, recalls and answers
#8Good that it's open source, though always sus about what they actually do. I've seen a lot of supposed memory layers end up just being a RAG system with remember and recall over pg_vector or something. I'll admit I haven't really looked into the code to verify whether that's actually the case so open to being fact checked.
Re: Memanto; open-source memory agent that remembers, recalls and answers
#9Good that it's open source, though always sus about what they actually do. I've seen a lot of supposed memory layers end up just being a RAG system with remember and recall over pg_vector or something. I'll admit I haven't really looked into the code to verify whether that's actually the case so open to being fact checked.
I assure you it is not a vibe coded pg_vector wrapper. It is built on top of a custom made search engine that is state-of-the-art in semantic search. Check out moorcheh.ai, cloud infrastructure, moorcheh on-prem and moorcheh-on-edge.
Here is the paper explaining how we came up with the idea of memanto: https://arxiv.org/abs/2604.22085
Re: Memanto; open-source memory agent that remembers, recalls and answers
#10Good that it's open source, though always sus about what they actually do. I've seen a lot of supposed memory layers end up just being a RAG system with remember and recall over pg_vector or something. I'll admit I haven't really looked into the code to verify whether that's actually the case so open to being fact checked.
I assure you it is not a vibe coded pg_vector wrapper. It is built on top of a custom made search engine that is state-of-the-art in semantic search. Check out moorcheh.ai, cloud infrastructure, moorcheh on-prem and moorcheh-on-edge. Here is the paper explaining how we came up with the idea of memanto: https://arxiv.org/abs/2604.22085
Thanks for the reply! So you've actually built your own custom vector DB on top of the memory layer? That's definitely something new.
I'm honestly not sold on memory layers as a whole, I find that adding more context only serves to make the LLM's dumber and I've been slowly leaning towards just having no memory and working on features in isolation.
You've done benchmarks already so that's another step in the right direction, do you find that these benchmarks are good indications of practicality? Have you seen a major difference in LLM performance utilizing this as a memory layer?