There I was, scrolling through yet another discussion about open-source software (OSS), and it hit me: everyone loves free software, but nobody seems to talk about how the folks behind it are supposed to get paid. Open-source software runs the world—your phone, your favorite streaming service, even the servers powering this very article. And yet, the maintainers of these projects? They’re often stuck feeling like the unsung heroes, except there’s no hero’s paycheck waiting for them at the end of the day.
It’s a strange dilemma. Imagine a room full of brilliant developers who pour their time and energy into these crucial projects, keeping the digital world spinning. But instead of getting rewarded, 60% of them are volunteers. They do this for free, without much financial support or even a thank you. You’d think there would be some kind of global fund for people responsible for the tech that everyone depends on, right? Well, not exactly.
Kevin Crosby, one of the higher-ups at GitHub, put it bluntly: we need more access to tech, better training, and, most importantly, corporate funding that supports these projects. In other words, if companies are going to rely on open-source software to keep their million-dollar businesses running, maybe it’s time they pitched in a bit more.
The real kicker? 90% of enterprises rely on open-source software, but only a small fraction are putting their money where their code is. Sure, some companies do employ open-source maintainers, which is great. But there’s still a big gap between the number of companies benefiting from OSS and those actually contributing back.
Take Priyanka Sharma from the Cloud Native Computing Foundation (CNCF), for example. She pointed out that many key maintainers of the Linux Foundation’s biggest projects work for major companies. That’s one of the rare success stories where companies directly invest in the people who maintain the software they rely on. But for a lot of smaller projects, the maintainers are left scrambling to find a way to fund their work. It’s like running a café everyone in town loves but nobody ever pays for.
What’s even more ironic? Some maintainers have tried to monetize their projects—maybe by offering premium features or charging for support—but those attempts often backfire. The very community they serve sometimes pushes back, as if asking for compensation is a crime. Thomas Johnson from Multiplayer talked about how it’s getting harder for maintainers to make money off their work, and some have even had to resort to restrictive licenses to push back against companies taking advantage of their work for free.
So, what are the options here? One way is direct corporate funding, where companies pony up to support the projects they depend on. GitHub Sponsors, for instance, has funneled $40 million into the hands of open-source maintainers. That’s a start, but it’s still a drop in the bucket. Some have suggested that companies who profit from open-source projects should share that revenue with the developers. Sounds fair, right?
Another indirect route is getting companies to contribute code or resources instead of cash. Some big names already pay employees to contribute to open-source projects. For example, Adobe has been contributing to projects under the CNCF banner for years. The idea here is simple: if you use the software, you should help maintain it. It’s a win-win. Companies ensure the projects they rely on stay secure and up-to-date, and developers get the support they need to keep going without burning out.
Then there’s the idea of intermediary companies—like brokers between developers and corporations. These companies could help manage the relationship, ensuring that maintainers get paid while companies get the necessary updates and fixes. Tidelift, for instance, pays maintainers to follow secure development practices. It’s a neat model that helps everyone sleep a little better at night, knowing the software is safer and the people maintaining it aren’t going broke doing it.
Non-profit foundations also play a huge role. Groups like the Linux Foundation or the Apache Software Foundation provide funding, mentorship, community, and even recognition for these developers. For some projects, these foundations have been a lifeline, but not every open-source project wants to be tied to a foundation. It’s a delicate balance.
And then, there’s the most forward-thinking option: public funding. The idea here is that open-source software is a public good, like roads or parks, and the government should fund it. Germany’s Sovereign Tech Fund is already trying this out, investing millions in open-source projects. It’s still early days, but the logic is sound. Governments rely on this software just as much as companies do, so why not help keep it afloat?
In the end, if we want open-source software to continue thriving, we have to figure out how to support the people who maintain it. Whether that comes from corporate sponsorships, government funding, or just a greater public awareness of how much we rely on this stuff, something’s got to give. Otherwise, we’re all just crossing our fingers and hoping that the unsung heroes behind our favorite apps don’t get fed up and walk away.