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.
Official and Community Support
Langfuse works with PostgreSQL and Postgres-compatible databases. We distinguish between officially supported and community-supported options:
| Option | Support Level |
|---|---|
| PostgreSQL (>= 12, self-hosted or managed) | Official |
| Amazon Aurora PostgreSQL | Official |
| Other Postgres-compatible databases (e.g., Google AlloyDB, YugabyteDB) | Community |
Managed services that run PostgreSQL, such as Amazon RDS, Azure Database for PostgreSQL, and GCP Cloud SQL, are covered by the official support level. Aurora PostgreSQL is the default in our AWS (Terraform) deployment.
- Official: Maintained and tested by the Langfuse team. We prioritize bug reports for these options.
- Community: Expected to work based on community usage. We do not systematically test these options; support is best-effort and fixes often depend on community contributions.
In either case, please report problems via GitHub issues — pull requests that fix or improve support for community-supported options are highly welcome.
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.
Last edited
