GitHub Code Quality Goes Paid July 20: See Your Bill Before It Hits

GitHub has added a license cost estimator for Code Quality, its static analysis and CodeQL-powered tool, ahead of its paid launch on July 20, 2026. Enterprise admins can now visit their Billing and Licensing page to see how many active committers are using Code Quality across their organizations and get a projected monthly cost. The feature is still free during public preview, but the estimate is there specifically so teams can decide whether to keep it enabled before billing starts.

What happened

Detail	Fact
Paid launch date	July 20, 2026
Price	$10 per active committer per month
Estimate location	Billing entity > Billing and Licensing > Licensing > Code Quality card
Available on	GitHub Enterprise Cloud, GitHub Team
Not available on	GitHub Enterprise Server
Current cost	Free during public preview

GitHub has quietly moved Code Quality, the platform’s static analysis suite built around CodeQL, toward a paid tier. The new estimator shows enterprise admins their current active committer count and what that translates to in monthly charges. Nothing is billed today, but the clock is ticking toward July 20.

What does the estimate actually include?

The number shown on the Code Quality card reflects only the per-committer license fee. It does not cover two other costs that can add up quickly:

• GitHub Actions minutes consumed by CodeQL analysis jobs.
• Usage-based charges for AI-powered features such as GitHub Copilot Autofix.

The estimate also uses standard list pricing. Any negotiated discounts your enterprise has in place will not appear in the preview figure, so your real bill could be lower.

Why it matters

For smaller engineering teams, $10 per active committer per month may be negligible. For a 50-person team all pushing code regularly, that is $500 a month before Actions minutes and Copilot Autofix. Larger enterprises could be looking at meaningful recurring spend that was not in last year’s budget.

The word “active committer” is doing a lot of work here. GitHub defines it based on who is committing to repositories with Code Quality enabled, so teams that have enabled it broadly across many repos could have a higher committer count than expected. Checking the estimate now, before July 20, is the only way to avoid a billing surprise.

This also signals a broader shift in GitHub’s pricing strategy. Features that were bundled or free during preview are increasingly moving to per-seat or usage-based charges, similar to how Copilot billing evolved. Teams that rely on multiple GitHub-native tools should expect this pattern to continue. If you are exploring how AI-assisted development tools fit into your workflow, our notes on Microsoft’s study on AI coding agents and pull request volume are worth a read alongside this pricing change.

Our take

GitHub giving teams a preview of their bill before flipping the switch is genuinely useful. Most SaaS vendors just send the invoice. The caveat is that the estimate is incomplete: it leaves out Actions minutes and Copilot Autofix costs, which could be substantial for teams running deep scans on large codebases. Do not treat the card number as your total Code Quality spend.

If you manage a GitHub Enterprise Cloud account, the action is simple: check the estimate this week and audit which organisations actually have Code Quality enabled. Disabling it on repos where nobody is acting on the findings is a fast way to reduce the committer count before billing starts. For teams building on GitHub and wanting to keep tool costs predictable, pairing this audit with a broader web development services review can surface other areas where tooling spend has crept up.

What to do about it

1. Log in as an enterprise admin and navigate to your billing entity’s Billing and Licensing page.
2. Open the Licensing section and find the Code Quality card.
3. Note the active committer count and the estimated monthly payment.
4. Identify organisations or repositories with Code Quality enabled where the findings are not being reviewed or actioned.
5. Disable Code Quality on those repos before July 20 to reduce your billed committer count.
6. Factor in GitHub Actions minutes and any Copilot Autofix usage separately when building your final budget figure.

Check your estimate before July 20. Disabling unused Code Quality repos now is the one lever you have to reduce that first bill.

Source: GitHub Changelog