Automated RunPod Idle GPU Cost Alerts
Every hour, WebRun opens the RunPod console, checks every running pod's GPU utilization and how long it has been running, adds a Google Calendar hold to review any pod idle past your threshold, and posts a Teams alert naming the pod and its running cost so spend does not go unnoticed.
How do I catch idle RunPod GPUs before they run up my bill?
Every hour, WebRun checks every running RunPod pod's GPU utilization and how long it has been running. It adds a Google Calendar hold to review any pod idle past your threshold and posts a Teams alert naming the pod, its GPU type, and its running cost, so idle spend gets caught before the invoice does.
- Idle GPUs get flagged within the hour instead of at the monthly invoice
- Every alert names the running cost, not just that a pod is idle
- A calendar hold makes sure a flagged pod actually gets reviewed
Built for ML engineers · AI startups · research teams · MLOps engineers
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
www.runpod.ioin a real browser with your saved login - no setup, no API keys. -
1
RunPod - check running pods for idle GPU time
runpod.io
WebRun opens RunPod to check running pods for idle GPU time. - Open the RunPod console and list every currently running pod
- Check GPU utilization and total running time for each
- Flag any pod below your utilization threshold for longer than your idle window
Done when Every pod running longer than the idle window has a captured utilization reading.
-
2
Google Calendar - hold a calendar slot to review it
calendar.google.com
WebRun opens Google Calendar to hold a calendar slot to review it. - Add a Google Calendar hold for later today to review each flagged pod
- Title the hold with the pod name and GPU type
- Include the utilization reading in the event description
Done when A review hold exists on the calendar for every flagged pod.
-
3
Microsoft Teams - alert the team with the running cost
microsoft.com
WebRun opens Microsoft Teams to alert the team with the running cost. - Post a Teams alert naming each idle pod, its GPU type, and its running cost so far
- Sort by running cost so the most expensive idle pod appears first
- Stay quiet when no pod is over the idle threshold
Done when The team has an alert for every idle pod with its running cost.
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
Does it stop or terminate the idle pod itself?
No. WebRun only flags idle pods and their cost. Stopping or terminating a pod always stays a decision you or your team makes.
How is idle defined?
You set the utilization threshold and how long a pod can sit below it before being flagged, so the alert matches how your team actually uses GPUs.
Does it track spend across the whole account?
It reports the running cost of each flagged idle pod so far. For full account level billing, RunPod's own billing page remains the source of truth.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.