Skip to Content
Open Beta — managed Kubernetes, DNS & more are live.
📊

Quotas

Updated 2026-11-20
On this page

Quotas

Quotas set the maximum resources a project can use, such as instances, volumes, networks and IP addresses. Watch your usage against them and request an increase when your needs grow.

Every project has a quota for each resource type. When usage reaches a limit, further creation of that resource is refused until you free some up or the limit is raised. Quotas are per project, so a busy project does not starve the others.

You can view current usage against each limit in the console and request an increase for any resource you are close to exhausting. The request is reviewed and, once approved, the new limit applies to that project.

Screenshot — The quota view showing usage bars for each resource type against its limit
The quota view showing usage bars for each resource type against its limit

Key concepts

Quota — The maximum amount of a resource type a project may hold.

Usage — How much of a resource the project is currently consuming.

Limit — The ceiling for a resource; creation fails once usage reaches it.

Quota request — A request to raise a limit, reviewed before it takes effect.

Before you start

  • A project whose usage you want to review.
  • An idea of which resource is constraining you and how much more you need.

Step by step

  1. Open quotas

    Open your project settings or Billing to view the project's quotas and current usage.

    Screenshot — The quotas panel with per-resource usage
    The quotas panel with per-resource usage
  2. Compare usage to limits

    Look for any resource where usage is close to its limit; that is what will block your next create action.

  3. Request an increase

    For a constrained resource, submit a quota increase request describing the new amount you need.

    Screenshot — The quota request form
    The quota request form
  4. Track the request

    Follow the request until it is approved; the higher limit then applies to the project.

Examples

View project quotas and usage (Patrii CLI)
patrii quota current --project <project-id>

Limits & specifications

Examples of resources governed by quotas:

ResourceExample limit
InstancesHow many compute instances the project can run.
VolumesNumber and total size of block volumes.
Floating IPsHow many public IP addresses the project may hold.
NetworksNumber of private networks and routers.

Best practices

  • Check usage before a big rollout so a limit does not stop you mid-deploy.
  • Request increases ahead of need rather than at the moment you hit the wall.
  • Release resources you no longer use to reclaim quota instead of asking for more.
  • Keep separate environments in separate projects so their quotas do not compete.

FAQ

My resource creation was refused for quota. What do I do?
You have hit the limit for that resource. Free some up by deleting what you no longer need, or submit a quota increase request for that resource and wait for approval.
Are quotas shared across my projects?
No. Quotas are per project. Each project has its own limits, so usage in one does not consume another's quota.
How long does a quota increase take?
The request is reviewed before it takes effect. Track it from where you submitted it; once approved, the new limit applies to the project.

Learn more

Everything you can do here in the console is also available through the Patrii Cloud API for automation and scripting.

Was this article helpful?
Thank you for your feedback. Still stuck? Contact us