Home / Blog / Cost and billing
Does GitHub charge for self-hosted runners? The $0.002 per minute fee, postponed
Not today. GitHub announced a $0.002 per minute charge on self-hosted runners for 1 March 2026, then postponed it. A dated table of what it said, and where to watch.
No. GitHub announced a $0.002 per minute charge on self-hosted runner minutes in private repositories on 16 December 2025, to start on 1 March 2026, then postponed it within days “to take time to re-evaluate our approach”, with no new date. When this post was last checked, its billing page still listed self-hosted runners as free usage that does not reduce included compute. Our GitHub self-hosted runner guide counts the full cost.
- GitHub announced a $0.002 per minute charge on self-hosted runners in private repositories on 16 December 2025, to start on 1 March 2026.
- It postponed the charge within days, with no new date; its roadmap item was closed on 19 December 2025.
- When this post was last checked, GitHub's billing page still listed self-hosted runners as free usage that does not reduce included compute.
- GitHub's own pages print three dates for the postponement, 15, 16 and 19 December, and describe one decision.
- Hosted-runner rates already include the platform charge, and public repositories and Enterprise Server were never in scope.
What happened, and when?
Every row below is from a page GitHub publishes, read on the date this post was last checked, and each says which. GitHub’s own pages print three different dates for the postponement, and the table keeps them as printed rather than choosing one.
| Date | What happened | Where GitHub says it |
|---|---|---|
| 16 December 2025 | GitHub announces a $0.002 per minute “Actions cloud platform charge”, to apply to self-hosted runner usage in private repositories from 1 March 2026. Public repositories and GitHub Enterprise Server are excluded. Hosted-runner rates are cut by up to 39 per cent from 1 January 2026. | Changelog and Insights page |
| 15 December 2025 (as printed) | The TLDR and update at the top of GitHub’s Insights page, dated 15 December 2025, a day before the announcement it updates: “We’re postponing the announced billing change for self-hosted GitHub Actions to take time to re-evaluate our approach.” | Insights page |
| 19 December 2025 | GitHub’s reply on its roadmap item for the charge says the same, and the item is closed as not planned. No new date is given. | Roadmap item 1197 |
| 1 January 2026 | The hosted-runner cut takes effect. It was never postponed. | Changelog and Insights page |
| 1 March 2026 | The start date GitHub had announced. The change was postponed before then, and no new date has been given. | Insights page and roadmap item 1197 |
| When this post was last checked | The billing page still lists self-hosted runners among usage that “remains free independently and does not reduce the included compute usage”. The Actions changelog, read by title to 12 November 2026, has no entry about the charge. | Billing page and changelog |
The pages are the changelog post, GitHub’s Insights page (which holds the same announcement and the update), roadmap item 1197 and the Actions billing page. The Actions changelog was read by entry title, so it shows no entry about the charge and does not prove there will never be one.
Which of GitHub’s dates is right?
All three describe the same decision, in the same words, and none is wrong: 15 December is what the Insights page prints over its update, 16 December is the day of the announcement it updates, and 19 December is the day GitHub replied on its roadmap item and closed it. The changelog’s notice carries no date. The start date of 1 March 2026 stayed in the announcement’s text and no longer applies. A bill follows GitHub’s billing page, and when this post was last checked it listed self-hosted runners as free.
Does the charge apply to public repositories or GitHub-hosted runners?
Not to public repositories or to GitHub Enterprise Server: the announcement excluded both. And for GitHub-hosted runners there is nothing to add, because GitHub says its platform charge is “already included into the reduced meter price”. What was postponed is the same charge applied to self-hosted runners. GitHub-hosted rates already carry it. The pricing post has the hosted rates.
What would it have cost?
This describes a plan GitHub postponed, so it is arithmetic, not a bill. At $0.002 a minute, 10,000 self-hosted minutes would be $20.00 and 50,000 would be $100.00. GitHub’s announcement said those minutes would draw on a plan’s included usage at that rate, so the $18 a month included with Team would have covered 9,000 of them. We include the sums only so you can size it if the charge returns, and GitHub has not said it will return in that form.
What does GitHub say it will do instead?
“We have real costs in running the Actions control plane.”
That is the reason GitHub gave for the charge, and it said in the same update that it “missed the mark with this change by not including more of you in our planning”. It added that it had opened a discussion to gather feedback for the Actions roadmap. It gave no replacement plan and no date, so what is left is a postponement, not a cancellation. Treat the charge as possible, and not as scheduled.
How should I plan around it?
Self-hosted minutes cost nothing to GitHub today, which is not the same as costing nothing: you pay for the machines, the engineer time to keep them patched and secure, and the idle hours between jobs. The self-hosted runner cost post works through what that adds up to. If a $0.002 minute would change your decision, run the sum above with your own minutes and look at the same two pages each month, because they are where a change would appear first: the billing page for what is listed as free, and the runner pricing page for a rate. We read them again every month and move the dates in this post when we do. The next reading is due on 17 December 2026. Our self-hosted runner alternative page sets out the other way: the same runs-on line, and no machines of your own to patch or scale.
For the rest of what has changed in Actions pricing, the dated log lists each change with its date, and the calculator prices a month of hosted minutes.
Sources
- Update to GitHub Actions pricing (GitHub changelog, 16 December 2025) (github.blog)
- Pricing changes for GitHub Actions (GitHub Insights) (github.com)
- GitHub Actions new pricing: self-hosted runner price increase (GitHub roadmap) (github.com)
- GitHub Actions billing (docs.github.com)
- Actions runner pricing (docs.github.com)
- GitHub changelog, Actions label (github.blog)
Frequently asked questions
Does GitHub charge for self-hosted runners?
Not today. GitHub's billing page lists self-hosted runners as free usage that does not reduce included compute. GitHub announced a $0.002 per minute charge from 1 March 2026 and postponed it, with no new date.
When was the self-hosted runner fee going to start, and who would it have hit?
From 1 March 2026, on self-hosted runner usage in private repositories. Public repositories and GitHub Enterprise Server were excluded, and the minutes would have drawn on a plan's included usage at list price.
Has GitHub said when the self-hosted charge will return?
No. GitHub's update says it is postponing the change to take time to re-evaluate its approach, and gives no date. Its roadmap item closed as not planned on 19 December 2025, and its Actions changelog to 12 November 2026 has no later entry.
Do GitHub-hosted runners include the $0.002 platform charge?
Yes. GitHub says the new Actions cloud platform charge is already included in the reduced hosted-runner rates, so a standard 2-core Linux minute at $0.006 has nothing added to it. What was postponed is the same charge on self-hosted runners.