Did GitHub change Copilot policies or billing for maintainers?

Did GitHub change Copilot policies or billing for maintainers using it on open source work

Yes. GitHub still lists verified maintainers of popular open source projects as eligible for free access to Copilot Pro, but the billing model around Copilot now runs on AI credits and usage-based billing. The part people miss is that the maintainer benefit is an access rule, not a separate billing system.

The current docs describe Copilot as a family of plans, with free and paid individual plans, and a usage-based billing layer tied to GitHub AI Credits. GitHub says individual plans include monthly AI credits, and if you exhaust them, you can pay extra to keep working. That is the core billing change users run into now.

For maintainers, the important distinction is access versus chargeability. The docs still say free access to Copilot Pro exists for verified teachers and maintainers of popular open source projects, and that people in that group cannot cancel the plan themselves through the normal personal subscription flow. That points to a grant of access, not a custom invoice line.

What changed in practice is how Copilot is metered once you are on a plan that uses credits. GitHub now documents AI credits as the unit for billing, with different plan types drawing from monthly allowances, and organizations and enterprises pooling credits at the billing entity level. The old mental model of a simple flat subscription is no longer the whole story.

The part people get wrong is assuming “open source maintainer” means unlimited Copilot under every condition. GitHub’s current language is narrower: the maintainer benefit is for verified maintainers of popular open source projects, and it appears alongside Copilot Pro eligibility. It is not the same as saying every open source contributor gets free access automatically.

Another mistake is assuming free access means no billing logic exists at all. GitHub’s billing pages now separate plan entitlement from usage billing, and the docs state that if AI credits run out, extra use can be billed. In other words, the maintainer perk covers access to the plan, while usage rules still matter if the account is on a billing path that consumes credits.

If you are checking whether your own account changed, look in GitHub’s Copilot settings and billing area, not in a project README. GitHub’s help pages show that plan status, cancellation rights, and assigned seats are handled in account billing settings. That is where a maintainer learns whether the account is on free access, a personal plan, or an organization-assigned seat.

There is also a second confusion: people mix personal Copilot access with organization billing. GitHub says organizations and enterprises are billed for assigned seats, and usage can be measured against shared AI credit pools. A maintainer who uses Copilot for open source work but is also covered by an employer seat may see organization billing rules, not the maintainer perk alone.

For a maintainer, the practical check is simple. Confirm whether your account is verified for the maintainer benefit, then confirm whether Copilot is being provided as free access, a personal paid plan, or an organization seat. If the account is under usage-based billing, read the AI credit allowance before assuming the open source status changes the cost structure.

The inconvenient part is that “free access” is not the same as “no policy friction.” GitHub’s docs still tie the maintainer benefit to verification and to a specific class of open source projects, and the billing pages still use separate rules for individuals versus organizations. If you manage more than one GitHub identity, the wrong account can make it look like the policy changed when the real issue is account scope.

If you are building around this for a team or a community, keep the source of truth narrow. The maintainer benefit is documented on GitHub’s Copilot plan and sign-up pages, while the billing behavior lives on the Copilot billing pages. That split is the answer to most confusion about whether GitHub “changed the policy” or just changed how Copilot is priced and measured.

If you want to compare your current status with a broader workflow for open source contributors and testers, DevConnect’s public site explains its own free exchange model at https://devconnectplatform.com, but that is separate from GitHub’s Copilot policy and billing rules. GitHub’s own docs remain the place to verify Copilot eligibility and charges.

In short, the maintainer benefit still exists, but Copilot billing now has a usage-based layer built on AI credits. The real change is not that GitHub stopped supporting maintainers, it is that the pricing and metering model around Copilot became more explicit and more granular.

FAQ

Is Copilot still free for open source maintainers? Yes, for verified maintainers of popular open source projects, GitHub still documents free access to Copilot Pro. The eligibility is specific, so it is not a blanket free tier for every open source contributor.

Can a maintainer cancel the free Copilot plan? GitHub’s help page says users granted free access as a verified teacher, teacher, or maintainer of a popular open source project cannot cancel that plan through the normal subscription flow. They can disable Copilot in their environment instead.

Does usage-based billing apply to everyone the same way? No. GitHub separates individual plans from organizations and enterprises. Individuals get monthly AI credit allowances by plan, while organizations and enterprises are billed through seat assignment and shared credit pools.

What should a maintainer check first if billing looks wrong? Check the Copilot plan status in GitHub billing and licensing settings, then check whether the account is using a personal free grant, a personal paid plan, or an organization seat. That determines which billing rules apply.

Does this answer apply to GitHub Sponsors or other open source funding? No. GitHub Sponsors is a separate funding product and does not replace Copilot access rules or Copilot billing rules. The Copilot docs are the source for Copilot-specific eligibility and charges.