Budgets
Set a budget with an amount for each period, follow spend against its pace, and see when a threshold is crossed.
A budget has a start date, a cadence and an amount for each period, and compares each period's spend with its amount. It measures the whole workspace, one saved cost report or one segment. A usage budget counts a quantity in one usage unit, such as tokens or GPU hours, instead of cost (Create a usage budget). Open Budgets under Planning.
Before you start
- Creating, editing and deleting budgets needs the Editor team role in a workspace your team can edit. Every team role can view them.
- A budget measures the cost, or the usage, of the connections the workspace uses; see Manage connections.
Create a budget
- Select "Create budget" in the page header. "Create budget" under Budget progress on the Overview opens the same form.
- Enter a Budget name.
- Under Measures, choose "The whole workspace", "A saved cost report" and the report under Cost report, or "An allocation segment" and the segment under Segment.
- Choose the Start date, the first day of the first period, and set the cadence: a number under Every and a Unit of days, weeks, months or years. A budget starts on or before 31 December 2100. A quarter is every 3 months.
- Enter the amount. With "Same amount for every period" ticked, one amount applies to every period. Untick it to enter an amount for each period the form lists, and add or remove periods. The amount field names the currency the budget is kept in: the one the workspace presents figures in, set under Currency settings.
- Optionally, select "Suggest from history" to fill in the average spend of the last three full months for one period of what the budget measures, then adjust it. When those months reach back before your plan's history begins, the average is taken over the days since it begins. Spend in other currencies without a usable rate is named under the suggestion rather than counted, and a scope billed only in such currencies is said to be so rather than suggested 0. Changing what the budget measures or its cadence afterwards drops the suggestion's note and keeps the amount, for you to adjust or suggest again.
- Under Alert thresholds, keep or change the thresholds: each is a whole percent from 1 to 200 of the period's amount under "Percent of amount", on "Spend" or "Forecast" under "Alerts on" (Forecast thresholds). A forecast threshold waits until there is a forecast, which needs 14 days with cost in one currency. A new budget starts with spend thresholds at 50, 80 and 100 percent and a forecast threshold at 100 percent. Select "Add threshold" to add one, or remove one; a budget keeps at least one and holds a percent once on each.
- Optionally, pick notification channels under Send to. An in-product notification is always sent too.
- Select "Create budget".
A budget created in the product is kept in the workspace's currency. Through the Public API a budget can also use another supported currency, and one created there without thresholds gets spend thresholds at 50, 80 and 100 percent. See the API reference.
A budget counts what a Cost Report counts. A budget on a report counts that report: its filter, virtual tags and settings, so the two always show the same figure for the same window. A workspace budget counts the product's own defaults: credits and refunds left out, tax in, commitments amortised (see Cost amounts). Workspace defaults saved with Save as workspace default change what new reports count, not what a workspace budget counts. A segment budget counts what a report filtered to that segment counts with the same defaults: its direct cost and its share of shared cost. A report carries at most one cost budget and one usage budget; a second cost budget for the same costs needs a second report.
Create a budget from a report
A saved cost report creates its own cost budget without its filter being entered again.
- Open the report and, in its header, open More actions and choose Create budget.
- The form opens on "A saved cost report" with that report under Cost report, named after the report. Change the Budget name if you like.
- Set the start date, cadence, amount, thresholds and channels as in Create a budget, and select "Create budget". "Budget created" confirms it, and the report shows the budget under its totals and its line on the chart (Read the result).
Create budget is disabled with "Save your changes first" while the report has unsaved changes, because the budget measures the saved report, and with "This report already has a cost budget" once it has one. A usage budget on a report is created on Budgets (Create a usage budget).
Create a usage budget
A usage budget counts a quantity in one usage unit, such as Tokens or GPU-Hours, instead of cost: the rows of one saved cost report whose usage unit is exactly the budget's unit, as the report's Usage measure counts them (see Usage and count). It needs that report, and it cannot measure the whole workspace or a segment, because a segment's share of shared cost divides money, not quantities. Its periods, cadence, states and percent thresholds, and the channels it sends to, work as for a cost budget, except that it has no forecast: its thresholds are all on its usage so far, and Alert thresholds offers no "Forecast".
- Select "Create budget" and enter the Budget name.
- Under Budget type, select "Usage".
- Choose the cost report. A usage budget requires one.
- Choose the Usage unit. The form offers the units the report's rows carried in the last 90 days, highest quantity first; a report with no usage in that time cannot hold a usage budget yet.
- Choose the Start date and set the cadence as for a cost budget.
- Enter the Budget quantity in that unit, or a quantity for each period, optionally pick channels under Send to, and select "Create budget".
To hold AI to a budget counted in tokens, choose the "AI tokens" report of the AI spend dashboard and the unit Tokens. The budget counts every AI line counted in tokens, across models and token types, and leaves out AI lines in another unit, such as Amazon Bedrock's lines in Units. Its thresholds fire on the tokens used so far, as a cost budget's fire on its spend.
Core-Hours, GiB-Hours and GPU-Hours, the units of Kubernetes rows, count only on a report filtered to a cluster, a namespace or the Kubernetes provider.
A usage budget's amounts, its usage so far, the prorated amount and the projection are quantities in its unit, never converted to a currency and never added across units. Through the Public API and the Terraform provider a usage budget still carries a currency, but its amounts are not in it: its measure says what they count. See the API reference.
Follow a budget

The list shows each budget with its state, its cadence, the current period, the spend so far, or a usage budget's usage in its unit, the period's amount and the share used; search finds a budget by its name. The amount is spread evenly over the period's days, so the state compares spend with the share of the amount the days so far may have spent:
| State | Spend in the current period |
|---|---|
| "On track" | Within the amount spread over the days so far |
| "At risk" | Ahead of it, so the period is on pace to pass its amount |
| "Over" | Past the period's whole amount |
| "Not started" | The budget's start date has not come yet |
Open a budget by its name to see its amount and cadence under its name, "Current spend" against "This period’s amount", the share used against the share of the period elapsed, with a mark on the bar where the period stands, and what is left or how far over the amount the spend is. One line then says where the period ends, with how far over the amount that lands or what it leaves: "Forecast: …" on a cost budget with a forecast, otherwise "At this pace: …" (Forecast thresholds tells the two apart). Below come its Alert thresholds, the Periods with their amounts, and the Spending trend of past periods, each with what was spent and the percentage of its own amount. A cost budget without a forecast that holds a forecast threshold says "No forecast for this period yet: a forecast needs 14 days with cost in one currency." The Overview page shows the same progress under Budget progress.

Edit or delete a budget
- Edit: select Edit on the budget's page, or "Edit" in the menu of its row in the list, change the Budget name, the amount or the amount of each period, what it measures under Measures, a usage budget's unit, the thresholds under Alert thresholds, or the channels under Send to, and select "Save changes". A threshold kept at the same percent, on spend or on the forecast, keeps whether it fired this period; a new one starts armed. The currency, the start date, the cadence and whether the budget measures cost or usage stay the ones it was created with; a different cadence or measure is a new budget. When a usage budget's unit changes, its periods are kept.
- Delete: on the budget's page, open More actions and choose Delete, or select "Delete" in the menu of its row, and confirm in Delete budget, which names the budget. This cannot be undone.
When a threshold is crossed
Planned: budget alert notifications
Costfluent checks budgets every hour. When spend for the current period reaches a threshold of that period's amount, it records the crossing, creates an in-product notification and sends it to the enabled channels the budget names. When several thresholds are crossed at once, only the highest is sent, the spend threshold when a spend and a forecast threshold share the percent, and the others are spent for the period too. On the Alerts page, each threshold is a row under Configured alerts of kind Budget threshold, or Budget forecast threshold, and Last fired shows when it was crossed.
The budget's own page lists its thresholds under Alert thresholds: each reads "Armed" until it is crossed and "Firing since" the day it was until the next period arms it again, and the card names the channels they are sent to. "View all alerts" opens the Alerts page.
Forecast thresholds
A forecast threshold is held against where a cost budget's current period is forecast to end: the spend so far plus the forecast for the period's days still to come, over the budget's own scope and in its currency, made as the forecast a report draws is made for its scope. When the forecast reaches the threshold's percent of the period's amount, Costfluent sends the notification once for the period, while there is still time to act. It states the forecast, its range, the period's last day and the spend so far. A forecast that falls back under the threshold and rises again in the same period sends nothing more.
A forecast needs 14 days with cost in the 12 weeks before the days whose cost is still arriving, all in the budget's currency. Until then, or while that history is in several currencies or another one, a forecast threshold stays armed and the budget's page says what a forecast needs. A usage budget has no forecast and takes no forecast threshold.
The budget's page shows one figure for where the period ends: the forecast, "Forecast: …", when there is one, otherwise "At this pace: …", which spreads the spend so far over the whole period at the same daily rate. The pace decides whether the budget is "At risk", which is why the share used runs ahead of the share of the period elapsed on an "At risk" budget; forecast thresholds alert on the forecast alone, so a budget can be "At risk" while its forecast stays under the amount, most of all early in a period or after a one-off charge.
A budget that measures a saved report also marks the crossing on that report's chart, as an annotation naming the budget and the threshold; see Annotations.
How it behaves
- A budget whose report was deleted shows "Spend unavailable", never zero, and cannot cross a threshold. Its page names the deleted report until you choose what it measures under Measures or delete it.
- A period in which a usage budget's report carried no row in its unit shows "No usage in" and the unit, never zero, and cannot cross a threshold. When a provider renames a unit, the budget measures nothing until you change its unit.
- Spend reaches back as far as your plan's history does, as a report's does. A period that ends before your plan's history begins shows "Before your plan's history" in the Spending trend, never zero. A period that starts before it is counted from the day it begins and says so: the list and the budget's page show "Counted from …: cost history before it is not included in your plan.", and the Spending trend adds "from …". Thresholds are held against the spend counted from that day.
- Cost billed in another currency with no usable exchange rate is not counted and is named in the list, on each period of the Spending trend it falls in, and under a suggestion: "Not counted: … billed in other currencies without a usable rate." A threshold fires on the counted cost alone, and its notification, in the product and by email, Slack, Microsoft Teams or webhook, names the rest per currency.
- Each threshold fires once per period, and is armed again when the next period starts. Changing the current period's amount, what the budget measures or a usage budget's unit arms again each fired threshold its spend, its usage or its forecast no longer reaches, so it fires when it is crossed again; a threshold still reached stays fired for the period. Periods follow the budget's start date: a monthly budget from the 15th runs from the 15th to the 14th, and one from the 31st keeps the 31st in the months that have one.
- After the last period you entered, every later period keeps the last amount, so a budget never stops measuring.
- Periods turn over at midnight in the workspace's time zone.