GitHub Sponsors just crossed $100 million in total contributions to open source maintainers and projects. I know that’s a big number, but it’s worth pausing to understand what it actually means for those of us building software.
When GitHub Sponsors launched in 2019, the goal was straightforward: make it possible for developers to directly fund the maintainers they depend on. At the time, that felt almost radical. Open source had always been this weird mix of labor of love, side projects, and sometimes corporate-funded work. The idea that individual developers could sustainably earn money from maintaining public projects? That was aspirational.
Seven years later, we’re looking at a funding network supporting over 70,000 maintainers across more than 280,000 sponsors. The acceleration tells the real story: the first $10 million took nearly two years. The most recent $10 million took five months.
The Economics Are Actually Shifting
What strikes me most is how the funding composition has changed. In 2022, nearly 40 percent of sponsorship funding came from organizations, with each org-funded sponsorship worth an average of 15 times more than individual sponsorships. That’s not coincidental. Companies are finally connecting the dots: their entire infrastructure depends on open source, so funding the maintainers of their dependencies isn’t charitable work, it’s risk management.
Shopify, Mercedes-Benz, and other major organizations have realized that sponsoring open source isn’t just about values. It’s practical. If you depend on a project, and that project has a burned-out maintainer who might walk away, then you have a problem. Better to fund them now than deal with an abandoned dependency later.
This is important for developers because it signals a fundamental shift in how the industry values open source work. We’re moving away from the “someone will eventually fix it” model toward actual, sustainable funding. That means more people can treat open source as a real career, not a side hustle squeezed into evenings and weekends.
What This Enables
Listen to what maintainers themselves are saying. One sponsor reflected that GitHub Sponsors “gave me a direct, sustainable way to fund the time it takes to build and maintain projects, instead of treating it like side work.” Another said it allowed them to “quit my job and work on them full time.”
That’s not small. That’s the difference between someone contributing occasionally to their projects and someone who can make deliberate, long-term architectural decisions. Someone who can spend time on documentation, security, and performance instead of just fixing bugs when they get around to it.
For those of us using open source, this is massive. The projects we depend on are getting better maintainers, not more burned out ones. The funding has also enabled sub-sponsorships, where maintainers can fund their own dependencies. It creates a healthier, more interconnected ecosystem.
The Friction Matters Too
GitHub learned something crucial while building this: reducing friction actually works. Every time they made sponsorship easier, funding increased. Invoice payments, expanding to 103 regions, bulk sponsorships, partnerships with platforms like Patreon. These seem like small product decisions, but they matter. They remove the excuses.
I think there’s a lesson there for anyone building developer-facing tools. Developers want to do the right thing. Often, they just need it to be easy. The same person who might not set up individual sponsorships will absolutely approve an org-level sponsorship process if the finance integration works smoothly. Explore more about building tools for developer communities here.
The Real Problem Still Exists
Here’s the thing though: $100 million sounds like a lot until you think about it at scale. The open source funding gap is still enormous. Critical projects remain underfunded. Maintainer burnout is still one of the biggest risks to the software supply chain.
The fact that the last $10 million came faster than the first doesn’t mean the problem is solved. It means awareness is growing, but the need is still vastly larger than the funding. Many essential projects that billions of developers depend on still operate with minimal resources.
What Comes Next
For developers, I think the immediate implication is clear: start sponsoring. If your organization depends on open source, and you almost certainly do, there’s no better time to convert that dependency into investment. Check out the sponsors explore page to discover which maintainers you actually rely on.
For maintainers, this milestone proves there’s real demand to support open source. If you’re not on GitHub Sponsors yet, the community is waiting.
The real question now is whether we can reach $1 billion before another seven years pass, or whether we’ll finally treat open source sustainability as an actual priority in software development.