> ## Documentation Index
> Fetch the complete documentation index at: https://docs.springwinter.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Deploy Langfuse

> Set up Langfuse and connect its dependencies with Spring Winter.

## Deploy with an agent

Copy agent prompt

Help me deploy Langfuse. Read [https://docs.springwinter.dev/deploy/open-source/langfuse](https://docs.springwinter.dev/deploy/open-source/langfuse.md), [https://langfuse.com/self-hosting/deployment/docker-compose](https://langfuse.com/self-hosting/deployment/docker-compose), and [https://docs.springwinter.dev/api-reference/agents](https://docs.springwinter.dev/api-reference/agents.md). Fetch the public OpenAPI specification from my Spring Winter origin. Use my local SPRINGWINTER\_TOKEN or existing SPRINGWINTER\_API\_TOKEN. Keep credentials out of chat, logs and source.

Confirm my project, AWS connection, Region and budget. Pin a release. Check its required services, container port, health path, network access and durable storage. Data requirements for this deployment: PostgreSQL, ClickHouse, compatible Redis or Valkey, and private S3-compatible object storage.

1. Create PostgreSQL in the Spring Winter project and wait for its writer. Provision ClickHouse, the cache and object storage before starting either Langfuse process. Verify private access and the cache’s supported topology.
2. Set DATABASE\_URL and CLICKHOUSE\_URL. Give the migration process a reachable CLICKHOUSE\_MIGRATION\_URL and the required grants. Configure the cache connection and LANGFUSE\_S3\_EVENT\_UPLOAD\_\* settings using the pinned release’s configuration.
3. Deploy matching Langfuse web and worker images. Set shared secrets consistently and set NEXTAUTH\_URL to the HTTPS web URL. Use a supported Spring Winter worker source, such as a GitHub Dockerfile wrapping the pinned upstream worker image, or run the worker on the chosen external host.
4. Run the release’s PostgreSQL and ClickHouse migration sequence. If the web image runs migrations on startup, wait for its readiness. Start the worker after migrations succeed and send traffic once both processes are healthy.

Show me the planned resources, database and migration order, secret names and estimated cost. Identify components that require separate hosting. Wait for approval before making changes. Use documented Spring Winter operations and wait for each workflow to finish. Submit a sample trace with a project key and confirm it appears in the UI after worker processing. Report resource links and anything you could not verify.

## Before you start

[Connect your AWS account](https://docs.springwinter.dev/connect-aws.md) and choose a project. Review the [upstream deployment instructions](https://langfuse.com/self-hosting/deployment/docker-compose) for the release you plan to pin.

See [Langfuse environment variables](https://langfuse.com/self-hosting/configuration).

## Data dependencies

PostgreSQL, ClickHouse, compatible Redis or Valkey, and private S3-compatible object storage. See [SQL databases](https://docs.springwinter.dev/deploy/databases.md) for private writer access and connection details.

## Deployment order

1. Create PostgreSQL in the Spring Winter project and wait for its writer. Provision ClickHouse, the cache and object storage before starting either Langfuse process. Verify private access and the cache’s supported topology.
2. Set `DATABASE_URL` and `CLICKHOUSE_URL`. Give the migration process a reachable `CLICKHOUSE_MIGRATION_URL` and the required grants. Configure the cache connection and `LANGFUSE_S3_EVENT_UPLOAD_*` settings using the pinned release’s configuration.
3. Deploy matching Langfuse web and worker images. Set shared secrets consistently and set `NEXTAUTH_URL` to the HTTPS web URL. Use a supported Spring Winter worker source, such as a GitHub Dockerfile wrapping the pinned upstream worker image, or run the worker on the chosen external host.
4. Run the release’s PostgreSQL and ClickHouse migration sequence. If the web image runs migrations on startup, wait for its readiness. Start the worker after migrations succeed and send traffic once both processes are healthy.

Use [Runtime variables](https://docs.springwinter.dev/concepts/environment-variables.md) for runtime credentials. For a [Spring Winter web server](https://docs.springwinter.dev/deploy/web-servers.md), set an app-supported health path that returns HTTP 200 without credentials. Check **History** before running the application check.

## Verify the deployment

Submit a sample trace with a project key and confirm it appears in the UI after worker processing.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.