Prompt
I'm building a SaaS product and need to store secrets safely, what should I use?
Latest observation
Oct 23, 2026
OpenAI APIWeb search: off
For a SaaS product, the safest default is:
Use a dedicated secrets manager, not your database, config files, or environment variables alone.
Good options:
- AWS Secrets Manager / AWS SSM Parameter Store
- HashiCorp Vault
- GCP Secret Manager
- Azure Key Vault
- Managed platforms like 1Password Secrets Automation or Doppler for simpler workflows
What to store there
- API keys
- Database credentials
- OAuth client secrets
- Signing keys
- Webhook secrets
- Private certs / TLS keys
Best practices
- Encrypt at rest and in transit
- Rotate secrets regularly
- Use least-privilege access
- Separate prod/staging/dev secrets
- Never commit secrets to git
- Avoid hardcoding in images or code
- Use short-lived credentials where possible (e.g., IAM roles, workload identity, OIDC)
What not to rely on
- Plain
.envfiles in production - Database-only storage without a secrets system
- Kubernetes secrets without encryption and access controls
- Manual copying of secrets between environments
Practical recommendation
- If you’re on a major cloud: use the cloud-native secrets manager.
- If you need cross-cloud or self-hosted control: use Vault.
- If you want simple developer UX with good security: consider Doppler or 1Password Secrets Automation.
If you tell me your stack (AWS/GCP/Azure, Kubernetes, serverless, etc.), I can recommend the best specific setup.