Budget

What it does

Budget sub-allocations author a currency and a monthly limit per budget scope for your organization. There is no standalone Budget surface in the shipped admin console. Budget authoring was folded into the unified Quotas & Budgets surface (/system/quotas), where a budget is an optional per-scope typed budget sub-object ({ currency, monthly_limit }) on a Quotas row.

Surface retired — authored from Quotas & Budgets

The former standalone System → Budget page has been retired (admin-0246 / F8 Phase-2): its /api/v1/admin/system/budget/{set,list} routes were removed and the budgets config domain is now inert. Budgets are authored today from System → Quotas & Budgets. This page is kept as a pointer so existing deep-links still land on an accurate explanation; author budgets on Quotas & Budgets.

Configure in the UI

Author budgets from the Quotas & Budgets surface — see Quotas & Budgets → Configure in the UI for the current step-by-step. In short: open System → Quotas & Budgets, add or edit a quota, and set its optional budget dimension (currency + monthly limit) for the chosen scope.

Historical capture — the former standalone System → Budget surface, now folded into Quotas & BudgetsCitadel synthetic data on a non-production Arbitex demo instance. Never client data.

Enforcement pending

Budget allocations are authored and synced to config, but no platform projector enforces a budget cap yet. Today the authored monthly limit only powers the spend-vs-limit view under Monitoring → Budget — the Monitoring budget gauge reads the typed budget sub-object off the quotas domain — it does not block or throttle spend.

API equivalent

The standalone /api/v1/admin/system/budget/{set,list} routes no longer exist. A budget rides on a Quotas object as an optional typed budget sub-object, so it is authored through the Quotas surface’s backend seam under /api/v1/admin/users-access/quotas — see Quotas & Budgets → API equivalent for the current list / upsert / delete calls and object shape.

Plan & availability

Budget authoring is available on every plan. Because enforcement is pending, no plan tier changes how a budget behaves today — every tier gets the same spend-vs-limit visibility and none get a hard cap yet.

Deployment notes

On a Hybrid Outpost, budgets are authored and stored the same as on the cloud admin console; the spend-vs-limit view under Monitoring reads from the same deployment’s usage rollup. In an air-gapped deployment, usage rollup still populates locally, so the spend-vs-limit view works without external connectivity.

Related

• Quotas & Budgets — the shipped home for budget and quota authoring.
• Budget & cost — where the authored monthly limit is actually shown against spend.
• Config Backup & Restore — budgets are included (secret-free) in every backup snapshot.