Resource Quotas¶
Every organization is assigned a quota profile that caps how many of each resource it can create. Quotas keep usage predictable and are enforced automatically when you create resources.
How quotas work¶
- Per organization: Quotas apply to your whole organization, not to individual projects.
- Counts, not capacity: Quotas limit the number of objects of each type — not raw CPU, memory, or storage totals.
- Profile-based: A platform administrator assigns your organization a profile, and the profile sets the limit for each resource. Higher tiers allow more. You generally cannot change your own organization's profile.
What is counted¶
Quotas cover the resources you create across the platform, such as:
- Projects and users
- Infrastructures and service configs
- Networks, routers, firewalls and SSH keys
- Managed Kubernetes clusters and their nodes
- Virtual machines
- PostgreSQL instances
- Application templates, instances and cluster fleets
The exact set of limited resources and their limits depends on your organization's profile.
Viewing your usage¶
The Resource Quotas page shows, for each resource, how much you have used against your limit — as a count and a percentage. Usage is grouped into health bands:
| Band | Usage |
|---|---|
| Healthy | below 75% |
| Warning | 75% to 90% |
| Critical | 90% or above |
Note
Viewing quotas requires the quota-view permission. If you do not see the page, ask an organization administrator.
When you hit a limit¶
If creating a resource would exceed your quota, the action is blocked and you see a "quota exceeded" message naming the resource. A notification links you to the Resource Quotas page so you can review usage.
To proceed, either delete resources you no longer need, or ask a platform administrator to raise your profile's limits.