Save money

Budgets and alerts

Set a monthly budget and choose where spending alerts go.

About 6 minutes

Budgets and alerts need the Pro or Business plan. Set a budget for each connected cloud account, then choose where alerts go.

Set a monthly budget

Open FinOps → Budgets. The page lists active cloud accounts with Spend this month. An account without a budget shows No budget set. Click its pencil, labelled Edit budget for <account> (1).

Enter Monthly budget * (1). Currency comes from the account's bill, so spend and budget use the same unit. Default alert threshold starts at 80%. Under Auto-create alert rules at (2), choose 50%, 80%, 90%, or 100%; each choice shows its amount. 80% and 100% are selected by default.

Choose where breaches go

Notify on breach (3) shows where budget alerts go. If you have no channel, it says “No notification channels yet. Pick where budget breaches go once — set it up right here.” Click Add channel. Choose Email, Slack, Microsoft Teams, or Webhook (1), enter a name (2) and address or URL (3), then click Create channel (4).

The new channel is routed to budget breaches straight away. Also use by default when no channel is routed also makes it a fallback for other notification sources without their own route. Slack, Teams, and webhook URLs are stored encrypted and never shown again.

Click Save budget (1). The example has two routed channels.

The account card now shows the amount used and Alert at 80%. In this example it reads “$0.00 of $250.00 · 0% used”.

When spend updates

Spend this month sums daily costs for the current calendar month in the latest completed scan. Run a scan to refresh it. On the first day of a month it can be $0 until your cloud reports its first full day. AWS Cost Explorer usually reports a day later.

The “on track to exceed” warning uses your month to date spend divided by elapsed calendar days, then projects that daily rate across the full month. It appears when the projected month end spend is greater than the budget. A zero spend projects zero.

Your selected thresholds also create rules on FinOps → Alerts, such as “Budget 80% — <account>” and “Budget 100% — <account>”.

Create your own alert rule

On FinOps → Alerts, click New rule (1). The switch at the top, Anomaly email alerts (warning/critical), controls email delivery for warning and critical anomaly alerts.

Enter Rule name (1), choose Alert type (2), then a Metric (3), Condition, and Threshold (4). Under Notifications, check where the rule will send alerts. You can also choose Also show in the in-app notifications feed and Rule enabled. Click Create rule (5).

For example, “Daily spend over $50” uses Cost threshold, Daily spend, Greater than, and 50.

Choose a type to pick its metric:

  • Cost threshold checks daily spend, monthly spend, or the latest day's cost change against the preceding seven days.
  • Waste detected checks estimated monthly waste savings. Security checks the average security score in the latest reports.
  • Budget checks month to date budget use or projected budget use. Anomaly checks the latest day's cost spike against the preceding seven days.

Rules are evaluated by the hourly alert job against the latest completed cost reports. It avoids sending another alert for the same rule within roughly a day. Find and clean up waste explains the waste items behind those savings.