The category splits cleanly between memory and data workflows
Teams often treat agent tooling as one market, but it is more useful to divide it into two real jobs. Some products are built around persistent memory and long-lived agent behavior. Others are built around retrieval, parsing, extraction, and orchestration over private data. The right choice depends on which problem is more central to the product.
That is why Letta and LlamaIndex feel so different in practice. Letta is the memory-first choice. LlamaIndex is the document-and-data workflow choice. LangGraph is often the fit when the team wants a more explicit orchestration layer without buying into a document platform or memory platform as strongly.
- Choose Letta when memory and long-lived agent state are the hard part.
- Choose LlamaIndex when parsing, indexing, and acting over documents is the hard part.
- Choose LangGraph when orchestration control is the hard part.


