Outcome and audience
For Owners, Admins, Editors, or approved billing roles managing a cost boundary.
Before you begin
The selected provider and connection must be active, eligible, and have a supported scope. Choose one currency and reporting timezone.
Where to go
Open Budgets under Control.
Complete the workflow
Keep the selected workspace, provider, period, currency, cost basis, and data-through date visible as you work.
- Choose provider, connection, and supported scope.
- Enter the budget amount, currency, and timezone.
- Set warning and critical threshold percentages in their valid order.
- Review the monthly actual and forecast context before saving.
- Use Delete budget only when the named budget should stop future evaluation.
Interpret the result
Utilization is actual spend divided by the budget amount. Forecast risk is separate and includes quality and freshness context.
Loading, empty, partial, and unavailable states
Loading preserves the current scope. Empty means no records match the authorized scope. Partial or stale data keeps its completed-through boundary visible. Unavailable or permission-denied states explain the missing prerequisite and never substitute zero or another provider.
Provider differences
Budget dimensions follow the connected source. Unsupported resource or tag scopes are unavailable.
Synthetic example
Illustrative example · synthetic data Example: Northstar Labs creates a USD 50,000 monthly AWS service budget with warning at 80% and critical at 95%.
Common mistakes
Do not mix currencies, reverse warning and critical thresholds, or assume deleting a budget deletes cost history.