Skip to main content
Unkey services read configuration from a TOML file passed at startup. Environment variables can be referenced with ${VAR} and are expanded before parsing. Defaults and validation run after parsing. The config schema maps to svc/ctrl/api/config.go. The control plane API is configured via a TOML file: control-api --config=unkey.toml.
string
Instance identifier for logs and tracing.
string
required
Region label for routing and observability.
int
default:"8080"
HTTP server port.
int
Prometheus metrics port. Set to 0 to disable.
string
required
Bearer token for control API clients.
Known consumers:
  • API service
  • Krane service
Rotation is manual today. There is no built-in rotation mechanism. TODO: Replace with JWT-based auth once auth.unkey.cloud is in place.
string
Base domain for wildcard certificates.
string
Base domain for regional routing.
string
Base domain for custom CNAME targets.
string
required
MySQL DSN. The control plane API uses one read-write connection for all queries.
object
Restate integration.
object
GitHub webhook configuration.
object
Tracing configuration. Logging settings are parsed but not applied by the control API runtime.

Example configuration

Control API: