Running Semantic Kernel or AutoGen in production?Plan your move to Microsoft Agent Framework

LangChain Development

Language-model applications built with LangChain, in Python or TypeScript: answers from your own documents, agents that call your tools, and upgrades of older LangChain code to the current 1.x release. Tested, traced and handed over to your team.

LangChain today

LangChain is an open-source framework for building applications on language models, in Python and in JavaScript/TypeScript, released under the MIT licence. LangChain 1.0 was released in October 2025, and as of October 2026 the stable line is still 1.x. LangChain’s release policy says breaking changes to its public API come only in a major release such as 2.0, although features marked beta can still change.

In LangChain’s own words, its agents are built on top of LangGraph, its lower-level library. LangGraph lets an agent resume from where it left off after a failure (durable execution and persistence), and lets a person inspect or change the agent’s work at any point (human-in-the-loop). It has its own 1.x release line and can also be used without LangChain.

LangSmith is LangChain’s separate commercial platform for tracing, evaluating and deploying agents. It is optional: the open-source libraries run without it.

What we build with LangChain

Answers from your documents

Retrieval over your own content, so answers come from your documents and can cite them. In Python on Azure, the langchain-azure-ai package, which Microsoft describes as “the Microsoft-maintained set of LangChain integrations for Azure”, connects LangChain to Azure AI Search. We prepare and index your documents the way we do for our custom AI solutions.

Agents that call your tools

Agents built with create_agent, LangChain’s standard way to build agents since 1.0, calling your APIs and databases through tools you define, with middleware adding checks before and after each model call.

Structured extraction

Turning emails, forms and free text into structured records that your systems can store, validate and act on.

Your choice of model

Microsoft Foundry models through langchain-azure-ai (Python only), Azure OpenAI through langchain-openai (@langchain/openai in JavaScript), or another provider, chosen by testing candidates on your own tasks.

Tools over MCP

Connecting agents to tools published over the Model Context Protocol (MCP). In Python, LangChain’s MCP support is now built in but still in beta; in JavaScript it comes through the @langchain/mcp-adapters package.

Upgrading older LangChain code

LangChain 1.0 changed how agents are built. create_agent replaced LangGraph’s create_react_agent, middleware took over customising agent behaviour, messages gained provider-neutral content blocks, and legacy chains and retrievers moved to a separate langchain-classic package. LangChain 1.x needs Python 3.10 or later, but the langchain-azure-ai package needs Python 3.11 or later, so we move projects to Python 3.11 or a newer release that still receives security fixes. LangChain’s migration guide for version 1 (opens in a new tab) covers the details.

There is a deadline, too. LangChain’s release policy keeps LangChain 0.3 in maintenance mode, with security patches and critical bug fixes only, until December 2026, so code still on it should move to 1.x before then.

  1. Take stock

    We list the chains, agents, integrations and package versions in use, and note anything that depends on deprecated packages.

  2. Record today’s behaviour

    Before changing any code, we run a set of real questions through the application and keep the answers, so the upgrade can be compared against them.

  3. Upgrade in small steps

    Package by package, running the questions again after each step, rather than in one large change that is hard to check.

  4. Compare and hand over

    We compare the answers before and after, fix the differences that matter and document what changed, so your team can keep the code current.

LangChain or Microsoft Agent Framework?

Microsoft’s own guidance treats Microsoft Agent Framework and LangGraph as alternative code-first frameworks. Microsoft Foundry’s hosted agents, generally available since July 2026 in selected Azure regions, can run either. Microsoft says investments in LangGraph “carry forward” on Foundry, and calls Agent Framework its “opinionated, open-source agent framework” for teams starting fresh. The recommendation in the last row of this table is ours.

LangChain and Microsoft Agent Framework compared, as of October 2026
AspectLangChain (with LangGraph)Microsoft Agent Framework
LanguagesPython and JavaScript/TypeScript.NET (C#) and Python
LicenceMITMIT
On Microsoft FoundryHosted agents can run LangGraph agents written in PythonHosted agents run Agent Framework agents, and Microsoft documents it as the recommended orchestration layer for them, although its Foundry hosting packages are still prerelease
TracingLangSmith, LangChain’s optional commercial platform, which also accepts OpenTelemetry tracesOpenTelemetry, built in
We recommend it whenYou already have LangChain code that your Python or TypeScript developers maintainYou are starting new agent work, you work in .NET, or you want agents that run on Microsoft Foundry and reach people in Microsoft 365; see Microsoft Agent Framework development

How we work on LangChain projects

  • Every change to a prompt, a model or a step in the chain checked against an evaluation set: real questions paired with the answers you expect.
  • Each step traced, so a wrong answer can be tracked to the step that produced it, in LangSmith or in the tracing tool you already use.
  • Cost per request watched from the first prototype, with smaller models used for the simple steps.
  • Code, prompts, tests and documentation handed over to your team. To start with a review of what you have, book a free discovery call (opens in a new tab).
Consulting
From ₹2,500 (US$40) an hour
Monthly retainer
From ₹2,00,000 (US$4,000) a month
Pilots and fixed-scope projects
Quoted per statement of work

GST is added to Indian invoices. Rate cards by business size and add-ons are on our pricing page.

Frequently Asked Questions

Can you take over an existing LangChain project?

Yes. We start by reviewing the code, the package versions it depends on and how it is tested, and then agree with you what to fix or upgrade first.

Should we upgrade to LangChain 1.x?

Yes, if you are still on LangChain 0.3: its maintenance, limited to security patches and critical bug fixes, runs only until December 2026, while 1.x is the active line. LangChain’s release policy says breaking changes to the public API will come only in a major release such as 2.0, although features marked beta can still change.

Do we need LangSmith?

No. LangSmith is LangChain’s commercial platform for tracing, evaluation and deployment, and the open-source libraries run without it. We use it when you already have it or want it, and other tracing tools when you do not.

Can a LangChain application run on Azure?

Yes. The langchain-azure-ai Python package, which Microsoft describes as “the Microsoft-maintained set of LangChain integrations for Azure”, connects LangChain to Microsoft Foundry models, Azure AI Search and other Azure services, though some of its features were still in preview as of October 2026. Microsoft Foundry’s hosted agents, available in selected Azure regions, can also run agents built with LangGraph in Python.

Should we use LangChain or Microsoft Agent Framework?

Keep LangChain if your Python or TypeScript developers already maintain LangChain code; we extend and upgrade that code. For new agent work, for .NET teams, or for agents meant to run on Microsoft Foundry and reach people in Microsoft 365, we usually recommend Microsoft Agent Framework.

Python or JavaScript?

LangChain’s 1.x line covers both. We use the language your team already maintains, so the code stays easy for you to own after handover.

What does a LangChain project cost?

Consulting starts at ₹2,500 (US$40) an hour and monthly retainers at ₹2,00,000 (US$4,000); pilots and fixed-scope projects are quoted per statement of work after a free discovery call.
Free discovery call

Tell us what your agent should do

We'll tell you the simplest approach that will work — Microsoft Agent Framework, Copilot Studio or no agent at all — and what a pilot would involve.

Mon–Fri, 9 AM–6 PM IST • Reply within 1 business day