Open source isn’t a tip jar – it’s time to charge for access

Summary

Steven J. Vaughan‑Nichols argues that the prevailing model of relying on donations and goodwill to sustain open source is broken. Large tech companies that derive huge value from open source contribute token grants but avoid covering the real operational costs. Many maintainers are unpaid or severely underpaid, with burnout and attrition rising. Critical infrastructure such as package registries (Maven Central, PyPI, npm, crates.io) bears enormous traffic — primarily from big cloud providers — yet runs on minimal funding. The piece contends commercial users should be charged for heavy access (the code remains free) and calls for a new organisation or funded mechanism to channel predictable, fair payments from businesses to maintainers.

Key Points

Big tech donations to open source (e.g. a recent $12.5m round) are tiny relative to their market value and the scale of their usage.
A large share of open source maintainers are unpaid; many have quit or considered quitting due to burnout and lack of compensation.
Package registries handle trillions of downloads; most traffic comes from a small number of large commercial users, creating outsized costs for public infrastructure.
AI‑driven low‑quality security reports and bug submissions impose significant triage burden on maintainers, damaging mental health and sustainability.
Some targeted funds (HeroDevs, Sentry’s Open Source Pledge) show how direct payments can help, but a systematic, industry‑wide funding model is needed.
The article proposes treating payments to maintainers as a cost of doing business and creating an organisation to route funds from commercial users to project maintainers.

Context and relevance

Open source underpins virtually all modern software: audits show over 97% of commercial projects rely on open source components. Yet many widely used projects show little sign of active maintenance. As cloud providers and AI tooling increase demand on registries and maintainers, the mismatch between commercial benefit and community funding grows. This debate matters if you build, ship, or run software that depends on open source — because the sustainability of that software stack affects supply chain risk, security, uptime, and long‑term costs.

Why should I read this?

Look — if your apps, CI pipelines or cloud builds ping npm, PyPI or Maven every five minutes, you’re freeloading on someone else’s time. This piece cuts through the hand‑wringing and says: stop pretending charity scales. Read it if you want to understand why companies will soon face real bills for heavy access, why maintainers are burning out, and what a workable fix might look like. Short version: it affects your builds, your risk, and your wallet.

Author style

Punchy: the writer is blunt and impatient with token charity. If you care about the health of the open source ecosystem, the tone amplifies the urgency — it’s more demand than suggestion: fix funding now or expect breakage in widely relied upon components.

Source

Source: https://go.theregister.com/feed/www.theregister.com/2026/03/25/open_source_bill_opinion/