This page is not translated yet. Deutsch is switched on so the navigation and URLs can be tested; the text below is the English original. Use the language selector in the header to switch back, or see the documentation home.
Budgets & Deposits
Deposits and budgets are two separate mechanisms that are easy to confuse. A deposit is the prepaid money that pays for usage. A budget is the cap that stops a team spending more than you intended. An organization can hold either without the other, though most want both.
The distinction is worth getting straight before you configure either of them. A deposit answers whether there is money available to pay for a workload, while a budget answers whether the team in question is permitted to spend it. Because they answer different questions, a job has to satisfy both before it launches, and either one can block it on its own.
Deposits, which fund usage
Deposit types
The four deposit types and which charges each one is able to pay for.
Assign and track deposits
Attach deposits to workspaces, monitor consumption, and pull the consumption report.
Budgets, which cap usage
How budgets work
What a budget measures, what it can be set against, and which one is enforced when several apply at once.
Create a budget
Set a cap against a member, project, workspace, or organization.
Budget enforcement
What happens when a cap is reached, covering the submission check, queuing, and strict budgets.
Alerts, which cover both
Related
- Billing & reports — reconciling actual charges against budgets and deposits
- Organizations & workspaces — the structure deposits and budgets attach to
- Usage dashboards — watching consumption trend before a cap is hit