polign.com
Show HN: A lightweight, stateless database for agent memory
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
评论
5 条预览评论 · 正在加载完整讨论请先登录 h4cker 账号，然后连接 Hacker News 后发表评论。
For a coding agent, just build an agent memory that is repo-aware and stores its files in respective repos. you can do this very quickly with any agent, just ask it to research memory systems like coala and propose an architecture
There are countless agent memory stores today. Closed source is a non-starter.
So what's stopping me from using one of the million other versions of this that already exist? Or, even better, pointing Fable to your site and having it just develop its own version of this that I completely own? I'm throwing in a bit of stank in those questions because I don't see anything here that's particularly unique, and keeping this closed and costly is just... absurd. I've vibe coded the same exact thing multiple times. It works, but it's only as useful as the philosophy of the person using it allows it to be. So why would someone choose your solution? A vector database hosted in S3 is effectively trivial to set up at this point in time. What are you offering that I can't get from prompting a powerful enough model? If the answer to that question isn't the first thing people read when they open this post, then you can just consider all of this worthless and save yourself the hassle.
This looks promising! Curious why you named it `Polign`?
Closed source - for those who maybe miss this. litestream with sqlite vector based design would be more apt for someone.