Doppler
Secrets management platform for syncing environment variables across environments
Doppler adds keyless syncs and agent-facing secrets as on-prem settles in
◆Recent moves
- 13d ago
Doppler opens project tags and environment-scoped roles to more plans
Project tags reach all workplaces and environment-scoped roles reach every paid plan, so teams can give one member different access per environment. Qovery syncs now cover Helm and Terraform services, and the classic Deno Deploy integration is retired with that platform.
View source ↗ - 1mo ago
Permissive secret naming and workplace-wide token revocation
Permissive secret naming opens to all workplaces and admins can revoke all personal and CLI tokens at once, with project-list actions and quoted secret references alongside. The token revocation is the lifecycle-control item, and the month also has a Doppler On-prem fix.
View source ↗ - 2mo ago
GitHub Copilot Agents sync and OIDC for GCP and Azure syncs
Doppler can now sync secrets to GitHub Copilot Agents, rotate OpenAI service accounts, and reach GCP and Azure through OIDC without a stored credential. Terraform resources for the new sync, rotation type and OIDC shipped in the same month, in line with the product's programmatic rule.
View source ↗ - 3mo ago
Compare page for secrets across configs and projects
A workplace-level Compare page shows a secret's values across configs and projects and can start a Change Request from the selection. It turns a one-config view into an audit tool, in the same month as a Laravel Forge v2 API migration.
View source ↗ - 4mo ago
Doppler On-prem released
⚡ SPARKDoppler On-prem is released, with the rest of the month going to dashboard role filters, downstream-impact warnings before deleting inherited or referenced data, and fuzzy secret search. The self-hosted build is the item that changes who can buy the product at all.
View source ↗ - 5mo ago
Terraform support for access scoping and full secret-history redaction
Integration Access Scoping becomes reachable through the API and Terraform, and every historical version of a secret can be redacted by name or ID so deleted history is fully scrubbed. History redaction is the substantive one — it answers the question an auditor asks after a leak.
View source ↗