Playbooks 6 min read· 19 Aug 2026· By Playbooks
Key rotation and per-key spend caps
How to structure keys across environments and teams.
One key for everything is convenient — and dangerous. Here's the model we recommend.
- One key per environment (dev, staging, prod)
- One key per human developer
- One key per third-party service (Zapier, n8n)
- Spend cap on each key sized to expected 30-day usage × 1.5
Rotate any human-developer key when someone leaves the team. Automated keys rotate every 90 days.