Self-Hosting Overview

Deploy LangWatch on your own infrastructure for full data control

LangWatch is an open-source LLM Ops platform for evaluation, observability, and optimization of AI agents and pipelines. You can self-host LangWatch for full data sovereignty, regulatory compliance (GDPR, SOC 2), or air-gapped environments. The self-hosted edition runs the same software that powers LangWatch Cloud. There is no separate “community” or “enterprise” build.

Without a license, self-hosted LangWatch is uncapped: unlimited members, teams, projects, and everything you create on your own infrastructure. An Enterprise license adds SSO, RBAC, SCIM, audit logs and support in the same deployment. See Editions and licensing.

Get the entire LangWatch platform running with a single Helm install:

helm repo add langwatch https://langwatch.github.io/langwatch
helm repo update
helm pull langwatch/langwatch --untar
helm install langwatch ./langwatch \
  --namespace langwatch --create-namespace \
  --set autogen.enabled=true \
  -f langwatch/examples/overlays/size-dev.yaml \
  --wait --timeout 10m

That fits a small cluster at roughly 2.8 CPU and 6.9 Gi of requests, and generates its own secrets, so you have no secret to prepare first. Auto-generated secrets change on every reinstall, so swap them for real ones before you rely on the deployment: see Kubernetes (Helm) for full setup instructions.

Reach the UI with kubectl -n langwatch port-forward svc/langwatch-app 5560:5560.

examples/values-local.yaml is a different thing and is not the one to start with: it pins the app, NLP and LangEvals images to a local tag and sets pullPolicy: Never on those and on ClickHouse, which only resolves on a Kind cluster you have loaded those images into with make images-local. On any other cluster the pods sit in ErrImageNeverPull. See Local Kubernetes if that is what you want.

Langy, the AI assistant, is part of this install and runs on the node’s normal container runtime. To harden it with a sandboxed runtime on EKS, see installing gVisor on EKS.

Looking for a managed solution? LangWatch Cloud is fully maintained by the LangWatch team and is the fastest way to get started.

Architecture at a Glance

Every component runs in your environment. The dashed line is the only connection to LangWatch, and each part of it has a switch.

Your agents send traces to the App over OpenTelemetry. The App and the Workers store them in ClickHouse, with PostgreSQL for configuration, Redis for the queue and object storage for older data. Model calls go to the providers you configure, with your keys. The AI Gateway and Langy are optional.

See Architecture & Infrastructure for a detailed breakdown of networking, scaling, and storage tiers, and AI Gateway → Self-hosting for the gateway sub-chart setup if you want to terminate LLM traffic on your own perimeter.

Running Langy, the automated AI engineer? It ships as an agent pod in the same umbrella chart, on by default; set langyagent.chartManaged: false to leave it out. See Self-hosting Langy.

Deployment Models

What LangWatch runs and what you run in each model. Cloud Enterprise is LangWatch Cloud on dedicated, single-tenant instances in the region you choose.

LangWatch Cloud

Fully managed by the LangWatch team. No infrastructure to manage, sign up and start sending traces in minutes.

Sign up at langwatch.ai

Self-Managed

Deploy the complete LangWatch stack on your own infrastructure, AWS, Azure, GCP, or bare metal. You manage everything: compute, databases, and storage. Full data sovereignty.

Get started with Kubernetes

Cloud Enterprise

LangWatch manages the application. Your data lives on exclusive, dedicated instances deployed in your preferred cloud region. The convenience of managed, with the isolation of self-hosted.

Contact sales

Hybrid

LangWatch manages the control plane (App, Workers, NLP, LangEvals). You provide the data plane, ClickHouse and S3 in your VPC. Your trace data never leaves your network.

Learn more

At a Glance

	Cloud	Self-Managed	Cloud Enterprise	Hybrid
You manage infrastructure		Yes
You manage data storage		Yes	Yes	Yes
LangWatch manages app	Yes		Yes	Yes
Data stored in your network		Yes	Yes	Yes
Setup time	Minutes	Hours	Days	Days

Quick Start

Choose the deployment method that fits your environment.

Docker Compose

Quick local setup with Docker Compose.

Kubernetes (Helm)

Production deployment on any Kubernetes cluster.

Local Kubernetes

Test the Helm chart locally with Kind.

What’s New in v3

LangWatch v3 is a major architecture upgrade. If you are migrating from v2, review the deployment guides for updated requirements.

• ClickHouse replaces Elasticsearch as the primary data store, delivering faster analytical queries and lower operational overhead.
• Event-sourcing architecture ensures reliable, ordered processing of traces, evaluations, and experiment runs.
• S3 cold storage tiering moves older data to object storage automatically, reducing ClickHouse disk costs.
• Native ClickHouse backup/restore simplifies disaster recovery without third-party tooling.
• Auto-tuned ClickHouse via the clickhouse-serverless subchart adapts resource allocation to your workload.
• Composable Helm chart overlays let you customize deployments without forking the chart.
• Deep OpenTelemetry integration: ingest traces via OTLP, export platform metrics and logs via OTel for infrastructure monitoring.
• AI Gateway sub-chart, terminate LLM traffic on your own perimeter with virtual keys, hierarchical budgets, multi-provider routing, guardrails, and prompt caching. Same Helm install, on by default; turn it off with gateway.chartManaged=false. See AI Gateway → Self-hosting.

Enterprise

For Cloud Enterprise or Hybrid deployments, contact the LangWatch team to discuss your requirements.

Enterprise capabilities include:

• SSO, SCIM: sign in through your identity provider and provision users from your directory
• Role-based access control: fine-grained permissions across projects and teams
• Audit logs: full visibility into who did what and when
• Priority support: dedicated engineering assistance and SLA-backed response times