LangWatch 3.0 — Self-Host with ClickHouse

Overview

LangWatch 3.0 is the release where we deleted more infrastructure than we added, and the product got better for it. For cloud users, this is the engine behind the speed and stability improvements you've already been experiencing. But the bigger story here is self-hosting — we've made it dramatically easier to run LangWatch on your own infrastructure.

If your organisation needs on-prem, has data residency requirements, or just wants full control over where your LLM traces live, 3.0 is built for you.

What You Can Do Now

Self-host in minutes

• A production-ready Helm chart for Kubernetes that auto-tunes ClickHouse memory, merge settings, and thread pools for your available resources. No ClickHouse expertise required.

• make dev to start locally with Docker Compose, make down to stop. That’s a pretty damn snazzy local workflow.

• Docker images support readOnlyRootFilesystem for security-hardened Kubernetes clusters.

Simpler to operate

• The platform runs on ClickHouse + PostgreSQL. Elasticsearch has been relegated to the depths of hell.

• Fewer moving parts means fewer things to monitor and fewer things that wake you up at night.

Documentation

• Self-hosting guide rewritten from scratch — Kubernetes, Helm, local Docker, resource requirements all documented upfront so you're not guessing.

• Migration guide for existing 1.x and 2.x deployments covering the move away from Elasticsearch.

Rollout

LangWatch 3.0.0 is on Docker Hub and our Helm chart repository now. Cloud users are already running it.

Notes

• The clickhouse-serverless Helm chart is versioned independently (0.2.0) and works standalone if you need a well-tuned ClickHouse for other purposes.

• If you're evaluating LangWatch for on-prem, reach out — we're happy to walk you through the deployment.