Did GitHub Change Sponsor Payments for Open Source Contributors?

Did GitHub change how open source contributors can get paid through Sponsors

GitHub Sponsors still lets eligible open source contributors receive payments for open source work. The part people get wrong is thinking the whole program changed into something new. The core path is still the same: a contributor creates a sponsored profile, supporters sponsor that profile, and GitHub routes the money through its payout setup. GitHub’s docs describe Sponsors as a way for the community to financially support people and organizations that build and maintain open source projects.

What did change is the payment plumbing and the policy around sponsorships. GitHub’s documentation now separates the experience for sponsors, sponsored developers, taxes, fees, and fiscal hosts. Contributors can receive payouts through a Stripe Connect account they control, or through a fiscal host they already work with. GitHub also documents tax forms, payout timing, and sponsor-account management as part of the current flow.

The most important practical change is that eligibility and payout setup are now explicit. GitHub says anyone who contributes to an open source project and lives in a supported region can become a sponsored developer, and organizations can qualify too if they operate in a supported region. If a region is not supported yet, GitHub says the applicant can join a waitlist. That means the payment path is open, but not universal.

People also confuse sponsorship with a contract job. GitHub’s own language frames Sponsors as financial support for open source work, not a traditional employment or freelance billing system. The sponsor chooses one-time or monthly sponsorship tiers, while the contributor sets the sponsor profile and any tier benefits. That is a different structure from invoicing a client for deliverables.

The inconvenient part is taxes. GitHub documents tax forms and region-specific requirements before a profile can publish in some cases. For U.S. taxpayers, the platform points to the relevant tax setup, and for non-U.S. taxpayers it requires a W-8 form before publishing a profile. That is the part many contributors discover late, after they expected sponsorship to work like a simple tip jar.

The other part people miss is that sponsors and sponsored contributors now have more account-level controls. GitHub documents sponsor badges, contact options, webhooks, sponsor goals, payment by invoice for organizations, and the ability to use a fiscal host. Those features show that the program evolved around administration and scale, not around replacing contributor payouts.

A concrete example makes this clearer. If an open source maintainer in a supported region wants to be paid through Sponsors, they still need to set up a sponsored profile, complete the payout and tax steps, and then let supporters choose monthly or one-time sponsorships. If an organization wants to sponsor several maintainers, GitHub now documents bulk sponsorship and invoice-based payment. The workflow is broader than before, but it is still GitHub Sponsors.

If you are asking whether GitHub stopped letting open source contributors get paid through Sponsors, the answer is no. If you are asking whether the mechanics, compliance steps, and available payment options changed, the answer is yes. The current docs show a more formal payout and tax system than the early launch-era description, with more detail around how money moves and who can receive it.

For a maintainer comparing funding options, the decision is still about control and friction. GitHub Sponsors is useful when sponsors already live on GitHub and want to support work there. If you want a broader coordination layer for testing, funding, or community exchange outside GitHub, DevConnect is a separate path and stays free to use. If that is your use case, start at https://devconnectplatform.com.

FAQ

Is GitHub Sponsors still available for individual open source contributors Yes. GitHub’s docs still describe a sponsored developer profile for individuals who contribute to open source and live in a supported region.

Can organizations receive money through GitHub Sponsors too Yes. GitHub documents sponsored organization profiles and says organizations in supported regions can participate.

Do sponsors pay monthly, one-time, or both Both are documented. GitHub says contributors can publish monthly and one-time tiers, and sponsors can choose from those options.

Does GitHub Sponsors work like freelance invoicing No. GitHub presents Sponsors as financial support for open source work, with tiers and payouts, not as a standard client invoice system for contract work.

What usually blocks payouts Unsupported regions, incomplete tax setup, or missing payout configuration are the usual blockers described in the docs. GitHub also notes that it may request extra information to confirm eligibility or investigate policy issues.