You’ve watched your favorite open source project slowly morph into something unrecognizable. The README now features three corporate logos. The maintainers used to argue about architecture on weekends; now they argue about quarterly deliverables in Slack channels. And somewhere deep in a private repo, a funding round just closed that you’ll never see the terms of.
Here’s the uncomfortable truth nobody wants to say aloud: the more money flows into open source, the faster it loses its soul. Not because money is evil — but because every dollar comes with invisible strings that reshape who decides what gets built, who gets credit, and who gets burned out quietly in the corner.
I spent months talking to maintainers of projects you rely on every day — from authentication libraries to build tools to entire operating systems. And what I heard wasn’t a story about scarcity. It was a story about a slow, quiet heist disguised as generosity.
Let me show you how the trap works.
Funding is not the problem. The structure of funding is the problem.
We’ve been told that open source is a funding crisis. That creators can’t eat. That we need more enlightened corporations to step in. So we watch as Vercel throws millions at Next.js. As Microsoft hires React core team members. As Google pays the maintainers of libraries that underpin the entire web. And we cheer. “Look, they’re finally getting paid!”
But here’s the twist nobody talks about: every time a maintainer becomes an employee, the community loses a voice. Not immediately. Not dramatically. But a month later, that maintainer’s GitHub issues are prioritized differently. Their blog posts read more like PR. Their commits now have a subtle bias toward what makes their employer look good.
I’ve seen this happen in real time. A well-known Vue plugin maintainer accepted a sponsorship from a competing framework’s parent company. Suddenly, the plugin’s compatibility with that framework mysteriously improved. No malice — just human nature. Money changes incentives, and incentives change behavior, and behavior changes the ecosystem.
And it’s not just hiring. It’s the rise of “sponsored development” — where corporations pay for features they need. The community wants bug fixes and stability. The sponsor wants a shiny new integration. Guess which gets the green light? When you let money dictate the roadmap, the community becomes a passenger in its own project.
This is the quiet crisis that funding debates ignore. They ask “How do we get more money?” But they should ask “How do we get money without giving away the keys?”
There’s a better way, and it’s not utopian. It already works in a few places. The Open Collective model — where funding goes to a neutral entity, and the community votes on priorities. The GitHub Sponsors model where individuals donate directly, zero strings attached. The contract-based model where maintainers are paid for specific work but keep full control of the project governance. These aren’t perfect, but they share one critical trait: the money serves the community, not the other way around.
Meanwhile, most open source funding today is a a one-way street from community trust to corporate profit. The investors get influence. The maintainers get a salary — and a leash. And the users? They get a slower, more complex, more corporate version of the tool they loved.
So what do we do? First, stop glorifying the latest funding round. Second, demand transparency: every project you depend on should have a public governance document that explicitly states who owns the roadmap. Third, support small, decentralized funding mechanisms — Patreon, Open Collective, direct donations — over corporate sponsorships. The best money is the money that expects nothing in return.
Open source was built on a radical idea: that contributions should be judged on merit, not on who pays the bills. That idea is under siege. And the enemy isn’t a shortage of dollars — it’s a shortage of courage. Courage to say “no thanks” to the wrong kind of money.
We don’t need more funding. We need more freedom.
FAQ
Q: Is all corporate funding bad for open source?
A: No, but most current models are. The problem is when funding comes with strings attached — like hiring maintainers, dictating roadmap priorities, or requiring exclusive features. Good corporate funding is unconditional: it supports the project as a whole, not the corporation's specific interests.
Q: What should I do as an open source maintainer?
A: First, write a clear governance document that separates funding from decision-making. Second, diversify your funding sources — don't rely on a single corporation. Third, reject any sponsorship that demands influence over which issues you prioritize or which features you build. Your community is your real boss.
Q: But isn't it better to have paid maintainers than unpaid ones?
A: Paying maintainers is good — but only when the payment structure preserves their autonomy. An unpaid maintainer with full control is healthier for the ecosystem than a well-paid maintainer who answers to a corporate manager. The goal should be sustainable independence, not salaried dependence.