Hindsight 1.0 + Memlake - Open source memory for AI agents to learn from experience

Hindsight is open-source memory that lets AI agents learn from experience, #1 on every dataset of the Agent Memory Benchmark. Today it's 1.0, and the API is a promise. We're also launching Hindsight Memlake, a storage engine written in Rust that keeps agent memory in object storage: 100M memories at under 100 ms p99, with no database, consensus cluster or leader. Self-host it free, start on Hindsight Cloud with free credits, or run it in your own cloud with Enterprise.

Add a comment

Replies

Best

Hi Product Hunt, Chris from Vectorize here.

When we launched Hindsight here, the idea was that agents should learn from experience the way people do, not just retrieve documents. After a year in production and #1 results on every dataset of the Agent Memory Benchmark, Hindsight is now 1.0. From here, the API is a promise.

The other half of this launch is the part I'm most excited about as the person who runs it: Hindsight Memlake, for Enterprise customers with very large memory volumes. Agent memory only grows, and every recall runs vector, keyword, graph and time search over all of it. So Nicolò and the team built a storage engine for that shape of data, in Rust:

• Object storage is the only source of truth: no database, no consensus cluster, no leader
• Only two objects ever change, through conditional writes, and the protocols are model-checked in TLA+
• 100M memories at under 100 ms p99 on 4 servers, and recall on a 200k-memory bank went from 5.3 s on Postgres to 113 ms

Hat tip to turbopuffer, whose object-storage-first design inspired a lot of this.

Try Hindsight open source (MIT, runs on Postgres) or on Hindsight Cloud with free credits. Memlake comes with Hindsight Enterprise, and the full engineering write-up is here:

Happy to answer anything about agent memory, Memlake, or why we didn't just use Postgres.

Making this open source is a big plus. I'd love to see how developers use it to build agents tahat actually learn over time.

The API commitment caught my eye, Chris. With memory sitting inside an agent's workflow, predictable upgrades matter as much as the storage underneath.