
Three independent open-source projects whose public ledgers ran above a thousand a month in 2026 — gpx.studio, Rotorflight and Basis — and the three payers behind them: 1,442 five-euro donors, two radio manufacturers, and one organisation that put a maintainer on a salary and then stopped.
| Project | Public figure (Sep 24, 2026) | Evidence class | Who pays | What the money buys |
|---|---|---|---|---|
| gpx.studio | €16,706 a year, about €1,392 a month; €13,520.85 raised, €4,578.42 disbursed 2 | Collective page plus its public ledger; €1,566–€1,940 a month in receipts since April | 1,442 individuals, mostly €5 at a time | Servers, map tiles, and €83.49 a month to GraphHopper |
| Rotorflight | €16,993 a year, about €1,416 a month; €10,425.94 raised, €996.36 disbursed 11 | Collective page plus its public ledger; €1,140–€2,413 a month since March 2026 | Two radio manufacturers at €500 a month, plus hobbyists | Development radios, test parts, maintainer tooling |
| Basis | $61,660 a year, about $5,138 a month; $57,296.70 raised, $53,612.13 disbursed 16 | Collective page plus its public ledger; $1,075–$2,075 a month since June 2026 | One VR organisation through May 2026, then individuals and small organisations | Ten months of a maintainer's salary, then $1,000 work-period payouts |
| Project archetype | Model this window's evidence supports | What to prove before you copy it |
|---|---|---|
| Consumer web tool | €5 monthly and yearly tiers from individual users, sold in volume | That several hundred people use the free tool repeatedly and can pay without a procurement process |
| Embedded or device firmware | Sponsorship from the vendors whose hardware runs your code | That a seller's product gets worse when you stop, and that a fork would cost more than the sponsorship |
| Framework or SDK | One organisation's sponsorship large enough to cover a maintainer, with a $100 support tier underneath | That the sponsor's own roadmap depends on you, and that the project survives the sponsorship ending |
| Library | Sponsorship from the companies that depend on it, with a paid support path for the largest users | That the payer is the one whose breakage you would cause |
| CLI tool | Paid support or a pro plugin for the people who run it daily, sponsorship for everyone else | That the free tier stays complete and the paid one is a different product rather than a lock |
github.com
opencollective.com
opencollective.com
opencollective.com
opencollective.com
opencollective.com
opencollective.com
opencollective.com
github.com
github.com
opencollective.com
opencollective.com
opencollective.com
opencollective.com
github.com
opencollective.com
opencollective.com
opencollective.com
opencollective.com
opencollective.com
This story was produced automatically by a channel. One sentence is all it takes for Neodrop to keep producing for you.