Skip to main content
LangSmith Deployment is a workflow orchestration runtime purpose-built for agent workloads. It provides the managed infrastructure agents need to run reliably in production at scale, supporting the full lifecycle from local development to deployment. LangSmith Deployment is framework-agnostic: you can deploy agents built with LangGraph or other frameworks.
LangSmith Deployment requires a Plus plan or above.
Get started building in minutes with the Cloud agent deployment quickstart.

Agent Server

Agent Server’s durable execution engine powers the core primitives: assistants to manage configurations, threads to persist state, and runs to execute workloads.

Core capabilities

Stream output to users, pause for human review, handle concurrent input, and connect agents via MCP and A2A—all available in Agent Server.

Tutorials

Guided examples to build production-ready agents for your use case.

Advanced configuration

Authentication, encryption, custom routes, and short- and long-term memory stores.

​
Agent deployment workflow

Start here if you’re building or operating agent applications. This section is about deploying your application. If you need to set up LangSmith infrastructure, the Platform setup section covers infrastructure options.

1. Test locally

Run your app on a local development server.

2. Configure

Set up dependencies, project structure, and environment config.

3. Choose hosting & deploy your agent

Select Cloud, Hybrid, or Self-hosted, then deploy via git push, Docker image, or standalone server.

4. Monitor

Track traces, alerts, and dashboards.

​
Capabilities

​
Studio

Studio connects to any Agent Server (local or deployed) and gives you an interactive environment for developing and debugging agents. Visualize execution graphs, inspect state at any checkpoint, step through runs, modify state mid-execution, and branch to explore alternative paths.

​
Agent composition

Agents don’t run in isolation. RemoteGraph lets any agent call other deployed agents using the same interface you use locally: a research agent delegates to a search agent on a different deployment, a routing agent dispatches to specialized sub-agents. The agents don’t need to know whether they’re calling something local or remote. Native support for MCP and A2A means your deployed agents can expose and consume tool interfaces and agent-to-agent protocols alongside the broader ecosystem.

​
Deployment options

Same runtime, same APIs. What changes is who manages the infrastructure. For a comparison, refer to Platform setup.

​
Reference & operations

​
Securing and customizing your server

​
Operations

​
Reference

Edit this page on GitHub or file an issue.
Connect these docs to Claude, VSCode, and more via MCP for real-time answers.