Overview
Self-hosted Logfire runs the same product as the public Logfire deployment in your own Kubernetes environment. It is delivered through the official Logfire Helm chart.
Self-hosted Logfire is included in the Enterprise plan. Contact sales@pydantic.dev for access to the private container images and commercial terms.
Use the Logfire Helm chart README for the current chart commands and chart-version-specific values. These website docs focus on planning, architecture, examples, and operational procedures.
- Local quickstart: run a first install with the chart’s
values.dev.yamlfile. - Production requirements: plan the production values you need before installing the chart.
- Architecture: understand the main services, dependencies, and data flow.
- Examples: copy provider-specific authentication snippets into your values file.
- Troubleshooting: debug image pull, database, and runtime issues.
- Bucket migration: migrate telemetry object storage buckets.
- Usage report: generate usage reports for self-hosted deployments.
A production deployment needs:
- A Kubernetes cluster with enough capacity for the selected sizing preset.
- Image pull credentials for Logfire’s private images.
- PostgreSQL 16 or later.
- Three PostgreSQL databases: one for Logfire application data, one for FusionFire metadata, and one for Dex.
- Object storage using Amazon S3, Google Cloud Storage, Azure Storage, or an S3-compatible provider.
- An identity provider supported by Dex.
- Kubernetes storage for scratch and ingest volumes, either through a default
StorageClassor explicit storage class settings in values.
After deploying self-hosted Logfire, point the SDK at your Logfire base URL:
import logfire
logfire.configure(
advanced=logfire.AdvancedOptions(base_url='https://logfire.example.com'),
)
You can also authenticate the CLI against your self-hosted instance:
logfire --base-url="https://logfire.example.com" auth