Who Pays the Electric Bill for the Internet's Free Software?

Here's a thought experiment: imagine if every highway in America was designed, paved, and maintained by unpaid volunteers who just really loved civil engineering. That's basically the situation with open-source software right now. The code that runs hospitals, stock exchanges, and your favorite streaming app was largely built by people who weren't getting a paycheck for it—and in a lot of cases, still aren't.

"Free" as in freedom, the old saying goes, not free as in lunch. But somewhere along the way, the tech industry quietly decided it meant both.

The Real Price Tag Nobody Talks About

Maintaining a popular open-source project isn't a hobby. It's a job—often a brutal one. Let's break down what it actually costs to keep something like a widely-used JavaScript library or a security-critical encryption tool running properly.

Server infrastructure alone can run thousands of dollars a month for projects with heavy usage or continuous integration pipelines. Security audits—which any responsible project handling sensitive data absolutely needs—can cost anywhere from $10,000 to $100,000 depending on scope. Then there's documentation, which sounds boring until you realize that bad docs are why developers abandon tools and why bugs go unfixed. Community management, issue triage, release coordination, responding to CVEs at 2 a.m. on a Tuesday—none of this is free, and none of it magically happens on its own.

The Log4Shell vulnerability in 2021 was a brutal wake-up call. A critical security flaw in a logging library maintained largely by volunteers was embedded in billions of devices worldwide. The people responsible for fixing it had no dedicated funding, no incident response team, and no paid time off to deal with the chaos that followed. They just... dealt with it. Because someone had to.

The Funding Gap Is Real, But It's Closing

The good news? A genuine ecosystem of sustainable funding models has started to take root, and some of them are actually working.

GitHub Sponsors launched in 2019 and has quietly become one of the most accessible on-ramps for individual maintainers to receive direct financial support. It's not perfect—discoverability is limited and most maintainers earn modest amounts—but it normalized the idea that clicking a "Sponsor" button on a repo is a reasonable thing to do. Some maintainers are pulling in several thousand dollars a month through it, which at least covers hosting and buys back a few hours of their time.

Open Collective operates on a more transparent, community-first model. Projects create a public collective where donations and expenses are visible to everyone—no black box finances, no wondering where the money went. Webpack, the JavaScript bundler that's essentially invisible infrastructure for millions of web apps, raised over $1 million through Open Collective over several years. That money paid for dedicated maintenance time, documentation rewrites, and a more sustainable release cadence.

Corporate sponsorship is the bigger lever, though it comes with complicated dynamics. When companies like Google, Microsoft, and Amazon sponsor open-source projects through foundations like the Linux Foundation or the OpenSSF, it can mean real resources—but it also raises questions about influence and independence. The key distinction is whether a company is funding maintenance of something it uses, or funding development of something it wants.

Projects Getting It Right

Curl is a good case study. The command-line tool for transferring data with URLs is installed on something like 20 billion devices. Its primary maintainer, Daniel Stenberg, ran it largely as a passion project for decades. In recent years, corporate sponsors have come on board specifically because companies realized how catastrophic it would be if curl went unmaintained. The project now has formal sponsorship tiers and Stenberg has been able to dedicate professional time to it—without compromising the project's independence or its open-source licensing.

Ruby Together is another model worth studying. It's a nonprofit trade association that pools membership dues from companies using Ruby and Ruby on Rails infrastructure, then pays developers to maintain shared tools like Bundler and RubyGems. The framing is elegant: instead of asking for charity, it positions funding as dues for a shared resource that everyone benefits from. Companies respond better to that framing than to donation requests.

The Astropy project, used extensively in scientific research, built a tiered sponsorship model through a combination of grants, institutional partnerships, and community fundraising. Critically, they published a detailed sustainability report showing exactly where money went and what it enabled. Transparency became a trust-building tool that actually drove more funding.

What the Community Can Do Right Now

If you're a developer, designer, or anyone who uses open-source tools professionally—which is basically everyone in tech—there are concrete things you can do today.

First, audit your dependencies. Most projects have a FUNDING.yml or a link to their Open Collective page. Spend ten minutes understanding who maintains the tools your work depends on. Second, bring the conversation to your employer. Many companies have open-source budgets they're not fully utilizing, or could be persuaded to start one. Framing it as risk management rather than charity tends to land better in budget meetings. Third, if you're a maintainer yourself, consider setting up a public funding page and being explicit about what funding enables—not as a guilt trip, but as honest communication about sustainability.

The open-source commons is one of the most remarkable collaborative achievements in human history. It's also one of the most chronically underfunded. The models to fix that exist. They're working. They just need more people—individuals, companies, and institutions—to actually use them.

The electric bill doesn't pay itself. But for the first time in a while, more people are reaching for their wallets.