You pick an agent framework to build the agent. The framework answers how the agent reasons: the graph, the roles, the tools, the step where a person signs off. It says nothing about who owns the system the agents run on, or how the work they produce gets reviewed.
That second question is the one teams hit late. Kortix is the open-source AI Operating System a company owns end to end, and the decision between a framework and a platform is about ownership rather than capability.
What each one is
LangGraph is a low-level orchestration framework for building stateful agents, released under the MIT license. Its own repository describes durable execution, human-in-the-loop interrupts, short and long-term memory, and LangSmith for debugging and deployment. You write the agent logic in Python, host it yourself, and wire in the models and tools your application needs. The framework gives a developer exact control, and that control is the point.
CrewAI is an open-source Python framework for multi-agent workflows, also MIT-licensed. It gives two primitives: Crews, teams of role-based agents that collaborate and delegate, and Flows, event-driven automations with explicit state and branching. For a team already building in Python, both are a short path from nothing to agents that work together.
Kortix is different in kind. It is the open-source AI Operating System where a company's agents, skills, memory and connectors live as files in one git repo the company owns. Each session runs on its own isolated cloud computer, and the work an agent produces lands as a change request a person reviews against the diff before it reaches the main branch. There is no framework to import and no application to build around it; the repo is the system.
A framework answers how an agent thinks. An owned platform answers where the system lives, who can read it, and who approves what it changes.
Framework or platform: the decision
| Kortix | LangGraph | CrewAI | |
|---|---|---|---|
| What it is | A company's agents, memory and connectors in one owned repo | A low-level framework for stateful agents | A Python framework for multi-agent workflows |
| Open source | Yes | Yes, MIT | Yes, MIT |
| Who runs it | The company, cloud, VPC or on-prem | You deploy the library | You deploy the app |
| Shared memory | Company memory as files in the repo | Memory in your own store | Per-run state you persist |
| Human review | A change request a person approves | Interrupts you code | Review you add in code |
| Model choice | Any model, your keys | Model-agnostic | Any LLM through its API |
Where a framework is the right tool
A framework is the right choice when a single team builds agent behavior inside an application it already runs and owns. You want the graph and the state to be code you control, you want to test it like any other software, and the agents are a feature of your product rather than the way the whole company works. Both LangGraph and CrewAI are strong engines for that job.
Where a team outgrows it
The pressure arrives when more than one person and more than one agent share the same context. Three things change at once.
Shared state becomes the first problem. When several agents need the same company memory, and several people need to see what each one learned, a store inside one application stops being the right home. Kortix keeps that memory as files in a repo the whole team versions and reviews.
Reaching real tools is the second. Wiring a CRM, a billing system and a code host into agent logic stays application plumbing until the rules about which agent may touch which tool need to live somewhere a reviewer can read. Kortix reaches 3,000+ apps in a click, plus MCP, OpenAPI, Postman, GraphQL and raw HTTP, and connector credentials are brokered server-side so they never enter the machine.
Review is the third. Work that changes something the company depends on should land the way code lands. In Kortix, a session cuts its own branch, an agent proposes its work as a change request with the exact diff, and merge is default-deny for agents. A person decides what ships.
What an owned platform adds
Because Kortix keeps the whole system in one repo, you can read it, fork it and run it yourself. Self-hosting is free, and the same stack runs on Kortix Cloud, in your VPC or on your own on-prem network. Any model provider works with your own keys, including the ChatGPT plan you already pay for. Per-resource permissions cover people and agents, and every action is recorded.
The point is not that a framework is worse. A framework is a building block, and a building block is exactly what a developer wants for one application. The point is that a company eventually needs a place where the agents, the memory, the rules and the review all live together, in something it owns.
If you are weighing the two, start with what your team has to own. Kortix on GitHub is where you read, fork and audit the whole thing, and you can run your first session for free at kortix.com.
Top comments (0)