Who Pays the Maintainers?

There’s a scene that keeps playing out in tech circles right now: half the world switches to remote work almost overnight, and the software holding that transition together turns out to be free. Not free-as-in-marketing-gimmick, but literally maintained by volunteers, often in their spare time, often for years, often for nothing.

That’s not a new observation. People have been pointing at the xkcd comic — the one with the massive dependency tower balanced on a single block labeled “a project some random person in Nebraska has been thanklessly maintaining since 2003” — for years. But the pandemic has given it new teeth. Companies that never thought twice about which packages sat in their node_modules or requirements.txt are suddenly very aware that their entire remote-work infrastructure runs on tools built by people who aren’t on anyone’s payroll for that work.

The funding problem isn’t new, but the attention might be

GitHub Sponsors has been around since 2019, and Patreon, Open Collective, and Tidelift have been chipping away at this problem for longer. What’s different this month is the framing. When your video conferencing stack, your CI pipeline, your text editor, and half your backend libraries are open source, and all of them depend on a chain of maintainers who might burn out or walk away at any point, “who pays for this” stops being an abstract governance question and starts being a business continuity question.

I don’t think there’s a single fix here. Sponsorship platforms help, but they tend to reward projects that are already popular or that have a maintainer skilled at self-promotion — not necessarily the ones doing the most critical, least glamorous work. A tiny parsing library that half the internet depends on transitively might never get a single sponsor, while a flashy new framework with a slick landing page racks up recurring donations.

What I’d like to see more companies do is treat open-source dependency funding the way they treat SaaS renewals: an actual line item, reviewed periodically, tied to what you actually use in production. Some companies already do this quietly. Most don’t. The incentive structure just isn’t there yet — it’s much easier to consume a dependency for free than to go through a procurement process to pay someone who isn’t asking for money.

None of this is a knock on GitHub Sponsors itself. Making it easy to send a maintainer $10 or $500 a month, directly from the platform where the code already lives, lowers the friction enough that it might actually change behavior over time. Whether it changes it enough to matter for burnout-prone maintainers is a different question, and one I don’t think anyone can answer yet.

For now, if you or your company depends on open-source tools you didn’t write and don’t fund, this seems like as good a moment as any to go check the sponsor button. Small gesture, but it’s not nothing.