Stacks and Flows

LangChain

Open-source framework ecosystem for LLM applications, with LangGraph for stateful orchestration.

framework open-source Updated 2026-05-09
Visit LangChain →

Pros

  • Broad ecosystem of model, retrieval, tool, and data integrations
  • LangGraph (the orchestration sibling) is genuinely good at stateful, multi-step agents
  • Model-agnostic — swap OpenAI, Anthropic, open models, or local LLMs at the config layer
  • Large public documentation and community-example surface
  • LangSmith provides managed tracing and evaluation features on current plans

Cons

  • Reputation for over-abstraction is partly earned — you can fight the framework before you fight the problem
  • API churn has historically been rough; v0.1 → v0.2 → v0.3 broke a lot of code
  • LangChain (the framework) and LangGraph (the orchestrator) confuse newcomers about what to use when
  • No affiliate program; LangSmith has paid tiers but no revenue share for content sites
  • Production monitoring is paid (LangSmith) — the OSS path is observable, but not turnkey

Best for

  • Teams who want model portability and the largest connector ecosystem
  • Engineers building stateful, multi-step agent workflows (LangGraph)
  • Anyone who wants to read 100 community examples before writing their own

What it is

LangChain is an open-source framework ecosystem for LLM-powered applications and agents. It includes langchain packages for integrations and application components, LangGraph for stateful orchestration, and LangSmith as a managed observability and evaluation product.

For agent builders that need explicit state and control flow, LangGraph is the relevant orchestration layer. LangChain components can still provide integrations and model abstractions underneath it. Simpler tool-calling workloads may not need a graph runtime.

Who it’s for

LangChain/LangGraph is a candidate for engineering teams that value provider and integration optionality. Portability is not automatic: model features, tool schemas, prompts, and deployment choices can still be provider-specific, so test the adapters you expect to switch.

It’s a poor fit for teams who want minimal abstraction (use the official OpenAI or Claude SDK), and for teams who want a polished no-code UI (use Dify or Lindy).

Strengths

  • Ecosystem. The project publishes integrations for major model providers, vector stores, document loaders, and tools; support depth varies by integration.
  • LangGraph orchestration. State, checkpointing, interrupts, and graph control flow are first-class concepts.
  • Provider adapters. Common interfaces can reduce switching work, but provider-specific behavior and features still need retesting.
  • Community surface. Documentation, templates, and community-maintained integrations are widely available.
  • LangSmith. Managed tracing, evaluation, and prompt tooling are available; check current plan limits and data-handling requirements.

Weaknesses / Watch out

  • Abstraction tax. For simple use cases, an official model SDK can require less framework surface. Compare maintainability rather than applying a line-count threshold.
  • API churn history. v0.1 → v0.2 → v0.3 transitions broke a lot of community code. The current API is more stable, but there’s still scar tissue.
  • Two frameworks, one brand. “Should I use LangChain or LangGraph?” is the most-asked beginner question. The answer is “use LangGraph for agent orchestration, LangChain for the connectors LangGraph uses underneath” — but it shouldn’t take a paragraph to explain.
  • Observability choice. LangSmith has paid plans; an open telemetry stack requires separate integration and operational ownership.
  • No affiliate. Pure SEO traffic value for publishers — no revenue share on LangSmith referrals at the time of writing.

Best paired with

  • LangGraph specifically for agent work — don’t reach for LangChain core’s older agent abstractions in 2026; LangGraph is the path.
  • Anthropic Claude or OpenAI as the model layer — both are well-supported, and the framework’s portability story actually pays off here.
  • Postgres or Redis for LangGraph checkpointing in production deployments.

Verdict

Recommended for teams that need a broad integration layer or explicit LangGraph orchestration. Use official model SDKs when a smaller provider-specific surface is enough. For visual building, compare actively maintained platforms; provider portability still requires workload-specific testing.

Sources

FAQ

Is LangChain free?
LangChain has a free tier or open-source edition. See pricing details on the official site for paid features and usage limits.
What is LangChain best for?
Teams who want model portability and the largest connector ecosystem Engineers building stateful, multi-step agent workflows (LangGraph) Anyone who wants to read 100 community examples before writing their own
What are the main downsides of LangChain?
Reputation for over-abstraction is partly earned — you can fight the framework before you fight the problem API churn has historically been rough; v0.1 → v0.2 → v0.3 broke a lot of code LangChain (the framework) and LangGraph (the orchestrator) confuse newcomers about what to use when
Who should use LangChain?
Open-source framework ecosystem for LLM applications, with LangGraph for stateful orchestration. See our review for the full pros and cons.