Self-hosted LangSmith

Important
Self-hosted LangSmith is an add-on to the Enterprise plan designed for our largest, most security-conscious customers. For more details, refer to Pricing. Contact our sales team if you want to get a license key to trial LangSmith in your environment.

Host an instance of LangSmith in your own infrastructure for observability, evaluation, and prompt engineering. You can optionally enable LangSmith Deployment to deploy and manage agents through the LangSmith UI.

For step-by-step setup instructions for self-hosted LangSmith on AWS, GCP, or Azure, refer to our cloud architecture guides: AWS, GCP, or Azure.

Before installing or upgrading, review the minimum versions for self-hosting dependencies.

What’s included

A self-hosted LangSmith instance includes:

Services:

• LangSmith frontend UI
• LangSmith backend API
• LangSmith Platform backend
• LangSmith Playground
• LangSmith queue
• LangSmith ACE (Arbitrary Code Execution) backend

Storage services:

• ClickHouse (traces and feedback data)
• PostgreSQL (operational data)
• Redis (queuing and caching)
• Blob storage (optional, but recommended for production)

To access the LangSmith UI and send API requests, you will need to expose the LangSmith frontend service. Depending on your installation method, this can be a load balancer or a port exposed on the host machine.

Services

Service	Description
LangSmith frontend	The frontend uses Nginx to serve the LangSmith UI and route API requests to the other servers. This serves as the entrypoint for the application and is the only component that must be exposed to users.
LangSmith backend	The backend is the main entrypoint for CRUD API requests and handles the majority of the business logic for the application. This includes handling requests from the frontend and SDK, preparing traces for ingestion, and supporting the hub API.
LangSmith queue	The queue handles incoming traces and feedback to ensure that they are ingested and persisted into the traces and feedback datastore asynchronously, handling checks for data integrity and ensuring successful insert into the datastore, handling retries in situations such as database errors or the temporary inability to connect to the database.
LangSmith platform backend	The platform backend is another critical service that primarily handles authentication, run ingestion, and other high-volume tasks.
LangSmith Playground	The Playground is a service that handles forwarding requests to various LLM APIs to support the Playground feature. This can also be used to connect to your own custom model servers.
LangSmith ACE (Arbitrary Code Execution) backend	The ACE backend is a service that handles executing arbitrary code in a secure environment. This is used to support running custom code within LangSmith.

Storage services

LangSmith will bundle all storage services by default. You can configure it to use external versions of all storage services. In a production setting, we strongly recommend using external storage services.

Service	Description
ClickHouse	ClickHouse is a high-performance, column-oriented SQL database management system (DBMS) for online analytical processing (OLAP). LangSmith uses ClickHouse as the primary data store for traces and feedback (high-volume data). 💡 Connect to external ClickHouse
PostgreSQL	PostgreSQL is a powerful, open source object-relational database system that uses and extends the SQL language combined with many features that safely store and scale the most complicated data workloads. LangSmith uses PostgreSQL as the primary data store for transactional workloads and operational data (almost everything besides traces and feedback). 💡 Connect to external PostgreSQL - AWS RDS, GCP Cloud SQL, Azure Database
Redis / Valkey	Redis is a powerful in-memory key-value database that persists on disk. By holding data in memory, Redis offers high performance for operations like caching. LangSmith uses Redis to back queuing and caching operations. Valkey is also officially supported as a drop-in replacement for Redis. 💡 Connect to external Redis or Valkey - AWS ElastiCache, GCP Memorystore, Azure Cache
Blob storage	LangSmith supports several blob storage providers, including AWS S3, Azure Blob Storage, and Google Cloud Storage. LangSmith uses blob storage to store large files, such as trace artifacts, feedback attachments, and other large data objects. Blob storage is optional, but highly recommended for production deployments. 💡 Enable blob storage - AWS S3, GCP GCS, Azure Blob

To install, follow the Kubernetes setup guide.

Next steps

• Enable LangSmith Deployment: add a control plane and data plane to deploy and manage agents through the LangSmith UI.
• Deploy standalone Agent Servers: deploy Agent Servers directly without enabling LangSmith Deployment.

---

Connect these docs to Claude, VSCode, and more via MCP for real-time answers.

Edit this page on GitHub or file an issue.