---
title: "Production checklist for self-hosted Langfuse"
description: "A go-live checklist for self-hosted Langfuse: infrastructure, sizing, TLS and encryption, sign-in and SSO, backups, monitoring, telemetry, data retention, and upgrades."
tags: [guide]
---

# Production checklist for self-hosted Langfuse

A Docker Compose trial of Langfuse runs in minutes. A production deployment needs a few more decisions: which managed services to use, how people sign in, how data is encrypted and backed up, and how you will notice problems. This checklist collects them in one place, with links to the configuration reference for each item.

**Start with Langfuse** [Sign up](/cloud)

**TL;DR:** Deploy with the Helm chart or a cloud Terraform module, not Docker Compose. Use managed Postgres, Redis, and S3, and ClickHouse Cloud, BYOC, or the ClickHouse Kubernetes Operator. Serve Langfuse over HTTPS, set `ENCRYPTION_KEY`, disable open sign-up, and configure SSO. Back up Postgres and ClickHouse, monitor health endpoints, set a retention policy, and plan a regular upgrade cadence.

**Deployment architecture — your infrastructure (VPC / on-premises)**

UI, API, and SDK clients send requests to [Langfuse Web](/self-hosting/deployment/infrastructure/containers) (`langfuse/langfuse`), which serves the UI and APIs. [Langfuse Worker](/self-hosting/deployment/infrastructure/containers) (`langfuse/worker`) processes events asynchronously.

| Storage service | Purpose | Connections |
| --- | --- | --- |
| [PostgreSQL](/self-hosting/deployment/infrastructure/postgres) | Transactional data | Web → PostgreSQL; Worker → PostgreSQL |
| [Redis / Valkey](/self-hosting/deployment/infrastructure/cache) | Cache and job queue | Web → Redis / Valkey; Redis / Valkey → Worker |
| [ClickHouse](/self-hosting/deployment/infrastructure/clickhouse) | Observability data | Web → ClickHouse; Worker → ClickHouse |
| [S3 / Blob storage](/self-hosting/deployment/infrastructure/blobstorage) | Raw events and multi-modal attachments | Web → S3 / Blob storage; Worker → S3 / Blob storage |

Both containers can optionally connect to [LLM providers](/self-hosting/deployment/infrastructure/llm-api): Web for the playground, Worker for evaluations. Bring your own LLM API; it can also run in the same VPC or a peered VPC.

The optional [Langfuse AI Gateway](/self-hosting/configuration/ai-gateway) (`langfuse/ai-gateway`, beta) receives model requests from apps and coding agents. Gateway → Web resolves gateway API keys and uploads traces; Gateway → LLM providers relays the requests.

## Infrastructure [#infrastructure]

- [ ] **Deployment method:** [Kubernetes with Helm](/self-hosting/deployment/kubernetes-helm), or the [AWS](/self-hosting/deployment/aws), [Azure](/self-hosting/deployment/azure), or [GCP](/self-hosting/deployment/gcp) Terraform modules. [Docker Compose](/self-hosting/deployment/docker-compose) has no high availability, scaling, or backups.
- [ ] **Postgres:** a managed service with automated backups. See [Postgres](/self-hosting/deployment/infrastructure/postgres).
- [ ] **ClickHouse:** ClickHouse Cloud, BYOC, or the ClickHouse Kubernetes Operator, on a supported version. See [ClickHouse for self-hosted Langfuse](/resources/engineering/clickhouse-for-self-hosted-langfuse).
- [ ] **Redis or Valkey:** Redis 7 or later, with `maxmemory-policy=noeviction` so queue jobs aren't evicted. See [cache](/self-hosting/deployment/infrastructure/cache).
- [ ] **Blob storage:** S3, GCS, Azure Blob Storage, or a compatible service. See [blob storage](/self-hosting/deployment/infrastructure/blobstorage).
- [ ] **UTC everywhere:** Postgres and ClickHouse must run in UTC.

## Sizing [#sizing]

- [ ] **At least the minimums:** web and worker 2 CPU and 4 GiB each, Postgres 2 CPU and 4 GiB, Redis 1 CPU and 1.5 GiB, ClickHouse 2 CPU and 8 GiB. See [scaling](/self-hosting/configuration/scaling#minimum-infrastructure-requirements).
- [ ] **More than one replica** of web and worker, so one restart doesn't stop ingestion or the UI.
- [ ] **A load estimate** from a typical day of traces, counted in observations, not requests.

## Security [#security]

- [ ] **HTTPS** terminated at the load balancer or Ingress. See [encryption](/self-hosting/configuration/encryption#https).
- [ ] **`ENCRYPTION_KEY`** set and stored in your secrets manager. It encrypts stored LLM connections and gateway provider connections, and changing it makes them unreadable.
- [ ] **Encryption at rest** on the databases and blob storage. See [encryption at rest](/self-hosting/configuration/encryption#encryption-at-rest).
- [ ] **Sign-in:** disable open sign-up, configure SSO, and enforce SSO for your email domains. See [hardening](/self-hosting/configuration/hardening#access) and [authentication and SSO](/self-hosting/security/authentication-and-sso).
- [ ] **Network exposure:** keep databases private, and expose only the web container and, if you use it, the AI Gateway. See [networking](/self-hosting/security/networking).
- [ ] **Outbound URL allowlists** for webhooks and LLM connections, to limit server-side requests. See [outbound URL allowlists](/self-hosting/configuration/hardening#outbound-url-allowlists).
- [ ] **PII:** mask data in the SDKs before it is sent, or with server-side masking on Enterprise. See [data masking](/self-hosting/security/data-masking).

## Reliability [#reliability]

- [ ] **Backups** for Postgres and ClickHouse, and a tested restore. See [backups](/self-hosting/configuration/backups).
- [ ] **Health checks** on the readiness and liveness endpoints. See [health and readiness endpoints](/self-hosting/configuration/health-readiness-endpoints).
- [ ] **Monitoring** of the Langfuse containers with OpenTelemetry. See [observability](/self-hosting/configuration/observability).
- [ ] **Disk alerts** on ClickHouse and blob storage, and ClickHouse system log tables capped. See [ClickHouse system log tables](/self-hosting/configuration/scaling#clickhouse-system-log-tables).
- [ ] **Data retention** per project, so storage doesn't grow forever. See [data retention](/docs/administration/data-retention) (Enterprise on self-hosted).

## Operations [#operations]

- [ ] **Upgrade cadence:** follow [the upgrade guide](/self-hosting/upgrade), and read the release notes before major versions. Subscribe to the [OSS newsletter](/self-hosting/oss-newsletter) for breaking changes.
- [ ] **Telemetry decision:** OSS sends usage telemetry unless `TELEMETRY_ENABLED=false`. Enterprise sends license telemetry, Government sends none. See [telemetry](/self-hosting/security/telemetry).
- [ ] **Headless setup:** create the first organization, project, and API keys from environment variables for repeatable deployments. See [headless initialization](/self-hosting/administration/headless-initialization).
- [ ] **One deployment or several:** decide whether teams share one instance or get their own. See [deployment strategies](/self-hosting/security/deployment-strategies).
- [ ] **Optional features:** LLM connections for the Playground and evaluations, [Halo](/self-hosting/configuration/halo), and the [AI Gateway](/self-hosting/configuration/ai-gateway).

  Langfuse does not require internet access. Without it, the update check
  fails gracefully. Features that call a model, such as LLM-as-a-Judge and the
  Playground, need a reachable LLM API. See [air-gapped LLM
  observability](/resources/engineering/air-gapped-llm-observability).

## FAQ

### What is the smallest production-ready setup? [#minimum-production]

Two replicas each of the web and worker containers on Kubernetes, managed Postgres, managed Redis, S3, and a small ClickHouse Cloud service or an operator-managed ClickHouse with at least 2 CPUs and 8 GiB of memory.

### Do I need an Enterprise license for production? [#enterprise-needed]

No. Open source Langfuse runs in production without limits, including enterprise SSO and organization-level roles. An Enterprise license adds features such as audit logs, data retention, project-level roles, server-side masking, and support. See the [license key page](/self-hosting/license-key).

[Ask another question](/docs/ask-ai)

**Start with Langfuse** [Sign up](/cloud)

<!-- agent-instructions -->

---

## Agent Instructions

This page is part of the [Langfuse](https://langfuse.com) documentation, published as plain Markdown for AI agents. Every page is available as Markdown by appending `.md` to its URL, or by sending an `Accept: text/markdown` header. This page: `https://langfuse.com/resources/engineering/self-hosted-langfuse-production-checklist.md`.

### Querying these docs

If the answer is not on this page, query the documentation instead of guessing:

- **Semantic search** across all Langfuse docs, returning an answer with the relevant pages and excerpts. Ask a specific, self-contained question:

  ```bash
  curl -sG "https://langfuse.com/api/search-docs" --data-urlencode "query=How do I trace a LangGraph agent?"
  ```

- **Index of every page**: <https://langfuse.com/llms.txt>, with per-section indexes [llms-docs.txt](https://langfuse.com/llms-docs.txt), [llms-integrations.txt](https://langfuse.com/llms-integrations.txt), and [llms-self-hosting.txt](https://langfuse.com/llms-self-hosting.txt).

### Before writing Langfuse code

- **Install the [Langfuse Agent Skill](https://langfuse.com/docs/api-and-data-platform/features/agent-skill).** It encodes Langfuse's own best practices for instrumentation, prompt management, and evaluation, and materially improves results.
- **Read [What does a good trace look like?](https://langfuse.com/docs/observability/best-practices.md)** before instrumenting an application.
- **Verify endpoints, parameters, and response fields** against the [API reference](https://api.reference.langfuse.com) instead of inferring them from code examples.
- **Use the [Langfuse CLI](https://langfuse.com/docs/api-and-data-platform/features/cli)** (`npx @langfuse/cli api <resource> <action>`) to read or write traces, prompts, datasets, and scores from the terminal.

Found an error in these docs? Please open an issue at <https://github.com/langfuse/langfuse-docs/issues>.
