Prompt
What should I use to store API keys for a small engineering team?
Latest observation
Nov 17, 2026
OpenAI APIWeb search: off
For a small engineering team, the best choice is usually a shared secrets manager, not a wiki, spreadsheet, or code repo.
Good options
- 1Password / 1Password Teams
Great balance of simplicity, auditability, and team sharing. Often the easiest to adopt. - Bitwarden Teams
Good if you want a lower-cost option with solid security and sharing controls. - HashiCorp Vault
Better if you need more advanced secret lifecycle management, dynamic secrets, or infrastructure-heavy workflows. Usually more operational overhead than a small team needs. - Cloud secret managers like:
- AWS Secrets Manager
- GCP Secret Manager
- Azure Key Vault
Best if your apps run mostly in one cloud and you want runtime secret injection.
What I’d recommend for a small team
- For human access and sharing: use 1Password Teams or Bitwarden Teams
- For production/runtime secrets: use your cloud provider’s secret manager
- Avoid storing API keys in:
- Slack
- Google Sheets
- plaintext docs
.envfiles in shared drives- git repos
Practical setup
- Store each key in a shared vault/folder
- Limit access by team/project
- Turn on MFA for everyone
- Rotate keys periodically
- Track ownership and purpose for each secret
- Use separate keys for dev/staging/prod
If you want, I can give you a recommended setup by team size and budget or compare 1Password vs Bitwarden vs Vault.