Comparisons / LangChain vs Semantic Kernel
LangChain vs Semantic Kernel: Which Agent Framework to Use?
LangChain is the most popular agent framework. Semantic Kernel is Microsoft's enterprise SDK for building AI agents. Here is how they compare — paradigm, ecosystem, and the use cases each one is actually built for.
By the numbers
LangChain
132.3k
21.8k
Python
MIT
2022-10-17
Harrison Chase
Sequoia Capital, Benchmark
$25M Series A (2023), $25M Series B (2024)
3.5M
LangSmith (observability), LangServe (deployment)
Yes
Used by: Notion, Elastic, Instacart
github.com/langchain-ai/langchain→Semantic Kernel
27.6k
4.5k
C#
MIT
2023-02-27
Microsoft
GitHub stats as of April 2026. Stars indicate community interest, not necessarily quality or fit for your use case.
| Concept | LangChain | Semantic Kernel |
|---|---|---|
| Agent | `AgentExecutor` with `LLMChain`, `PromptTemplate`, `OutputParser` | `ChatCompletionAgent` with `Kernel`, instructions, and service config |
| Tools | `@tool` decorator, `StructuredTool`, `BaseTool` class hierarchy | — |
| Agent Loop | `AgentExecutor.invoke()` with internal iteration | — |
| Conversation | `ConversationBufferMemory`, `ConversationSummaryMemory` | — |
| State | LangGraph state channels with typed reducers | — |
| Memory | `VectorStoreRetrieverMemory`, `ConversationEntityMemory` | `SemanticTextMemory` with embeddings and vector stores |
| Guardrails | `OutputParser`, `PydanticOutputParser`, custom validators | — |
| Tools / Plugins | — | `KernelPlugin` with `@kernel_function` decorators, typed parameters |
| Planning | — | `StepwisePlanner`, `HandlebarsPlanner` for multi-step decomposition |
| Orchestration | — | `Kernel.invoke()` with plugin resolution and filter pipeline |
| Multi-Language | — | C#, Python, Java SDKs with shared abstractions |
LangChain vs Semantic Kernel, head to head
LangChain LangChain is the most popular agent framework.
Semantic Kernel Semantic Kernel is Microsoft's enterprise SDK for building AI agents.
Both wrap the same underlying agent pattern — an LLM call, a tool dispatch, a loop — in different abstractions. The choice between them is mostly about which mental model and ecosystem fits the team you have, not which one is technically more capable.
Pick LangChain if
Pick LangChain if langChain adds value when you need production integrations (vector stores, specific LLM providers, deployment tooling). But if you want to understand what's happening — or your use case is straightforward — the plain Python version is easier to debug, modify, and reason about. LangChain is the right fit when the tradeoffs in its intro line up with how your team actually wants to work day-to-day; Semantic Kernel would force you to translate.
Pick Semantic Kernel if
Pick Semantic Kernel if semantic Kernel earns its complexity in enterprise environments with Azure OpenAI, .NET backends, and existing Microsoft infrastructure. But the core agent pattern — LLM call, tool dispatch, loop — is identical to what you can build in 60 lines of Python. Semantic Kernel is the right fit when the tradeoffs in its intro line up with how your team actually wants to work day-to-day; LangChain would force you to translate.
What both add
Both LangChain and Semantic Kernel pull in a class hierarchy and a dependency tree to wrap what is, at the core, an HTTP POST in a while loop. If your use case is straightforward — one provider, a handful of tools, a single agent — the framework cost may exceed the framework benefit. The lesson below shows the same pattern in ~60 lines without either dependency.
Or build your own in 60 lines
Both LangChain and Semantic Kernel implement the same 8 patterns. An agent is a function. Tools are a dict. The loop is a while loop. The whole thing composes in ~60 lines of Python.
No framework. No dependencies. No opinions. Just the code.
Build it from scratch →