See which agent-driven branches are driving your CI bill.
Small teams whose parallel coding agents generate frequent CI runs.
This is an early product concept currently being validated. The product is not yet available.
The problem
More branches and pushes create more runner minutes, but the bill does not explain which work caused the increase.
What happens today
Export run history, group jobs in a spreadsheet and adjust workflow triggers.
What I’m exploring
I’m exploring a tool that would offer: a read-only breakdown of CI spend by branch and agent-work label, starting with GitHub Actions.
- Find expensive work patterns
- Separate retries from new work
- Review one weekly spending report
These are proposed outcomes. There is no launch date yet.
Proposed early-access price
Would this save you enough time to be worth paying for? That’s what I’m testing.
$29 / month
No payment is collected. No subscription starts.
Would you use this?
If this is a problem you deal with, tell me a little about your workflow. Joining is an expression of interest. It does not start a subscription.
Please keep client details, credentials and confidential information out of your answers.
If your current tools already handle this, say so.
I want to understand what’s missing before I build anything. Your answers help me decide whether this deserves a next step. — Kai
Optional click and scroll mapping. No form contents, recordings or mouse trails. Basic page and signup funnel events are recorded separately.