Get a weekly scorecard on your Heroku apps
Every Monday, WebRun opens Heroku, counts deploys, build failures, and dyno hours for every app, attaches the scorecard as notes on your team's recurring review event in Google Calendar, and posts the same summary to Microsoft Teams.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I track Heroku deploys and dyno usage across all my apps every week?
WebRun reviews every Heroku app each Monday, counting deploys, build failures, and dyno hours for the week. It attaches the scorecard as notes on your team's recurring review event in Google Calendar and posts the same summary to Microsoft Teams, so the whole team walks into the review already knowing which app needs attention.
- Every app gets a weekly deploy and dyno usage review
- The team walks into review already knowing what needs attention
- Build failures get surfaced weekly instead of getting lost in logs
Built for Engineering managers · DevOps teams · 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
dashboard.heroku.comin a real browser with your saved login - no setup, no API keys. -
1
Heroku - review deploys and dyno usage
WebRun opens Heroku to review deploys and dyno usage. - Open the Heroku dashboard and review every app
- Count deploys, build failures, and dyno hours for the week
- Note any app with a failed build or unusual dyno usage
Done when Every app has a week's deploy and usage count.
-
2
Google Calendar - attach notes to the review event
WebRun opens Google Calendar to attach notes to the review event. - Open the team's recurring engineering review event
- Attach this week's scorecard as notes on the event
- Keep last week's notes in place for comparison
Done when The review event has this week's scorecard attached.
-
3
Microsoft Teams - post the scorecard
WebRun opens Microsoft Teams to post the scorecard. - Post the scorecard to your engineering channel
- List each app with its deploy count, failures, and dyno usage
- Flag the app that needs the most attention
Done when The team has this week's Heroku scorecard in Teams.
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 redeploy or restart an app on its own?
No. WebRun only reads deploy history and dyno usage. Redeploying, scaling, or restarting an app is always done by a person in Heroku.
What counts as unusual dyno usage?
A clear jump from the app's typical weekly hours. It gets flagged for a look, not acted on automatically.
Does the scorecard cover every app on the account?
Yes. It reviews every app under the account each week, not just the ones that had a deploy.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.