Hello everyone, we've heard your feedback and just shared an update on the announcement. Be sure to check out our latest blog post and have a chance to share your feedback in our community discussion here.

Hi,

From GitHub’s current pricing model, self-hosted runners are generally still different from GitHub-hosted runners because you are providing and maintaining the infrastructure yourself.

For most plans, GitHub-hosted runners consume included Actions minutes and may incur charges after the included quota is exceeded. Self-hosted runners historically did not consume those hosted compute minutes because GitHub is not providing the compute resources.

However, the recent pricing and platform changes have created some confusion because GitHub has started separating billing categories such as:
• hosted runner compute
• larger runners
• storage/artifacts
• logs
• enterprise-level usage features

For GitHub Enterprise specifically, you still receive included GitHub-hosted runner minutes depending on the plan, but self-hosted runner behavior may depend on which additional enterprise features or managed runner capabilities are enabled.

The important distinction is:
• self-hosted runner compute itself is typically not billed the same way as GitHub-hosted compute
• but surrounding platform services or enterprise-managed features may now have associated pricing

I would strongly recommend reviewing:
https://docs.github.com/en/billing/managing-billing-for-your-products/managing-billing-for-github-actions

and:

https://github.com/pricing

as well as checking whether the pricing email specifically references:
• larger runners
• managed runners
• Actions storage
• enterprise orchestration features
• or standard self-hosted runners

For your personal self-hosted runner at home, my understanding is that simply running workloads on your own hardware should still not behave the same way as consuming GitHub-hosted compute minutes. However, because the pricing changes are evolving, opening a support ticket for official clarification is probably the safest option before communicating internally.

Support:
https://support.github.com/

This is definitely an area where GitHub could communicate the distinctions more clearly because many users interpret “Actions pricing changes” as meaning all self-hosted execution is now billable.