Frameworks, orchestrators, memory layers, eval harnesses, deployment targets: what each piece does, what it composes with, and what got abandoned. Written by people who wire these things together.
Send the stack reportEvery layer of the agent stack in one diagram: what is production-grade, what is a demo, and what is quietly unmaintained.
Which memory layer actually works with which framework, which eval harness plugs into which pipeline. The wiring, not the marketing.
Agent projects that died, and the pattern behind why. Cheaper to read about than to build on.
Pinecone vs Weaviate vs Chroma: Choosing the Memory Layer for Your Agent Stack
Three vector stores, three ownership models: fully managed, open source with cloud, and usage-first serverless. Verified pricing, licensing and lock-in risk for the memory layer of your agent stack.
LangGraph vs LlamaIndex vs Haystack: Picking the Orchestration Layer of Your Agent Stack
Three frameworks, three centers of gravity: state machines, retrieval, typed pipelines. What each one composes with, what it locks in, and how to choose without regret.
One email a month: map changes, two composition notes, one graveyard entry.
No spam. Unsubscribe anytime. Privacy.
It is a map, not a phone book. We cover fewer tools with wiring notes on how they compose, rather than listing everything with a logo grid.
No. Placement on the map cannot be bought. If we ever run sponsorships, they will be labeled and separate from the map itself.
Builders who ship agent systems for real workloads and keep notes. The report is the cleaned-up version of those notes.
Yes, where they matter to real architectures, with the same standard: what it composes with and what locks you in.