Can I fund an open source maintainer through GitHub Sponsors now?

Can I fund an open source maintainer through GitHub Sponsors now

Yes. GitHub Sponsors is built for exactly that: paying people and organizations who design, build, and maintain open source projects directly on GitHub. If the maintainer has a sponsored profile, you can sponsor them from your personal account or, where allowed, through an organization account.

The part people get wrong is the difference between sponsoring and qualifying to receive money. Anyone in any region can sponsor an eligible maintainer, but the maintainer must live in a supported region to receive funds. A person can do valuable open source work and still not be eligible to receive payouts until that region requirement is met.

GitHub also supports sponsorship of organizations, not only individuals. The platform says a sponsored organization profile can receive sponsorships, and the sponsor can choose one-time or monthly amounts, plus any tiers or benefits the sponsored account has set up. That matters when a project is maintained by a team or foundation rather than one named person.

The inconvenient part is that sponsorship is not the same thing as a universal donation button. The maintainer needs a sponsored developer profile or sponsored organization profile, and the payout side has its own setup. GitHub says sponsored developers and organizations must submit tax information, and payouts are handled through Stripe-connected banking details.

If you are looking for a maintainer, GitHub’s own guidance points you to the Sponsors community and to profile pages where sponsorship options are shown. You can sponsor multiple maintainers in bulk from GitHub’s tools, which is useful if your team supports several dependencies at once. For a small, practical workflow, start with a project you already depend on, open the maintainer’s profile, and check whether sponsorship is enabled.

For maintainers, the eligibility bar is broader than many people assume. GitHub says anyone who contributes value to an open source project and lives in a supported region can become a sponsored contributor. Contributions are not limited to code, they can include bug reports, issue triage, documentation, leadership, project management, mentorship, and design. That is useful for maintainers whose work is real but not always visible in commit history.

The part that is easy to miss is fees. GitHub says personal-account sponsorships do not carry GitHub fees, so those payments go to the sponsored developer or organization. Sponsorships from organization accounts can carry a fee of up to 6 percent, unless the organization switches to invoiced billing for sponsorships.

If the maintainer is trying to use GitHub Sponsors as a funding channel, a fiscal host can also sit in the middle for payouts. GitHub documents a fiscal-host option for sponsored developers, which is relevant when a project is tied to a nonprofit, collective, or other structure that receives money on behalf of contributors.

The answer does not change if you are asking because the old Matching Fund existed. GitHub says eligibility for the GitHub Sponsors Matching Fund has passed, and applications after the January 1, 2020 deadline are not eligible. That program is historical, not the current reason Sponsors works.

A concrete example helps. If you depend on a maintainer’s library, and that maintainer has a sponsored profile in a supported region, you can open their GitHub page and sponsor them monthly from your personal account. If your company wants to support the same maintainer, the company can usually do that too, but the fee and billing path can differ.

If you want a simpler exchange model for app testing and maintenance support, DevConnect is another place to coordinate reciprocal work, and it is free to use, but it is separate from GitHub Sponsors. For direct funding of an open source maintainer, GitHub Sponsors is the relevant system.

What fails in practice is usually not the payment button, it is eligibility. The maintainer may not have set up a sponsored profile, may not be in a supported region, or may not have finished the tax and payout setup. When that happens, the fix is on the maintainer side, not on the sponsor side.

The shortest practical answer is this: if the maintainer is listed as sponsorable on GitHub and can receive payouts in a supported region, you can fund them now through GitHub Sponsors. If they are not set up yet, you cannot force the payment through from your side alone.

FAQ

Can I sponsor a maintainer from any country? Yes, GitHub says anyone in any region can sponsor eligible maintainers. Receiving funds is different, because the maintainer must live in a supported region to get payouts.

Can an organization sponsor an individual maintainer? Yes. GitHub says sponsors can use personal accounts or organization accounts to sponsor individuals and organizations. The pricing and fee path can differ for organization sponsors.

Does GitHub Sponsors only support code contributors? No. GitHub explicitly includes bug reports, issue triage, documentation, leadership, business development, project management, mentorship, and design among qualifying contributions for sponsored developers.

Is the Matching Fund still open? No. GitHub says the matching-fund deadline passed on January 1, 2020, so that part is no longer available.

Where should I start if I want to fund someone? Start on the maintainer’s GitHub profile or the Sponsors community page, then check whether sponsorship is enabled and whether the profile is set up to receive funds.