What LangChain gives a team
LangChain is a library for building an agent harness. Its own docs describe an agent as a model plus a harness, and give you create_agent to compose one from a model, a set of tools, a prompt, and middleware that shapes behavior. LangChain supports OpenAI, Anthropic, Google, and other providers behind one interface, so a team can switch a model without rewriting every call site. The agent machinery is built on LangGraph, which adds durable execution, persistence, and human-in-the-loop support. The application, the prompts, and the control flow around the loop stay with your engineers.
The layer a platform adds
A harness runs one agent inside a process that you build, deploy, and watch. A platform adds the parts a company needs around that loop: where the agents and their skills live, where the memory they work from is stored, how they reach your tools, and how their output is reviewed before it counts. In Kortix those parts are files in one git repo you own. Agents and skills are markdown, memory accumulates as files, connectors are declared in kortix.yaml, and each session runs on its own cloud computer. Session work reaches main through a change request a person reviews, and merge is default-deny for agents.
When to pick which
Pick LangChain when the agent is a feature of your product and your engineers want to place every prompt, tool, and branch themselves. The library stays inside your application, and LangSmith traces what happens at runtime. Pick Kortix when the agent is part of how the company works and the requirement is ownership: one repo that holds the agents, skills, memory, and connectors, work that lands as reviewed changes, and a model you can swap. Framework or platform walks through the decision, and Kortix versus LangGraph compares the layer under LangChain.