The Three Models
GitHub Sponsors, launched in 2019, sits inside the platform where most open-source code already lives. Maintainers link a funding profile to their repository and receive direct contributions from individuals or companies; GitHub originally waived its fee entirely, absorbing payment-processing costs to prime the market. The frictionlessness is the pitch: a developer already watching a repository is one click from supporting it. The weakness is the same — individual sponsorships are small, voluntary, and easy to cancel. GitHub's own data shows a handful of maintainers earning meaningful income, and a long tail earning almost nothing.
Open Collective operates on a different premise: radical fiscal transparency. Every transaction — incoming donation, outgoing expense — is public by default, and funds sit with a fiscal host rather than a personal bank account. Projects including curl and core-js have used it to accept institutional money they could not otherwise process as unincorporated collectives. The model demands ongoing governance effort, and the public ledger that builds trust also exposes every slow quarter. Open Collective the company has faced its own financial turbulence; in 2023 it underwent significant restructuring after its revenue model proved insufficient.
Tidelift takes the most explicitly commercial approach. It sells subscriptions to enterprises — the argument being that companies already depend on hundreds of open-source libraries and should pay for the assurance that those libraries are maintained, patched, and accompanied by signed metadata. Maintainers who join a Tidelift subscription agreement commit to specific security and maintenance tasks in exchange for a recurring monthly payment. The ceiling is higher than a typical sponsorship, but the enrolment burden is real, and the platform's coverage concentrates on widely used libraries rather than niche infrastructure.

What the Comparison Reveals
None of the three platforms addresses the structural problem directly: the organisations that extract the most value from open-source infrastructure — large cloud providers, enterprises — are not the ones funding it at any proportionate scale. GitHub Sponsors captures generosity; Open Collective captures institutional goodwill; Tidelift captures procurement budgets. All three are real money for some maintainers and nearly invisible to others.
The Open Source Initiative's ongoing work on sustainability frames the gap as a governance problem as much as a revenue problem: the licence terms that make software free to use also make payment entirely optional. Platforms can route money when someone chooses to pay; they cannot compel it. Filling that gap is the work the Sovereign Tech Fund and similar public-funding instruments are attempting — with mandates that private platforms structurally cannot carry.