Manage Logfire with Infrastructure as Code

Logfire supports Infrastructure as Code (IaC) via provider projects for different tools.

Terraform and OpenTofu

• Terraform docs: registry.terraform.io/providers/pydantic/logfire
• OpenTofu docs: search.opentofu.org/provider/pydantic/logfire
• Provider source: github.com/pydantic/terraform-provider-logfire

Pulumi

• Published in the Pulumi Registry: pulumi.com/registry/packages/logfire
• Pulumi provider source: github.com/pydantic/pulumi-logfire

What You Can Manage

Resources include:

• logfire_project
• logfire_channel (webhook and Opsgenie)
• logfire_alert
• logfire_dashboard
• logfire_write_token
• logfire_read_token
• logfire_organization (self-hosted only)

Requirements

• Terraform CLI 1.8+ (per provider docs)
• A Logfire API key, passed as api_key or LOGFIRE_API_KEY
• A Logfire base URL, passed as base_url or LOGFIRE_BASE_URL

See API keys for key creation and scopes.

Quick Start

terraform {
  required_providers {
    logfire = {
      source  = "pydantic/logfire"
    }
  }
}

provider "logfire" {
  # You can also set LOGFIRE_BASE_URL and LOGFIRE_API_KEY.
  base_url = "https://logfire-us.pydantic.dev"
  api_key  = var.logfire_api_key
}

resource "logfire_project" "production" {
  name        = "production"
  description = "Managed by IaC"
}

Apply with your tool of choice:

• Terraform: terraform init && terraform apply
• OpenTofu: tofu init && tofu apply

Self-Hosted Note

Set base_url to your self-hosted Logfire endpoint when running outside Logfire Cloud. The logfire_organization resource is self-hosted only and requires an API key with organization-level scope.