Skip to main content
Configure deployment infrastructure in .env, container environment variables or Kubernetes Secrets. Configure business policies and integrations in Settings; configure backend connections on each Fleet and recurring work under Scheduled tasks. Environment-only values are not editable through the settings API; some existing deployment paths remain visible as read-only diagnostics. Set the same infrastructure values on API, worker and gateway replicas, then restart them after changes. Object storage is required for S3-backed operations; shared-filesystem deployments are still supported. Settings stores sparse database overrides and encrypts secrets. Existing saved values take precedence over environment baselines. Prefer Settings for integrations instead of maintaining a second copy in .env. Fields marked as requiring a restart, including OIDC and Hugging Face OAuth, require a process restart after saving. Before upgrading a deployment that saved infrastructure values in Settings, copy its effective S3 configuration and other environment-only overrides into the deployment environment. Old database overrides for those fields are ignored. Keep TUNEPLANE_SECRET_ENC_KEY unchanged when moving integration secrets into Settings.
This page is generated from server.core.config.WebSettings by scripts/gen_settings_docs.py, and CI fails if a setting is added without a description. If a knob exists, it is on this page.

Deployment essentials

Everything else has a working default. These do not.
path
The one path a deployment configures. It must be an absolute path, and it must resolve identically on the console, on every node, and inside every container. Empty means single-machine development.
string
Generated per process when unset, which logs everyone out on restart and breaks multi-replica deployments outright. Set a fixed strong random value for anything but single-machine development.
url
Required PostgreSQL URL for every deployment, including local development. There is no SQLite fallback.
url
The https address users reach this deployment at. The OIDC redirect URI is built from it, so single sign-on cannot work without it.

Reading the tables

  • Required means the deployment refuses to start without it.
  • generated means a value is derived per process when you do not supply one.
  • A dash means the default is empty, and empty usually means the feature is off.
Absolute paths are validated at startup: a relative TUNEPLANE_STORAGE_ROOT is refused rather than resolved against whatever directory the process happened to start in.

Core

Proxied submission

Automatic retry

LLM judge

Agent sandbox

Playground

Model deployments

Slurm executor

KubeRay executor

Object storage

Scheduling windows

Maintenance mode

Runtime watchdog

Diagnosis agent

Secrets and integrations

Webhook channels