Automated Gitpod Usage Scorecard
Every Monday, WebRun opens Gitpod, compiles the past week's workspace usage hours and prebuild counts per teammate, emails the engineering manager a short summary highlighting anyone well above the team's usual usage, and logs every teammate's numbers to Airtable so usage trends build up over time.
How do I track my team's Gitpod usage every week?
WebRun compiles your team's Gitpod workspace usage hours every Monday, teammate by teammate. It emails the engineering manager a summary highlighting anyone well above the usual range, and logs every teammate's numbers to Airtable, so usage trends and potential cost surprises get tracked automatically instead of discovered at the invoice.
- Usage spikes get flagged before they show up as a cost surprise
- Adoption trends are visible without pulling reports by hand
- The engineering manager gets a summary without opening every teammate's account
Built for engineering managers · platform teams · DevOps · developer experience 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
gitpod.io/loginin a real browser with your saved login - no setup, no API keys. -
1
Gitpod - compile the week's workspace usage
- Open Gitpod and pull the past week's workspace usage hours per teammate
- Record the prebuild count for each
- Note anyone whose usage is well above the team's usual range
Done when Every teammate's usage hours and prebuild count for the week are captured.
-
2
Gmail - email the eng manager a summary
gmail.com
WebRun opens Gmail to email the eng manager a summary. - Draft a short internal summary email to the engineering manager
- Highlight anyone whose usage was well above the team's usual range
- Send it to the manager only, not the whole team
Done when The engineering manager has this week's usage summary email.
-
3
Airtable - log usage per teammate
airtable.com
WebRun opens Airtable to log usage per teammate. - Log this week's usage hours and prebuild count as a new row per teammate
- Keep prior weeks in place so the trend is visible
- Flag any teammate with no usage at all this week
Done when This week's usage is logged as a new row for every teammate.
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 change anyone's workspace or settings?
No. WebRun only reads usage totals. Changing a workspace or a teammate's settings is never something it does.
Who sees the usage summary?
Only the engineering manager, by email. It's an internal usage report, not shared with the whole team by default.
Why would usage matter to track?
Cloud dev environment hours often tie to cost and to whether the team's workflow is actually adopted, so tracking it helps catch both cost surprises and low adoption early.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.