Catch Azure cost spikes before the bill lands
Every morning, WebRun opens the Azure portal, reads yesterday's spend by subscription, resource group, and service, compares it with the running daily average, drafts a Gmail note to the owner of anything that jumped, and logs every spike in an Airtable tracker so the trend is visible before the invoice arrives.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I get alerted when my Azure costs spike?
WebRun opens the Azure portal every morning, reads yesterday's spend by subscription, resource group, and service, and compares each line with its 7 day average. It drafts a Gmail note to the owner of anything that jumped and logs every spike in Airtable, so cloud overspend surfaces days before the invoice.
- Cost spikes are caught the next morning instead of at invoice time
- Every spike arrives with a named owner and a ready-to-send draft
- The Airtable tracker builds a spend history you can review each month
Built for cloud engineers · DevOps teams · FinOps teams · IT managers · CTOs
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
portal.azure.comin a real browser with your saved login - no setup, no API keys. -
1
Microsoft Azure - read yesterday's cloud spend
WebRun opens Microsoft Azure to read yesterday's cloud spend. - Open the Azure portal and go to Cost Management and Billing
- Open Cost analysis and set the view to yesterday, grouped by subscription and then by service
- Capture the total for each subscription, resource group, and service
- Compare each figure with its average over the previous 7 days and mark anything above your threshold
- Note the tags on each spiking resource so the owner can be identified
Done when Yesterday's spend is captured and every line above the threshold is marked with its owner tag.
-
2
Gmail - draft a note to the owner of each spike
WebRun opens Gmail to draft a note to the owner of each spike. - Draft one short email per spike to the owner named on the resource tag
- State the subscription, the service, yesterday's cost, the 7 day average, and the size of the jump
- Leave every message in Drafts. WebRun never sends the email itself
- Skip any spike that was already emailed about in the last 3 days
Done when Every new spike has a ready-to-send draft waiting in Gmail for your review.
-
3
Airtable - log every spike and its trend
WebRun opens Airtable to log every spike and its trend. - Add one row per spike to your cloud cost tracker with the date, subscription, service, amount, and percentage jump
- Update the row for any spike that is still running from a previous day rather than creating a duplicate
- Mark spikes that have returned to normal as resolved
Done when The Airtable tracker holds an up-to-date record of every cost spike and its status.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it email engineers without my approval?
No. Every message is left in Gmail Drafts for you to read and send. WebRun writes the note, names the resource and the numbers, and stops there. Only the internal Airtable log is written automatically.
Can it change or shut down a resource that is overspending?
No. WebRun only reads Cost analysis in the Azure portal. It never resizes, deletes, or deallocates anything, so a runaway resource is reported to you rather than acted on.
How does it decide what counts as a spike?
It compares yesterday's cost for each subscription, resource group, and service against that line's own average over the previous 7 days, and flags anything past the threshold you set, in both percentage and absolute terms.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.