Subscription keys and plan limits
Key lifecycle, plan caps, and enforcement errors.
Project owners, billing admins, and anyone blocked by key or plan limit errors.
Learn how subscription keys bind to projects, how plan tiers cap collaborators and non-production branches, and where the product enforces those limits with clear errors.
Every hosted project is powered by one subscription key at a time. Plan limits apply at bind time and whenever you add collaborators or map development/staging branches — not just at purchase.
4 sections4 key takeaways3 related guides
Quick highlights
Every hosted project is powered by one subscription key at a time. Plan limits apply at bind time and whenever you add collaborators or map development/staging branches — not just at purchase.
Review key lifecycle before changing billing, then use the enforcement and error sections when a specific action is blocked mid-workflow.
What you will learn
- One active key binds to one project; release a key before reusing it elsewhere.
- Plans cap collaborator seats and combined development + staging branch capacity.
- Enforcement is explicit — failed actions return readable messages with used/limit counts.
- Keep an unused key or headroom on seats/branches before production cutover windows.
Sections in this guide