LangSmithOnboarding

Self-Hosted Onboarding Overview

Understand what a LangSmith Self-Hosted deployment involves and how to work with your Solution Architect through the installation.

Relevant Tools
Admin Readiness Review→RBAC & SCIM Guide→ABAC Policy Builder→Cluster Sizing Calculator→Platform Architecture Assessment→
Onboarding Partner Your assigned Solution Architect will guide you through the full deployment. Use this page to understand what the deployment involves and to prepare your team.

What is LangSmith Self-Hosted?

LangSmith Self-Hosted runs entirely within your own infrastructure. You manage the full stack — Kubernetes cluster, databases, storage, networking, and the LangSmith application itself. This gives you complete data control and the ability to run LangSmith in environments that cannot send data to external services.

This is the most complex deployment model. Every self-hosted customer has a dedicated Solution Architect who guides them through the full installation and configuration.

What a Production Deployment Involves

Before your SA engagement begins, it helps to understand what goes into a production self-hosted deployment:

Infrastructure

LangSmith runs on Kubernetes. Supported distributions include EKS (AWS), AKS (Azure), GKE (GCP), OpenShift 4.14+, and other CNCF-conformant clusters.

A production deployment requires externally-managed services for each of these components — do not use the in-cluster defaults for production:

ComponentOptionsNotes
PostgreSQLRDS, Cloud SQL, Azure DatabaseStores metadata, RBAC, configuration
RedisElastiCache, Memorystore, Azure CacheRequired version ≥ 5.0
ClickHouseLangChain Managed · ClickHouse Cloud · Self-managed (Altinity operator)In-cluster is dev/POC only — see options below
Blob StorageS3, GCS, Azure BlobStrongly recommended — storing payloads in ClickHouse degrades cluster performance
ClickHouse production options
  • LangChain Managed ClickHouse — LangChain-operated ClickHouse service, zero ops overhead for your team. Simplest path if data residency allows it.
  • ClickHouse Cloud — ClickHouse Inc.'s managed cloud service. Good option if you need a cloud-hosted ClickHouse that you control directly.
  • Self-managed replicated cluster — Run your own ClickHouse outside the LangSmith namespace. The Altinity Kubernetes Operator is the standard way to deploy and manage a replicated ClickHouse cluster on Kubernetes. Your SA can help size and configure this appropriately for your environment.

Application

LangSmith is deployed via Helm chart. Your SA will help you configure your values file, connect to external services, and set up post-deployment requirements including:

  • Ingress and custom domain
  • TLS certificate management
  • SSO (OAuth 2.0 / OIDC) with your Identity Provider
  • Environment separation and upgrade procedures

PS Portal Deployment Guides

Your SA will reference the provider-specific deployment guides during your engagement. These contain the full Terraform modules, Helm values, and deployment steps for each cloud provider:

Azure AKS

Full Guide

AKS with Azure CNI, Workload Identity, NGINX ingress, cert-manager TLS, private PostgreSQL, Redis, and Blob Storage.

View deployment guide →

GCP GKE

Full Guide

GKE Standard/Autopilot with Workload Identity, Envoy Gateway ingress, Cloud SQL, Memorystore Redis, and GCS.

View deployment guide →

AWS EKS

Full Guide

EKS with IRSA, ALB Ingress Controller, RDS PostgreSQL, ElastiCache Redis, and S3 via VPC endpoint.

View deployment guide →

OpenShift OCP

Coming Soon

OpenShift on-prem or ROSA with Routes, cert-manager, PostgreSQL Operator, Redis Operator, and ODF.

These guides are used by your SA to deploy and configure LangSmith in your environment.

What to Prepare Before Your Engagement

Help your SA hit the ground running by having the following ready:

  • Cloud provider and Kubernetes distribution confirmed
  • Kubernetes cluster provisioned or access confirmed (existing infra path) or cloud account access ready (greenfield path)
  • LangSmith License Key received from your Account Executive
  • Container registry accessible from your cluster
  • Identity Provider details for SSO configuration (Okta, Azure Entra ID, etc.)
  • Networking requirements understood (egress requirements, private vs. public endpoints)
  • Team contacts identified — who owns infrastructure, who owns the application, who owns security/IAM

Next: Configure Your Organization

Once your SA has completed the deployment, use the Admin Readiness Review to work through all org configuration — SSO, SCIM, workspace design, roles, ABAC policy, API keys, data retention, Fleet setup, and more. Your SA will guide you through each topic.