No account. No upload. No cookies.

Your CI costs went up. Nothing tells you which PR did it.

Drop in one usage report and Tolly itemizes the Actions bill by workflow, repository, runner and day. Takes about a second. The file never leaves your browser.

Drop your usage report CSV here

The enhanced billing export — Settings → Billing → Usage.

Parsed in this tab. Nothing is uploaded. Close the page and it’s gone.

A month of Actions, itemized

This is the breakdown a real usage report produces.

Net cost$976.65
Run-rate$2,092.82
terraform-plan.yml$263.79
ci.yml$239.47
release.yml$220.91
nightly-e2e.yml$178.17
2025-06-012025-06-14

Daily gross cost, split into compute, storage and other — the spikes are usually nightly jobs.

1

Export the usage report

Organization settings, billing, usage. Pick a month and download the CSV.

2

Drop it in

Read locally, priced from the report's own gross, discount and net columns. No estimates.

3

See where the money went

Cost by workflow, repository, runner SKU and day, with a projected monthly run-rate.

See what every pull request costs, without asking

Tolly is a read-only GitHub app. It attributes every billed minute to the pull request, workflow and team that caused it, then comments on the PRs that make CI more expensive — before they merge.

One email when it opens. Nothing else.

Only your email is sent. Your report stays in this tab. Privacy policy.

Frequently asked questions

Is this a cost estimate or my actual GitHub bill?

Your actual figures. The calculator prices nothing itself — it reads the gross, discount and net columns GitHub already wrote into your usage report, so every total traces back to a number GitHub charged you.

Which workflows are costing me the most?

That is the first thing the breakdown shows. Billed minutes carry the workflow that spent them, so grouping them by workflow ranks your pipelines by spend and usually makes one or two obvious culprits jump out.

What will this month cost me if nothing changes?

The projected run rate answers that: the net cost of the days your report covers, scaled to a 30-day month. Treat it as the pace you are on, not a promise about the final invoice.

Do I need to work out OS minute multipliers myself?

No, and neither does GitHub any more — the old Linux-times-one, Windows-times-two, macOS-times-ten model is retired in favour of flat per-minute rates per runner SKU. Any multiplier you see here is a readability aid comparing a SKU to the cheapest Linux runner.