Overview
Before step 1 of 6
You will leave with a shortlist and an honest sense of what each framework will make you build anyway.
The framework chooser — You are evaluating frameworks and want to compare with eyes open.
You are evaluating frameworks and want to compare with eyes open.
Path position
The framework chooser: You are evaluating frameworks and want to compare with eyes open.
This is inferred from the page and path structure. Nothing is saved as completion state.
Begin path
What frameworks actually sit on top of
Framework comparisons make sense only against the stack they layer on. Re-grounds the rest of the path.
Start step 1Steps
What frameworks actually sit on top of
Framework comparisons make sense only against the stack they layer on. Re-grounds the rest of the path.
You should be able to name the layers a framework owns and the layers it leaves to you.
The framework hub
See the field of options and how this site categorises them before opening any single profile.
You should be able to name two axes the hub uses to differentiate frameworks.
The deep-dive baseline
LangGraph is treated as the baseline across the site. Reading it first gives you a yardstick for the others.
You should be able to describe LangGraph's mental model in one sentence — what is the primary abstraction.
A contrasting profile
Comparing one alternative to the baseline reveals the design-space — what a framework choice actually trades.
You should be able to name one thing CrewAI makes easy that LangGraph makes you wire yourself, and vice versa.
Protocols so your choice doesn't lock you in
The open protocols an agent speaks — MCP to tools, A2A to other agents, AG-UI to UIs — make the framework boundary less terminal. Read this before committing.
You should be able to name one boundary each of MCP and A2A crosses, and one protocol you would not reach for yet.
What the framework still makes you build
Every framework punts state shape, persistence, and observability back to you. Knowing this caps framework enthusiasm.
You should be able to name the three production pillars and which of them your candidate framework actually handles.