For GitHub Actions users
See exactly which repo and which team is burning your CI minutes.
Your GitHub bill shows one aggregate number. WorkflowFerret breaks Actions spend down by repo, team, and workflow, and flags likely waste, so you know where the money is actually going before you cut anything.
4 questions, about 30 seconds, no card, no account created.
All repositories · last 30 days
Actions spend
$4,180
Minutes
372,400
Flagged waste
$910
| Repository | Team | Minutes | Cost |
|---|---|---|---|
| api-gateway | Platform | 96,200 | $1,124 |
| web-app | Frontend | 74,800 | $842 |
| data-pipeline | Data | 61,300 | $735 |
| mobile-ci | Mobile | 44,100 | $496 |
| 14 more repos | · | 96,000 | $983 |
Oversized runner: data-pipeline uses 16-core on 3 jobs averaging 4% CPU, est. $210/mo
Status
This product does not exist yet.
We're building it. This page collects an early-access list so we can tell people who actually have this problem when it ships. Joining does not create an account, start a trial, or charge you anything, and you can leave the list at any time.
Scope
What it will do
- Ingest your Actions run/job history and billing usage, and attribute cost per repo, team, and workflow.
- Flag likely waste: oversized runners, cache misses, retry loops, and stale scheduled workflows still running.
- Read-only against your existing GitHub-hosted or self-hosted runners, no migration required.
What it won't do at launch
- No auto-remediation in v1. It flags issues, it doesn't cancel jobs or edit your workflow files for you.
- GitHub Actions only at launch, no support for other CI providers yet.
- Needs an org admin to grant read access to your Actions billing/usage data and workflow logs, a short setup step.
- Cost estimates depend on GitHub's own billing API; it won't be more precise than what GitHub reports.
Why this exists
One number on the invoice is not an answer.
GitHub's own billing dashboard reports a single aggregate dollar figure for Actions usage at the org level. It doesn't break spend down by repo, team, or workflow (per GitHub's published Actions billing documentation, checked August 2026).
Tools like Depot and Namespace.so sell replacement runner infrastructure, which is a different thing. They don't attribute cost on the runners you already have. WorkflowFerret is aimed specifically at teams who want to see where an existing bill is going, not switch runner providers.
Replace your runners
Depot, Namespace.so, BuildJet
Different category
Attribute the bill you already have
WorkflowFerret
What this is
Price
$250
/ month
This is the real price we plan to charge at launch, not an introductory rate, not a discount that expires. We're showing it now so the people joining this list are the people who would actually pay it. No card required to join.
4 questions, about 30 seconds, no card, no account created.
Early access
Is your Actions bill actually a problem yet?
Tell us a little about your setup. We'll email you once to confirm what you signed up for, then again when there's something real to show you.