Every secret the system uses: what it is, where it’s deployed, and how to rotate it. Never put a value in this file. The master copy of every value, per environment, is the operator’s Bitwarden vault (decisions log, Configuration and secrets management).
Rules
- Add a row when a secret is created; update it when one is rotated or moved.
- Staging and production always have separate values. “Per env” below means one value per environment.
- Order of a rotation: create the new value → update Bitwarden → deploy it to every place in the “Deployed to” column → confirm → revoke the old value.
Where secrets are deployed
- Worker secret:
wrangler secret put <NAME> --env <env>.
- Kubernetes secret:
kubectl, run over WireGuard, in that environment’s namespace.
- GitHub secret: a repository secret, prefixed
STAGING_ or PROD_.
- Bitwarden only: never deployed, kept for recovery.
| Secret |
Per env |
Deployed to |
Used by |
Rotation |
| Deploy API token (Workers, Routes, Pages, Queues, R2, Hyperdrive) |
One, both environments (Cloudflare can’t scope a token per environment) |
GitHub secret |
The pipeline |
New token in Cloudflare, update GitHub, revoke old |
Pages preview token CLOUDFLARE_PAGES_PREVIEW_TOKEN (Pages edit only) |
One |
GitHub secret |
The PR preview job only, which runs the PR’s own code, so it never holds the deploy token (cicd.md section 1). Not created yet: previews are skipped until it exists |
New token in Cloudflare, update GitHub, revoke old |
| Tunnel token |
One per tunnel |
Kubernetes secret |
cloudflared |
Rotate in Zero Trust, update secret, restart pods |
| Rate-limit rules token (this zone’s rate-limiting rules only) |
Yes |
Worker secret |
apps/dashboard-api (admin Edge rate limits screen) |
New token, wrangler secret put, revoke old |
| DNS-01 token (DNS edit, one zone) |
One |
Kubernetes secret |
cert-manager |
New token, update secret, revoke old |
Queues send token (niobi-callbacks only) |
Yes |
Kubernetes secret |
apps/niobi-proxy |
New token, update secret, restart, revoke old |
| Turnstile secret key |
Yes |
Worker secret |
apps/dashboard-api |
Rotate in Cloudflare, wrangler secret put |
| Access service token (admin probe) |
Production |
Datadog Synthetics |
Monitoring probe of admin. |
Rotate in Zero Trust, update Datadog |
| Secret |
Per env |
Deployed to |
Used by |
Rotation |
BETTER_AUTH_SECRET_APP |
Yes |
Worker secret |
apps/dashboard-api |
Rotating signs every customer out (auth-security.md 3.2) |
BETTER_AUTH_SECRET_ADMIN |
Yes |
Worker secret |
apps/dashboard-api |
Rotating signs every staff member out |
| OAuth client secrets (Google, GitHub, GitLab) |
Yes |
Worker secret |
apps/dashboard-api |
Regenerate at the provider, wrangler secret put |
| Secret |
Per env |
Deployed to |
Used by |
Rotation |
| Virtual-key encryption key (versioned) |
Yes |
Worker secret |
apps/dashboard-api (encrypts), apps/api (decrypts) |
Add a new version, deploy both Workers, re-encrypt rows in the background, then remove the old version |
| Bifrost admin credential |
Yes |
Worker secret |
apps/dashboard-api (management routes only) |
Change in Bifrost, wrangler secret put |
Bifrost encryption key (bifrost-encryption-key) |
Yes |
Kubernetes secret; copy in Bitwarden |
Bifrost (encrypts stored provider keys) |
Bifrost maintenance window |
| Bifrost Postgres password |
Yes |
Kubernetes secret; copy in Bitwarden |
Bifrost |
Change in Postgres, update secret, restart |
| Provider API keys (OpenAI, Anthropic, Google, Fireworks) |
Yes |
Bifrost (through its dashboard, over WireGuard); copy in Bitwarden |
Bifrost |
Rotate at the provider, update in Bifrost |
| Secret |
Per env |
Deployed to |
Used by |
Rotation |
Niobi credentials (client_id, sender, secret key) |
Yes: sandbox credentials for staging, production credentials for production (revised 2026-11-02) |
Kubernetes secret; copy in Bitwarden |
apps/niobi-proxy only |
Regenerate in the Niobi portal (Workspace → Integrations), update the secret, restart |
| Maansa API credentials (FX source, Q3.7) |
To confirm in the Maansa scope |
Worker secret on apps/dashboard-api (the FX job), unless Maansa needs a whitelisted IP, then the droplet like Niobi |
The daily FX job |
Per Maansa’s process |
niobi-proxy HMAC secret |
Yes |
Worker secret and Kubernetes secret |
apps/dashboard-api signs, apps/niobi-proxy verifies |
Rotate both together |
| Secret |
Per env |
Deployed to |
Used by |
Rotation |
api role credentials |
Yes |
Hyperdrive config (the cluster Postgres over a VPC Service) |
apps/api |
New password, update Hyperdrive |
dashboard role credentials |
Yes |
Hyperdrive config |
apps/dashboard-api |
Same |
consumer role credentials |
Yes |
Hyperdrive config (logs) |
Queue consumer |
Same |
migrator role credentials |
Yes |
Kubernetes secret the self-hosted runner reads |
The pipeline only |
New password, update the secret |
| Postgres superuser password |
Yes |
Kubernetes secret; copy in Bitwarden |
Bootstrapping roles on the cluster database |
Change in Postgres, update secret |
| R2 backup credentials (S3 access key and secret) |
Production |
Kubernetes secret; copy in Bitwarden |
Production Postgres backups, write access to the backup bucket only |
New token in Cloudflare, update secret |
| Secret |
Per env |
Deployed to |
Used by |
Rotation |
| Resend API key |
Yes |
Worker secret |
apps/dashboard-api |
Rotate at Resend |
| Datadog API key |
One |
Worker secret; Kubernetes secret |
Workers telemetry; droplet agent |
Rotate in Datadog, update both |
| GHCR read token (image pulls) |
One |
Kubernetes imagePullSecret; copy in Bitwarden |
K3s |
New classic token with only read:packages (GitHub Packages does not accept fine-grained tokens), update secret, revoke old |
| Self-hosted runner registration |
One |
Registration token: Kubernetes secret runner-registration in ci-runner, used once and deleted. The registration it creates is kept on the runner’s volume (ci-runner-state) |
GitHub Actions runner (infra/ci-runner) |
Remove the runner in GitHub, clear the volume, new token, reinstall (infra/README.md, P0.09) |
Migrator connection strings (MIGRATOR_DATABASE_URL_STAGING, _PRODUCTION) |
Yes |
Kubernetes secret runner-migrator in ci-runner, built from each database’s app-db-cluster-app secret |
The pipeline’s migrate job, on the self-hosted runner |
Rotate the migrator password in the database operator, rebuild the secret, restart the runner |
Image pushes to GHCR use GitHub’s built-in GITHUB_TOKEN; nothing to store.
| Secret |
Notes |
| Account MFA recovery codes |
DigitalOcean, Cloudflare, GitHub, Datadog, Resend, Niobi portal |
| WireGuard keys |
Operator laptop peer and the droplet’s peer |
| SSH key |
For use over WireGuard only, after the lockdown |
| Bifrost dashboard password |
Reached over WireGuard only, after the lockdown |