Quotas

The resource ceilings that apply to your organization on Gigadrive Network, how a denial reaches you, and how to get one raised.

A quota bounds how many platform resources your organization can hold at once, independent of what it spends. Hitting one never interrupts something already running: a quota refuses to allocate more, and nothing else.

The quotas

Quota	What it counts	Checked when
Applications	Applications your organization can create.	Creating an application
Environments per application	Environments a single application can have, including production and preview.	Creating an environment
Storage buckets per environment	File-storage buckets a single environment can hold. A bucket replicates per environment, so it uses one slot in each.	Creating a bucket
Deployments per day	Deployments created in a rolling 24-hour window.	Creating a deployment
Concurrency	Requests a single Function can process at the same time.	While serving
Active memory	Total memory of Functions currently starting or handling traffic across your organization. Scaled-to-zero Functions do not count.	Starting or waking a Function
Always-warm applications	Applications with paid always-warm residency enabled.	Enabling always-warm
Organization members	People in your organization. Paid plans grow the team by purchasing seat licenses.	Shown for review on the Limits page

The values behind each quota come from your plan, and Plans lists them. Concurrency is the one worth understanding rather than looking up, because it decides how far a single Function scales out under load. See Concurrency.

Deployments per day counts every deployment row created in the window, including builds that failed. Deployments the platform cancelled itself because a newer commit superseded them are excluded, but a deployment you cancel still counts.

Seeing where you stand

Open /{organization}/settings/limits in the console. Every quota is listed with its effective limit and its live usage, and the bar turns red once usage passes 80% of the limit. A quota that Gigadrive support has raised for your organization specifically carries a "Custom limit" badge and keeps its raised value regardless of plan.

Any member of the organization can read that page. The Concurrency figure there is the busiest single Function in your organization at that moment, read live from the edge.

Quotas are not budgets

A quota caps how much you can hold. A budget caps what you can be charged, and unlike a quota it does suspend running Functions when it engages. See Spend caps and budgets.

What a denial looks like

Every quota refusal carries the same message, naming the quota, the usage, and the limit:

Applications quota reached (10/10). Contact support to request a limit increase.

The console shows that text inline on the form you were using. The public API returns it as HTTP 429 when you create an application or a deployment:

{
  "error": "Deployments per day quota reached (200/200). Contact support to request a limit increase."
}

Two refusals have their own shape:

A deployment whose build config asks for more memory than your plan allows is refused while the deployment is being prepared, before anything is packaged, and names the Function:

Function dist/index.js requests 8192 MB of memory, but the current plan allows up to 4096 MB per function. Lower the function's "memory" setting or upgrade your plan.

Deployments already serving are unaffected by that check, so lowering your plan does not take an existing deployment down. The limit re-applies the next time you deploy. See Memory and CPU for setting the value.

When your organization is at its Active memory ceiling, a Function that needs to start cannot, and the visitor gets HTTP 503 with the error code EDGE_ORGANIZATION_COMPUTE_LIMIT and the title "Compute limit reached". Functions already running keep serving.

Raising a quota

Two routes, and only one of them is self-serve.

Upgrading the plan applies its values immediately, to what you already have as much as to what you create next. Per-Function memory is the exception, because it is checked at deploy time: a Function gets the higher ceiling on its next deployment.

For a limit above what any plan gives you, contact Gigadrive support. Support applies a per-organization override, which takes precedence over the plan value in both directions and is what the "Custom limit" badge on the Limits page is telling you about. There is no API or CLI for requesting or applying one.