Pricing changes for GitHub Actions · GitHub
Skip to content You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert We’ve read your posts and heard your feedback. We’re postponing the announced billing change for self-hosted GitHub Actions to take time to re-evaluate our approach.
We are continuing to reduce hosted-runners prices by up to 39% on January 1, 2026. We have real costs in running the Actions control plane. We are also making investments into self-hosted runners so they work at scale in customer environments, particularly for complex enterprise scenarios. While this context matters, we missed the mark with this change by not including more of you in our planning. We need to improve GitHub Actions.
We’re taking more time to meet and listen closely to developers, customers, and partners to start. We’ve also opened a discussion to collect more direct feedback and will use that feedback to inform the GitHub Actions roadmap. We’re working hard to earn your trust through consistent delivery across GitHub Actions and the entire platform. Below is the original announcement from 12/16/25 We’re announcing updates to our pricing and product models for GitHub Actions.
Historically, self-hosted runner customers were able to leverage much of GitHub Actions’ infrastructure and services at no cost. This meant that the cost of maintaining and evolving these essential services was largely being subsidized by the prices set for GitHub-hosted runners. By updating our pricing, we’re aligning costs more closely with usage and the value delivered to every Actions user, while fueling further innovation and investment across the platform.
The vast majority of users, especially individuals and small teams, will see no price increase. We will have a GitHub Actions pricing calculator available where you will know how much you will be charged. You can see the Actions pricing calculator to estimate your future costs. 96% of customers will see no change to their bill. Of the 4% of Actions users impacted by this change, 85% of this cohort will see their Actions bill decrease and the remaining 15% who are impacted across all face a median increase around $13.
GitHub Actions will remain free for public repositories. In 2025, we saw developers use 11.5 billion total Actions minutes in public projects for free (~$184 million) and we will continue to invest in Actions to provide a fast, reliable, and predictable experience for our users. Background When we shipped Actions in 2018, we had no idea how popular it would become. By early 2024, the platform was running about 23 million jobs per day and our existing architecture couldn’t reliably support our growth curve.
In order to increase feature velocity, we first needed to improve reliability and modernize the legacy frameworks that supported GitHub Actions. Our solution was to re-architect the core backend services powering GitHub Actions jobs and runners with the goals of improving uptime and resilience against infrastructure issues, enhancing performance, reducing internal throttles, and leveraging GitHub’s broader platform investments and developer experience improvements.
This work is paying off by helping us handle our current scale, even as we work through the last pieces of stabilizing our new platform. Since August, all GitHub Actions jobs have run on our new architecture, which handles 71 million jobs per day (over 3x from where we started). Individual enterprises are able to start 7x more jobs per minute than our previous architecture could support. As with any product, our goal at GitHub has been to meet customer needs while providing enterprises with flexibility and transparency.
This change better supports a world where CI/CD must be faster and more reliable, better caching, more workflow flexibility, rock-solid reliability, and strengthens the core experience while positioning GitHub Actions to power GitHub’s open, secure platform for agentic workloads. What’s changing? Lower prices for GitHub-hosted runners Starting today, we’re charging fairly for Actions across the board which reduces the price of GItHub Hosted Runners and the price the average GitHub customer pays.
And we’re reducing the net cost of GitHub-hosted runners by up to 39% , depending on which machine type is used. This reduction is driven by a ~40% price reduction across all runner sizes, paired with the addition of a new $0.002 per-minute GitHub Actions cloud platform charge. For GitHub-hosted runners, the new Actions cloud platform charge is already included into the reduced meter price. Standard GitHub-hosted or self-hosted runner usage on public repositories will remain free .
GitHub Enterprise Server pricing is not impacted by this change. The price reduction you will see in your account depends on the types of machines that you use most frequently – smaller runners will have a smaller relative price reduction, larger runners will see a larger relative reduction. This price reduction makes high-performance compute more accessible for both high-volume CI workloads and the agent jobs that rely on fast, secure execution environments.
For full pricing update details, see the updated Actions runner prices in our documentation . This price change will go into effect on January 1, 2026 . Introduction of the GitHub Actions cloud platform charge We are introducing a $0.002 per-minute Actions cloud platform charge for all Actions workflows across GitHub-hosted and self-hosted runners. The new listed GitHub-runner rates include this charge. This will not impact Actions usage in public repositories or GitHub Enterprise Server customers.
This aligns pricing to match consumption patterns and ensures consistent service quality as usage grows across both hosting modalities. This will impact self-hosted runner pricing starting March 1, 2026. Deepened investment in the Actions self-hosted experience We are increasing our investment into our self-hosted experience to ensure that we can provide autoscaling for scenarios beyond just Linux containers. This will include new approaches to scaling, new platform support, Windows support, and more as we move through the next 12 months.
Here’s a preview of what to expect in the new year: GitHub Scale Set Client This new client provides enterprises with a lightweight Go SDK to build custom autoscaling solutions without the complexity of Kubernetes or reliance on ARC. It integrates seamlessly with existing infrastructure—containers, virtual machines, cloud instances, or bare metal—while managing job queuing, secure configuration, and intelligent scaling logic.
Customers gain a supported path to implement flexible autoscaling, reduce setup friction, and extend GitHub Actions beyond workflows to scenarios such as self-hosted Dependabot and Copilot Coding Agent. Multi-label support We are reintroducing multi-label functionality for both GitHub-hosted larger runners and self-hosted runners, including those managed by Actions Runner Controller (ARC) and the new Scale Set Client.
Actions Runner Controller 0.14.0 This upcoming release introduces major quality-of-life improvements, including refined Helm charts for easier Docker configuration, enhanced logging, updated metrics, and formalized versioning requirements. It also announces the deprecation of legacy ARC, providing a clear migration path to a more reliable and maintainable architecture. Customers benefit from simplified setup, improved observability, and confidence in long-term support, reducing operational friction and improving scalability.
Actions Data Stream The Actions Data Stream will deliver a near real-time, authoritative feed of GitHub Actions workflow and job event data, including metadata such as the version of the action that was executed on any given workflow run. This capability
The rest of this page is on the live site.