GitHub Sponsors has now paid out more than $100 million to the people who maintain open source, and the number that stopped me cold is the pace: the first $10 million took nearly two years to raise, while the most recent $10 million took just five months. GitHub laid this out in $100 million for open source: A milestone built by the community, and I want to talk about what it means for someone reading this from Sri Lanka.
Because "someone in the West got rich off open source" is not the story. The story is that the pipe now reaches 103 regions, and the money increasingly comes from companies, not fans.
💰 The money is real, and it's accelerating
The headline numbers are worth sitting with. This isn't a grant program run by one foundation; it's a distributed flood of small and large payments through a single platform launched in 2019.
| Metric | Figure |
|---|---|
| Total contributed via GitHub Sponsors | Over $100 million |
| First $10M raised | Nearly 2 years |
| Most recent $10M raised | 5 months |
| Maintainers & orgs supported | Over 70,000 |
| Total sponsors | More than 280,000 |
| Regions reached | 103 |
An accelerating curve matters more than a big total. A big total is history. An accelerating curve is a forecast, and it says the amount of money looking for open source maintainers to pay is going up every quarter.
Key takeaway: The interesting metric isn't $100 million. It's that the last tenth of it arrived roughly four times faster than the first. Funding open source is becoming normal corporate behaviour, not charity.
🌐 Why "103 regions" is the line that matters here
Most funding stories are useless to a developer in Colombo or Galle because the money never crosses the border. Payoneer this, Stripe-not-supported that. GitHub Sponsors reaching 103 regions is the part I'd underline for a Sri Lankan reader, because it means the payout rail is one of the few that plausibly reaches you.
That reframes open source from "free work I do for a portfolio" into "unpaid work that has a real, if uncertain, revenue path." Those are very different decisions.
- A student maintaining a small library gets a public, verifiable track record and a tip jar attached to it.
- A freelancer can point clients at sponsored projects as proof of standing, not just a CV bullet.
- A small team can fund the one dependency that keeps breaking instead of forking it at 2am.
If you're already publishing code on GitHub for free, you are one profile toggle away from being able to receive money for it. The gap is administrative, not technical.
When that USD does land, the boring next question is what it's worth at home. That's a currency-conversion and fee problem, and it's exactly what our freelancer USD-to-LKR calculator exists to answer before you get surprised by the transfer cut.
🏢 Companies now write the big cheques
Here's the shift I think matters most strategically. GitHub made organization-funded sponsorships generally available in 2023, and the effect on the mix is large.
| Source | What the data shows |
|---|---|
| Organizations' share of funding (2022) | Nearly 40% |
| Org sponsorship vs individual sponsorship | Organizations pay roughly 15x the individual average |
| Enabling features | Bulk sponsorships, invoice payments, a Patreon partnership |
Individuals tipping five dollars is lovely and it will not pay your rent. A company that needs your library not to break, and can process an invoice and expense it, is a different animal. It pays in multiples and it pays predictably.
The practical read: if you want sponsorship income to be more than pocket money, build or maintain something a business depends on. Boring infrastructure beats flashy demos. A logging shim that a hundred companies quietly import is worth more, financially, than a viral toy.
🛠️ What actually earns money (from who says it worked)
GitHub's post names maintainers who turned this into real income, and the pattern in their own words is consistent. Caleb Porzio, who maintains Livewire and Alpine.js, said sponsorships let him quit his job and work on them full time. Sebastián Ramírez (tiangolo, of FastAPI fame) used it to support the tools his own work depends on.
The common thread isn't luck. It's maintaining something other developers reach for daily.
- Solve a real, recurring pain. The tools that get funded remove friction from other people's builds.
- Maintain it visibly. Merge PRs, cut releases, answer issues. Fundability tracks reliability.
-
Make the tip jar obvious. Enable Sponsors, add a
FUNDING.yml, put the button in your README. - Aim at teams, not just stars. A dependency for companies out-earns a project for hobbyists.
You don't need a framework to start. A well-scoped utility — a linter plugin, a config generator, a Sinhala text helper nobody else has built — is a legitimate on-ramp. If you're setting up a new repo today, even our small .gitignore generator removes one bit of friction before your first commit.
Bottom line: Fundable open source is unglamorous and consistent, not clever and abandoned. The maintainers getting paid are the ones who kept showing up.
💡 What this means for you
If you write code in Sri Lanka, treat this milestone as a signal about direction, not a lottery ticket. The pool of money paying maintainers is growing, it's increasingly corporate, and the rail now reaches you. That's three tailwinds at once.
I wouldn't quit anything on the strength of it. What I'd do this week is smaller and safer: enable Sponsors on the projects you already maintain, add a funding file, and pick one recurring problem worth solving well enough that a company would rather pay you than fix it themselves. The first dollar is a proof of concept. The $100 million says the market for the rest of them is real, and getting bigger faster.
One last practical note: sponsorship income is income. When it starts arriving, keep records, because the tax side is real too — our Sri Lanka freelancer tax calculator is the boring companion to the fun part of getting paid to build in the open.
Top comments (0)