Postgres Database
Follow one of the deployment guides to get started.
Langfuse requires a persistent Postgres database to store its state. You can use a managed service on AWS, Azure, or GCP, or host it yourself.
Langfuse supports Postgres versions >= 12 and uses the public schema in the selected database.
Use Cases
Postgres is used for all transactional data, including:
- Users
- Organizations
- Projects
- Datasets
- Encrypted API keys
- Settings
Configuration
Timezones
Langfuse expects that its infrastructure components default to UTC. Especially Postgres and ClickHouse settings that overwrite the UTC default are not supported and may lead to unexpected behavior. Please vote on this GitHub Discussion if you would like us to consider supporting other timezones.
Blob Storage (S3)
Configure S3 or S3-compatible blob storage for self-hosted Langfuse. Store raw events, multi-modal inputs, and batch exports with AWS S3, MinIO, or compatible services.
LLM API / Gateway
Optionally, you can configure Langfuse to use an external LLM API or gateway for add-on features. Langfuse tracing does not need access to the LLM API as traces are captured client-side.
