# Which secrets management platforms rotate credentials automatically without breaking running services?

<p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">Automatic rotation is easy to enable and easy to regret. The service that only reads its credential at startup is the one that falls over at 3am.</p><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">Hi G2 reviewers, which<a class="a a--md" elv="true" href="https://www.g2.com/categories/secrets-management-tools"> </a><a class="a a--md" elv="true" href="https://www.g2.com/categories/secrets-management-tools">secrets management tools</a> rotate cleanly in practice? What decides it:</p><ul>
<li>Whether the platform issues short-lived credentials rather than rotating long-lived ones</li>
<li>Whether applications re-read the secret at runtime or only at startup</li>
<li>Whether old and new credentials overlap during the changeover</li>
<li>What happens to anything still reading from a config file</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/akeyless-identity-security-platform/reviews"><strong>Akeyless</strong></a> issues dynamic credentials rather than rotating static ones, alongside certificate lifecycle management and privileged access in one platform. Reviewers describe it as reliable in daily use once deployed, and ask for more consistent testing and communication around new releases.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/doppler-secrets-management-platform/reviews"><strong>Doppler</strong></a> keeps secrets synchronised across environments and integrates with Kubernetes, Terraform and CI/CD, which is what makes a rotation propagate rather than strand a service.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/azure-key-vault/reviews"><strong>Azure Key Vault</strong></a> is the default for teams already inside Azure, with rotation tied to platform identity.</li>
</ul><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">What broke the last time you rotated something, and did you find out from monitoring or from a user?</p><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true"></p><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true"></p>

##### Post Metadata
- Posted at: 5 days ago
- Author title: Tech Consultant
- Net upvotes: 1


## Comments
### Comment 1

The overlap between old and new credentials seems like the detail I’d test before enabling automatic rotation broadly. I’d rotate one credential while long-running jobs, cached connections, and older service instances are still active and watch what actually breaks. Dynamic credentials avoid part of that problem, but only if every application consuming them is designed to refresh rather than quietly holding the original secret.

##### Comment Metadata
- Posted at: 4 days ago
- Author title: Writer





## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: over 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: over 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: over 13 years ago
  - Comments: 4