Skip to main content
Cloud costs change daily, and waiting for the monthly invoice to spot problems means you’re always reacting too late. Cloud cost alerts in Costory monitor your spend continuously and notify you through Slack, Microsoft Teams, or email when costs cross the thresholds you define.
Cloud cost alerts dashboard in Costory showing active alerts and coverage

​
Prerequisites

  • At least one cloud provider (AWS, GCP, or Azure) connected to Costory
  • A notification channel configured (Slack, Microsoft Teams, or email)

​
Overview

Costory evaluates your cloud spend every day (or twice a day depending on your plan) across AWS, GCP, and Azure. You define what to watch, the threshold that matters, and where to send the notification. Costory handles the rest. Use cloud cost alerts to turn that daily evaluation into proactive notifications instead of manual checks. Where alerts fit in your day-to-day:
  • Catching a cost spike in a specific service before it compounds over the full billing period
  • Tracking team-level budgets with automatic notifications when a team approaches or exceeds its target
  • Monitoring commitment coverage (, ) to avoid paying on-demand rates unnecessarily
  • Watching custom ratios like marginal cost per user or savings plan utilization

​
Setting up a cloud cost alert

1

Navigate to Alerts

Go to Alerts in the Costory app. You’ll see all your existing alerts in one place.
2

Create a new alert

Click Create Alert. Choose from a pre-built template for common alert types or configure your own custom logic.
Create a new alert from a list of predefined templates
3

Set evaluation criteria

Choose the scope and threshold for the alert:
  • Which , service, tag, or cloud provider to watch
  • The threshold amount or formula
  • The time window: daily, week, or month-to-date
Set evaluation criteria
4

Configure notifications

Select where to send alerts (Slack, Microsoft Teams, or email), who should receive them, and the notification frequency.
5

Save and activate

Your alert appears in the summary view and begins evaluating data after the next data refresh.

​
Alert types

​
Cloud cost alerts

Cloud cost alerts track actual spending against thresholds you define. Each threshold supports one of four modes:
ModeWhat it does
is aboveFires when spend exceeds a fixed amount
is underFires when spend drops below a fixed amount
increases by more thanFires when spend rises by more than a set amount (USD) or percentage (%) compared to the previous period
decreases by more thanFires when spend falls by more than a set amount (USD) or percentage (%) compared to the previous period
Alert threshold mode dropdown with is above, is under, increases by more than, and decreases by more than options
For period-over-period modes, you choose whether to compare by absolute delta (USD) or percentage change. Costory compares the current evaluation window against the previous calendar-aligned period (day, week, or month) using the same data delay rules described below. Multi-threshold severity levels (Info, Warning, Alert) let you escalate notifications based on how far costs have deviated. You can mix absolute and relative thresholds on the same alert, for example an informational notification when weekly spend increases by more than 10% and a warning when it exceeds a hard cap. Evaluation periods can be daily, weekly, or monthly. Use custom formulas for advanced use cases: Savings Plan coverage ratios, marginal cost limits, or cost-per-transaction thresholds. See the example below for a walkthrough.

​
Budget alerts

Budget alerts track spend against allocated with percentage-based triggers. When a team approaches or exceeds its target, Costory notifies the budget owner and each budget line owner automatically. Weekly cumulative sums let you track running totals over the current week, so you can catch budget overruns before the month closes. For a full walkthrough of setting up per-team budgets with automated alerts, see the Automate Cloud Budgets guide.

​
Example: Savings Plan coverage alert

Savings Plan coverage alert
reduce your on-demand costs, but only when they actually cover your usage. If coverage drops, you’re paying full price for compute that should be discounted. A coverage alert catches this early. To set one up, create a cost alert with a custom formula that computes the ratio of covered spend to total eligible spend. For example: 
savings_plan_covered_cost / (savings_plan_covered_cost + savings_plan_uncovered_cost)
Set a threshold at the coverage percentage you want to maintain (e.g., alert when coverage drops below 80%). Use a 7-day rolling window to smooth out daily fluctuations. This same approach works for other ratio-based alerts. You can divide infrastructure cost by active user count (from an external usage metric) to track marginal cost per user and alert when it rises above a target. Or compare against on-demand cost to monitor how much your commitments are saving over time.

​
Example: period-over-period cost spike alert

Period-over-period cost spike alert set to 15% weekly increase
A hard spending cap catches runaway costs, but gradual week-over-week increases can slip under a fixed threshold for months. A period-over-period alert catches these trends early. To set one up, create a cost alert and select increases by more than from the threshold mode dropdown. Enter the change limit as a dollar amount or switch to % for a percentage-based rule. Choose the evaluation period (daily, weekly, or monthly), and Costory compares each window to the same calendar-aligned period immediately before it. For example, to detect a weekly spend increase greater than 15%:
  1. Set the mode to increases by more than
  2. Enter 15 and select %
  3. Set the evaluation period to week
Costory fires the alert whenever the current week’s spend exceeds the previous week’s by more than 15%. You can add a second threshold at a higher severity for larger swings, such as a warning at 15% and an alert at 30%.

​
How alerts are evaluated

Alerts evaluate cost data with a built-in delay to ensure accuracy.
ParameterValue
Evaluation frequencyEvery day, or twice a day depending on your plan
Data delayAt least 48 hours (cloud providers finalize billing data with a delay)
Lookback window4 days
For example, if today is January 15, the alert evaluates spend from January 9 to 13 (a 4-day window, starting 48 hours before today).
Costory does not evaluate the most recent 48 hours because cloud providers (especially AWS) can revise billing data during that window. This avoids false positives from incomplete data.

​
Managing alerts

From the alerts summary page, you can snooze an alert to temporarily pause notifications during a planned migration or expected cost spike. Snoozed alerts stop sending notifications but continue evaluating in the background, so you can review what happened when you un-snooze. You can also delete an alert you no longer need, which removes the alert and its history permanently. When an alert fires, the notification you receive in Slack, Teams, or email includes a direct link to the pre-filtered to the exact scope of the alert. Click View in Explorer to investigate the cost change immediately, without recreating filters manually.

​
Frequently Asked Questions

Costory evaluates alerts every day, or twice a day depending on your plan. Data is checked with at least a 48-hour delay to ensure billing data from your cloud provider is finalized.
Yes. Cloud cost alerts support multi-threshold severity levels (Info, Warning, Alert), so you can receive an informational notification at one threshold and escalate to a warning or critical alert at a higher one.
Snoozed alerts stop sending notifications but continue evaluating cost data in the background. When you un-snooze, you can review any threshold breaches that occurred while the alert was paused.
Yes. You can define custom formulas using any cost metric available in Costory. Common examples include Savings Plan coverage ratios, marginal cost per user, and cost-per-transaction thresholds.
Yes. Each threshold row has its own mode, so you can combine an absolute cap (e.g., “is above $50,000”) with a relative change rule (e.g., “increases by more than 20%”) on the same alert. The highest-severity breach across all rows determines the notification level.
Alerts can be delivered to Slack, Microsoft Teams, or email. Each alert notification includes a direct link to the Cost Explorer pre-filtered to the scope of the alert.

​
Key terms used in this article

  • Lookback window: The number of days of cost data included in each evaluation. Costory uses a 4-day window, starting at least 48 hours in the past to ensure final cost data is available.
  • : Custom groupings that let you scope alerts to teams, products, or environments, regardless of how resources are tagged in the cloud provider.
See the Glossary for a full list of terms.

​
Next Steps

Automate Cloud Budgets

Define per-team budgets and get notified when teams exceed targets

Digest

Auto-triage cost anomalies with AI-generated incident reports

Slack Reports

Send recurring cost snapshots to your team’s channels

Cost Explorer

Drill into specific cost changes with full context

Virtual Dimensions

Create team-level and product-level cost groupings for targeted alerts

Feature Engineering

Clean up billing labels so alerts target the right resources
Last modified on April 10, 2026