Open source has always allowed businesses to profit from software they did not write. Take nginx, the open-source web server behind so many business websites. An online retailer can use it to help run a profitable shop without paying a licence fee for nginx itself or sharing its earnings with the developers. Its BSD licence permits that commercial use. The software can be essential to a company’s business, yet the company has no obligation to contribute towards its continued development and maintenance.
AI coding assistants have added a new twist to this arrangement. Companies have trained models on publicly available source code and built subscription businesses around the results. The developers behind those projects still have bugs to fix, users to help and security reports to investigate, whether any subscription income reaches them or not. I find it hard to accept that pointing to the licence should end the discussion. If a company can build a profitable service partly from their work, asking it to help fund the maintenance seems reasonable enough.
Thanks for the Code. Now Pay Us.
Microsoft has secured an enviable position. Developers use GitHub to publish software, fix bugs and review each other’s work. Microsoft owns the platform and sells an assistant trained partly on public GitHub code. The community supplies years of accumulated knowledge; Microsoft gets another subscription product. Building that product takes considerable engineering, but so did building the software it learned from.
GitHub offers free Copilot Pro access to eligible maintainers of popular open-source projects. Useful, certainly. As an answer to the funding problem, it is almost comically inadequate. A project needing a security audit cannot pay the auditor with a free Copilot account. Access to the product is a perk. Supporting the work that helped make the product possible requires rather more commitment.
Transparency Is Apparently for Other People
Is it unreasonable to expect projects making substantial use of generative AI to disclose it publicly? A developer cannot simply ask users to trust that everything is fine. I see no reason to extend that courtesy to the companies supplying the models. “Trained on publicly available code” leaves unanswered which licences were accepted, how they were checked and what happened when the licensing was unclear.
BigCode’s original Stack dataset provided information about its sources and a mechanism for requesting exclusion. That approach has limitations, including the inability of a later exclusion to undo earlier training, but it gives developers something to examine. Companies should explain their procedures clearly enough for maintainers to challenge them. Expecting openness from the people supplying the code while offering vague assurances about its use is a remarkably convenient standard.
Somebody Else Gets the Extra Work
curl shows what happens when producing a report becomes easier than investigating it. Daniel Stenberg described AI-generated security submissions that consumed hours of his team’s time. Later, he reported much better submissions, with AI-assisted analysis finding genuine problems. The workload still grew: somebody had to investigate, fix, test and release the software.
Those discoveries are valuable. They also expose the missing person in the productivity sales pitch: the maintainer receiving the output. A user can generate a patch or report quickly, then hand the expensive checking to somebody else. Count only the time saved by the person using the assistant and almost any tool can look productive. The hours spent dealing with its output belong in the calculation too.
Put It in the Budget
AI companies could pay maintainers, fund security reviews and support neglected dependencies. They could help check generated contributions before encouraging users to submit them. There is no need to calculate a royalty for every function: talk to projects, identify useful work and pay for it. Publish the contributions so people can judge whether the support amounts to much.
I am tired of maintenance being treated as a charitable cause while the products built from shared software are treated as serious businesses. If a company can budget for GPUs, research and sales staff, it can budget for upstream development. The people keeping those projects alive should not have to pass round a donation link while being invited to admire the next breakthrough in developer productivity.
If AI companies can make billions from open-source code, why are the people maintaining it still expected to work for free?

Please read our Comment Policy before commenting.
I’m not convinced. Open source has always allowed companies to make money from other people’s work without paying them. Why should AI companies be treated differently? Is this really about fairness, or are we just uncomfortable with how much money Microsoft and others are making?
So, sure, open source licenses don’t technically demand payment – just a polite nod of acknowledgment, like you’d give the neighbor whose WiFi you’re borrowing. But AI companies seem to have skipped that chapter in the etiquette book. They’ve been vacuuming up code for their LLMs without so much as a footnote, leaving developers stuck with server bills that are ballooning faster than Elon Musk’s ego. It’s the digital equivalent of throwing a rager at someone else’s house and leaving them with the cleanup. Once upon a time, businesses understood stakeholders – you know, the whole “we’re in this together” thing. Open source developers? They’re basically your unpaid, over-caffeinated suppliers. Maybe these AI companies should try and treat them a little better than an old VHS tape that fell behind your entertainment center. They deserve some love and that really should include remuneration.
I think Sean makes a really good point here. Just because open source licences allow companies to profit from developers’ work doesn’t mean those companies have no moral responsibility to give something back. When you’re making billions from an ecosystem sustained largely by unpaid contributors, financially supporting that ecosystem should be a given, not an optional act of generosity.
The LLMs are just a massive copyright breach.
There’s glaring hypocrisy here too. OpenAI was quick to complain about DeepSeek allegedly using its models to train a competitor, yet AI companies have benefited enormously from the work of open source developers, many of whom receive nothing in return. Funny how the value of other people’s work suddenly matters when it’s their ‘own’. And it’s not even their own.
When I heard about “open source” first in 1998, the motto was “You don’t sell your software, you sell services around it”. Isn’t this exactly what the AI companies do?
Re: Poll: Should AI companies that train on open-source code be expected to give more back?
Yes, absolutely. Mainly thru funding.
And it should be billions of $, not chicken feed.