Automated CodeSandbox Credit Usage Alerts
Every morning, WebRun signs into CodeSandbox, reads the workspace credit usage against the plan, works out the daily burn rate and the projected run-out date, names the devboxes consuming most, posts the picture to Telegram, and texts the admin through Twilio when credits will not last the sprint.
How do I know before my workspace runs out of VM credits?
Every morning WebRun signs into CodeSandbox, reads the workspace VM credit usage against your plan, and works out the daily burn rate and projected run-out date. It posts the picture to Telegram with the heaviest devboxes named, and texts the admin through Twilio only when credits will not last the cycle.
- The run-out date is projected daily instead of discovered mid-sprint
- The devboxes burning the most credits are named with their owner
- A text only arrives when credits will not last the billing cycle
Built for engineering managers · workspace admins · startup CTOs · platform teams
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
codesandbox.io/signinin a real browser with your saved login - no setup, no API keys. -
1
CodeSandbox - read credit usage and burn rate
codesandbox.io
WebRun opens CodeSandbox to read credit usage and burn rate. - Sign in to CodeSandbox and open the workspace usage page
- Record the VM credits used so far this cycle and the allowance on the plan
- Work out yesterday's consumption and the average daily burn over the last seven days
- Project the run-out date if the current rate holds, against the days left in the cycle
- List the devboxes and sandboxes consuming the most credits, with the member who owns each
- Never change the plan or buy credits: WebRun reads usage only
Done when Credits used, burn rate and projected run-out date are all recorded.
-
2
Telegram - post the daily usage picture
telegram.org
WebRun opens Telegram to post the daily usage picture. - Post credits used, credits left and the days remaining in the cycle
- Show the average daily burn and the projected run-out date
- Name the top consuming devboxes with their owners
- Note any devbox left running with no recent activity
Done when The team channel has today's usage picture on Telegram.
-
3
Twilio - text the admin when credits run short
twilio.com
WebRun opens Twilio to text the admin when credits run short. - Text the workspace admin only when the projection runs out before the cycle ends
- State the run-out date, the credits left and the top consumer in one message
- Stay quiet on days when the projection is comfortable
- Send only to the admin's own number
Done when The admin has been warned before builds could stop.
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 buy more credits or change the plan?
No. WebRun reads usage and warns you. Buying credits and changing a plan both spend money, so they stay with the workspace admin every time.
Does it shut down idle devboxes?
No. Idle devboxes are named in the Telegram post with their owner so a person can decide, because shutting one down can interrupt work someone is mid-way through.
How is the run-out date worked out?
From the average daily credit burn over the last seven days, carried forward against the credits remaining. The date sits beside the end of the billing cycle so the gap is obvious.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.