> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paradime.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Budgets

> Set monthly Snowflake spend budgets per warehouse or for the whole account in Radar, track them against actuals, and get alerted at 80% and 100%.

Cost monitoring tells you what you spent. A **budget** tells Radar what you meant to spend, so it can warn you while the month is still running. Budgets live under **Radar → Snowflake → Budget**.

<Warning>
  **Prerequisites**

  * A Snowflake cost connection, set up in [Cost Management](/products/radar/getting-started#id-1.-cost-management).
  * Editing budgets requires the Radar data alerts permission. See [Roles and permissions](/products/settings/users/roles-and-permissions).
</Warning>

## Set a budget

The budget table lists an **Account** row and one row per warehouse, each showing month-to-date spend, a usage bar, and its monthly budget.

1. Type a monthly amount in a row's budget field and confirm it.
2. Clear the field to remove that budget.

A warehouse you have budgeted stays in the table even if it stops appearing in recent spend, marked as not seen recently, so a budget never disappears silently.

### Distribute a total across warehouses

If you think in terms of one monthly number for the account, use **Distribute budgets**:

1. Enter the monthly total.
2. Choose how to split it: **equally** across warehouses, or **by historical spend** using the last 30 days.
3. Adjust any of the proposed allocations inline. Radar flags an allocation that is already below that warehouse's month-to-date spend.
4. Apply. The allocations are saved together as one change.

## Read the chart

The budget-vs-actuals chart plots cumulative spend against a **pace line**: the budget spread across the month day by day, reaching 100% on the last day. Spend above the pace line means you are tracking to exceed the budget, below means you are tracking under.

Filter the chart to a single warehouse or to all of them, and change the window (this month, last month, 3 or 6 months, 7 or 30 days). Over multi-month windows the pace line steps at each month boundary and uses the budget that was actually in force then, so past months stay honest after you change a budget.

## Budget alerts

When a budget is set, Radar watches it on the daily cost run and alerts:

* once when spend crosses the **warning threshold**, 80% of the budget by default;
* once when it crosses **100%**.

Each target alerts at most once per threshold per calendar month, and crossing both thresholds between runs sends only the higher one. Editing or removing a budget re-arms its alerts for the rest of the month.

Alerts are delivered to the destinations you already configured for [Data Alerts](/products/radar/real-time-alerting/configure-alerts).

<Info>
  Budgets can also be set on a [usage group](/products/radar/cost-management/usage-groups) rather than a single warehouse, which is usually how teams and environments are budgeted.
</Info>


## Related topics

- [Budget & Consumption](/products/dino-ai/budget-and-consumption.md)
- [Budget & Consumption for DinoAI credits](/changelog/2026-07-29/budget-and-consumption.md)
- [Radar cost controls: budgets, usage groups, custom alerts](/changelog/2026-09-09/radar-cost-controls.md)
- [Usage groups](/products/radar/cost-management/usage-groups.md)
- [Radar](/products/radar/index.md)