Budgets
Cap what an organization can be charged in a month, get warned at 80 percent, and know exactly what stops at 100.
A budget is a hard monthly ceiling on rated spend for the whole organization. Cross it and Gigadrive stops the meter rather than letting the bill keep growing, which makes it the control you want before you hand an API key to a job you have not watched run yet.
Set it under Spend budget at /{organization}/settings/billing. Owners and admins only.
Setting one
Type an amount in euros and save. The field is a single number, and an empty field is not the same as a zero.
| You enter | Effective cap |
|---|---|
| An amount | That amount, every month |
| Nothing | Your plan's default cap |
Starter carries a default cap of €25 per month. Pro and Enterprise have no default, so an organization on either runs uncapped until you set a budget.
What counts toward it
Rated euros, month to date. Gigadrive prices your usage through the same rating that builds your invoice, then compares the total against the cap. One number therefore covers every metric and every product, and there is no per-metric budget to keep in sync.
The cap is enforced hourly rather than per request.
Usage can take up to an hour to appear, so treat the cap as accurate to within an hour rather than to the second.
What happens at each threshold
At 80% you get one warning email for the period.
At 100% the organization is capped. New deployments are refused: the API answers HTTP 402 with "Organization billing cap reached. Raise your budget to create new deployments.", and the console says "Your organization has reached its monthly billing cap. Raise your budget to keep deploying." Running compute is suspended, and anything that starts back up is suspended again. A "Cap reached" badge appears on the billing page.
Visitors hitting a suspended application get HTTP 503 with a plain explanation that the organization reached its compute limit, not a generic error page.
Saving a higher budget lifts the cap immediately. Deploys unblock straight away and paused compute resumes on its next request, without waiting for the next hourly check or the next month.
A budget cap is not the same as running out of included usage
Starter also stops when its included compute allowance is exhausted, which is a separate mechanism with a separate email and a separate remedy. A budget cap says raise your budget. An exhausted allowance says upgrade your plan. See Spend caps and budgets.
Related controls
Build cache paid overage is opted into separately, on the Limits page, and it pauses while the spend cap is engaged. Quotas are a different thing again: they bound how many resources you can hold, independent of what you spend.