Uploaded September 2026 | Updated September 2026, 44 minutes ago

---

Most agentic memory systems just store every message, search that pile with the latest user turn, and dump the results into context.

We've spent the last year building a memory service at Weaviate, and that approach breaks: context gets overloaded, retrieval fails, and contradictory and outdated facts lead to a system that worsens over time.

𝗘𝗻𝗴𝗿𝗮𝗺 treats memory as engineered infrastructure instead of storage bolted onto the app. Memory gets 𝗮𝗰𝘁𝗶𝘃𝗲𝗹𝘆 𝗺𝗮𝗶𝗻𝘁𝗮𝗶𝗻𝗲𝗱, not accumulated.

This video walks through why these failures happen, plus a full setup of a basic chat app with Engram.

Engram: weaviate.io/product/engram
Demo: engram.playground.weaviate.io



▬▬▬▬▬▬▬▬▬▬▬▬ CONNECT WITH US ▬▬▬▬▬▬▬▬▬▬▬▬

- Visit weaviate.io
- Star us on GitHub github.com/weaviate/weaviate
- Stay updated and subscribe to our newsletter: newsletter.weaviate.io
- Try out Weaviate Cloud for free here: https://console.weaviate.cloud/

Got a question?

- Forum: forum.weaviate.io

Connect with us on

- Twitter: twitter.com/weaviate_io
- LinkedIn: linkedin.com/company/weaviate-io