Self-host Langfuse with Levelrail
Trace, evaluate, and debug LLM applications with prompt management and cost analytics.
- Authorlangfuse
- LicenceMIT
- Memory4 GiB
- Archarm64
- Services6
How to self-host Langfuse
-
Pull the images
6 images are pulled on your server.
Show images
clickhouse/clickhouse-server:24.12-alpinepostgres:16-alpinelangfuse/langfuse:3.225.11langfuse/langfuse-worker:3.225.11ghcr.io/coollabsio/minio:RELEASE.2025-10-15T17-29-55Zredis:7-alpine
-
Create the app
6 services start in a single Compose app, with 4 named volume mounts for your data, on port 3000.
-
Fill in the secrets
14 secrets are generated and stored encrypted, 25 settings are preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Langfuse requirements
- Memory
- About 4 GiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 3000
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- MIT, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 3000 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Langfuse. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Langfuse docs page.
Deploy Langfuse your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Langfuse from the CLI
levelrail-cli templates deploy langfuse --name my-langfuse Deploy Langfuse with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/langfuse/deploy Langfuse configuration
Langfuse services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| clickhouse | clickhouse/clickhouse-server:24.12-alpine | none | langfuse_clickhouse_data -> /var/lib/clickhouse |
| db | postgres:16-alpine | none | langfuse_db_data -> /var/lib/postgresql/data |
| langfuse-web | langfuse/langfuse:3.225.11 | 3000 | none |
| langfuse-worker | langfuse/langfuse-worker:3.225.11 | none | none |
| minio | ghcr.io/coollabsio/minio:RELEASE.2025-10-15T17-29-55Z | none | langfuse_minio_data -> /data |
| redis | redis:7-alpine | none | langfuse_redis_data -> /data |
Langfuse environment variables
| Variable | Service | Value |
|---|---|---|
| CLICKHOUSE_PASSWORD | clickhouse | Generated at deploy |
| CLICKHOUSE_USER | clickhouse | Preset by the template |
| POSTGRES_DB | db | Preset by the template |
| POSTGRES_PASSWORD | db | Generated at deploy |
| POSTGRES_USER | db | Preset by the template |
| CLICKHOUSE_CLUSTER_ENABLED | langfuse-web | Preset by the template |
| CLICKHOUSE_MIGRATION_URL | langfuse-web | Preset by the template |
| CLICKHOUSE_PASSWORD | langfuse-web | Generated at deploy |
Show all 39 variables
- CLICKHOUSE_URLlangfuse-webPreset by the template
- CLICKHOUSE_USERlangfuse-webPreset by the template
- DATABASE_URLlangfuse-webGenerated at deploy
- ENCRYPTION_KEYlangfuse-webGenerated at deploy
- LANGFUSE_S3_EVENT_UPLOAD_ACCESS_KEY_IDlangfuse-webPreset by the template
- LANGFUSE_S3_EVENT_UPLOAD_BUCKETlangfuse-webPreset by the template
- LANGFUSE_S3_EVENT_UPLOAD_ENDPOINTlangfuse-webPreset by the template
- LANGFUSE_S3_EVENT_UPLOAD_FORCE_PATH_STYLElangfuse-webPreset by the template
- LANGFUSE_S3_EVENT_UPLOAD_REGIONlangfuse-webPreset by the template
- LANGFUSE_S3_EVENT_UPLOAD_SECRET_ACCESS_KEYlangfuse-webGenerated at deploy
- NEXTAUTH_SECRETlangfuse-webGenerated at deploy
- NEXTAUTH_URLlangfuse-webPreset by the template
- REDIS_HOSTlangfuse-webPreset by the template
- SALTlangfuse-webGenerated at deploy
- CLICKHOUSE_CLUSTER_ENABLEDlangfuse-workerPreset by the template
- CLICKHOUSE_MIGRATION_URLlangfuse-workerPreset by the template
- CLICKHOUSE_PASSWORDlangfuse-workerGenerated at deploy
- CLICKHOUSE_URLlangfuse-workerPreset by the template
- CLICKHOUSE_USERlangfuse-workerPreset by the template
- DATABASE_URLlangfuse-workerGenerated at deploy
- ENCRYPTION_KEYlangfuse-workerGenerated at deploy
- LANGFUSE_S3_EVENT_UPLOAD_ACCESS_KEY_IDlangfuse-workerPreset by the template
- LANGFUSE_S3_EVENT_UPLOAD_BUCKETlangfuse-workerPreset by the template
- LANGFUSE_S3_EVENT_UPLOAD_ENDPOINTlangfuse-workerPreset by the template
- LANGFUSE_S3_EVENT_UPLOAD_FORCE_PATH_STYLElangfuse-workerPreset by the template
- LANGFUSE_S3_EVENT_UPLOAD_REGIONlangfuse-workerPreset by the template
- LANGFUSE_S3_EVENT_UPLOAD_SECRET_ACCESS_KEYlangfuse-workerGenerated at deploy
- REDIS_HOSTlangfuse-workerPreset by the template
- SALTlangfuse-workerGenerated at deploy
- MINIO_ROOT_PASSWORDminioGenerated at deploy
- MINIO_ROOT_USERminioPreset by the template
Ports and volumes
- Ports
- 3000
- Volumes
- 4 named mounts: langfuse_clickhouse_data -> /var/lib/clickhouse, langfuse_db_data -> /var/lib/postgresql/data, langfuse_minio_data -> /data, langfuse_redis_data -> /data
Langfuse FAQ
How much memory does Langfuse need?
The catalog lists about 4 GiB of memory for Langfuse across its 6 services.
Does Langfuse run on arm64?
For Langfuse, an arm64 image is published; amd64 is image published.
What licence is Langfuse under?
Langfuse is licensed under MIT, which is permissive, with few conditions on reuse.
Does Langfuse need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does Langfuse bundle?
The template includes Postgres, Redis and ClickHouse, running as its own service.
Which ports does Langfuse use?
Langfuse listens on port 3000 inside the stack.
Where does Langfuse keep its data?
In named volumes: langfuse_clickhouse_data mounted at /var/lib/clickhouse, langfuse_db_data mounted at /var/lib/postgresql/data, langfuse_minio_data mounted at /data and langfuse_redis_data mounted at /data.
Can I deploy Langfuse on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id langfuse for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image clickhouse/clickhouse-server:24.12-alpine, postgres:16-alpine, langfuse/langfuse:3.225.11, langfuse/langfuse-worker:3.225.11, ghcr.io/coollabsio/minio:RELEASE.2025-10-15T17-29-55Z, redis:7-alpine is what you deploy there.