Dash0 Raises $110M Series B at $1B Valuation

Last updated: July 19, 2026

Configuration

Configure the Dash0 Terraform Provider — the provider-block schema, supported environment variables, credential resolution order, and OAuth-enabled Dash0 CLI profiles.

The Dash0 Terraform Provider is configured through the standard provider block plus a set of environment variables. Credentials can also be sourced from a Dash0 CLI profile.

Provider block schema

AttributeTypeRequiredDescription
urlstringConditionalBase URL of the Dash0 API (for example, https://api.us-west-2.aws.dash0.com). Required unless DASH0_API_URL is set or a CLI profile supplies it.
auth_tokenstring (sensitive)ConditionalDash0 auth token. Must start with auth_ (static token) or dash0_at_ (OAuth access token). Required unless DASH0_AUTH_TOKEN is set or a CLI profile supplies it.
profilestringOptionalName of a Dash0 CLI profile whose credentials should be used. Only consulted when neither environment variables nor the url/auth_token attributes are set.
max_retriesnumberOptionalMaximum number of retries for failed API requests. Range: 05. Default: 3.

Environment variables

Environment variables take precedence over the equivalent provider block attributes.

VariableRequiredDescriptionDefault
DASH0_API_URLYes¹Base URL of the Dash0 API (for example, https://api.us-west-2.aws.dash0.com). Overrides the url provider attribute.
DASH0_URLNoDeprecated alias for DASH0_API_URL. Used only when DASH0_API_URL is not set.
DASH0_AUTH_TOKENYes¹The API auth token for Dash0. Must start with auth_ or dash0_at_. Overrides the auth_token provider attribute.
DASH0_CONFIG_DIRNoDirectory containing the Dash0 CLI configuration files (activeProfile, profiles.json). Used when loading credentials from a CLI profile.~/.dash0
DASH0_MAX_RETRIESNoMaximum number of retries for failed API requests (0–5). Overrides the max_retries provider attribute.3

¹ Required unless credentials are supplied through the provider block or a Dash0 CLI profile.

Credential resolution order

The provider resolves credentials in this order and stops at the first source that supplies them:

  1. The DASH0_API_URL and DASH0_AUTH_TOKEN environment variables. DASH0_URL is accepted as a deprecated fallback when DASH0_API_URL is not set.
  2. The url and auth_token attributes on the provider block.
  3. A named Dash0 CLI profile — the one named by the profile attribute, or the active profile in ~/.dash0/ when profile is unset.

The Dash0 credentials can be found under Dash0's settings screens.

sh
1234
export DASH0_API_URL="https://api.xxx.dash0.com"
export DASH0_AUTH_TOKEN="auth_xxxx"
export DASH0_MAX_RETRIES=3 # optional; default 3, max 5

With those set, the provider block only needs the version pin:

terraform
12345678910
terraform {
required_providers {
dash0 = {
source = "dash0hq/dash0"
version = "~> 1.6"
}
}
}
provider "dash0" {}

Option 2: Provider-block attributes

terraform
12345678910111213
terraform {
required_providers {
dash0 = {
source = "dash0hq/dash0"
version = "~> 1.6"
}
}
}
provider "dash0" {
url = "https://api.xxx.dash0.com"
auth_token = "auth_xxxx"
}

Environment variables take precedence over provider-block attributes when both are set.

Option 3: Dash0 CLI profile

When the Dash0 CLI is installed and configured, the provider can load credentials from one of its profiles. Set the profile attribute to pick a named profile, or omit it to fall back to the active profile.

terraform
123
provider "dash0" {
profile = "production"
}

The CLI configuration directory defaults to ~/.dash0; set DASH0_CONFIG_DIR to point at a different location (useful for CI runners or sandboxed environments).

OAuth-enabled profiles

Profiles authenticated via dash0 auth login (OAuth) are fully supported. The provider transparently refreshes the access token when it is close to expiry. If the refresh token itself has expired or been revoked, the provider emits an error asking you to re-authenticate:

1234
Error: OAuth re-authentication required
The OAuth session for your dash0 CLI profile has expired.
Run `dash0 auth login` to re-authenticate, then re-run your Terraform command.

[!NOTE] OAuth support was added in version v1.14.0. Earlier versions reject OAuth-enabled profiles with an Invalid Dash0 Auth Token error because they require auth tokens to start with the auth_ prefix — OAuth access tokens use dash0_at_ instead, so upgrade the provider if you see this error.