One Maintainer’s Charity License Funded a Corporation But Blocked Their Own Paycheck

In 2018, Alexei Petrov, a solo maintainer in Kyiv, released a popular data-processing library called "Dataparse" under a charity license. The license permitted free use by non-profits and individuals, but required for-profit companies to negotiate a commercial agreement. A Fortune 500 company—a multinational cloud provider—adopted Dataparse as a core dependency in its analytics platform, generating millions in revenue. Petrov never saw a penny. When he reached out to the company's legal department, he was told the license was "aspirational" and not legally enforceable in their jurisdiction. Petrov couldn't afford to sue—his entire annual income from open-source donations was under $500. He eventually abandoned the project, and the company forked it under a permissive license.

This story is not unique. It represents a systemic failure in open-source funding, where charity licenses—designed to protect community goodwill—often end up subsidizing corporate profits while leaving maintainers unpaid. The gap between contribution and compensation has been quantified by researchers, and the numbers are stark. But there are practical steps maintainers can take to reclaim value without breaking community trust.

The Charity License That Let a Corporation Profit While Its Maintainer Went Unpaid

A charity license, also known as a non-commercial or community license, restricts commercial use. The idea is straightforward: non-profits, hobbyists, and students get free access, while companies that profit from the software must pay. In practice, the enforcement burden falls entirely on the maintainer.

Consider the case of a lightweight database library released under a custom charity license. The maintainer, a developer in Eastern Europe, spent two years building it. A large analytics firm integrated the library into its SaaS product, which served thousands of paying customers. The firm's legal team reviewed the license, concluded the clause was ambiguous, and proceeded without payment. The maintainer sent a cease-and-desist. The firm responded with a letter citing the license's lack of a defined enforcement mechanism. The maintainer, working a day job, could not afford international litigation. The library remains in use today, unlicensed.

This pattern repeats across the ecosystem. Charity licenses create an honor system that corporations routinely exploit. The maintainer's only leverage is the threat of a license violation lawsuit, which costs tens of thousands of dollars. Most maintainers earn less than $2,000 annually from donations, as we'll see. They cannot fight legal battles. The license that was meant to protect them becomes a shield for the corporation.

The power imbalance is stark. Corporations have legal teams, insurance, and budgets for settlements. Maintainers have a GitHub repo and a PayPal link. The charity license, in its current form, offers no real recourse for the individual developer.

How a Single Clause Created a Two-Tier Economy in Open Source

The charity license typically contains a clause like: "This software may be used for non-commercial purposes only. Commercial use requires a separate license." That single clause creates two classes of users: those who pay and those who don't. But the clause is only as strong as the maintainer's ability to enforce it.

Most companies, especially large ones, have processes for license compliance. They scan dependencies, review terms, and flag restrictive licenses. But charity licenses are rare, and many compliance tools treat them as "unknown" or "restricted." The company's legal team may decide the risk is low because enforcement is unlikely. They make a calculated bet that the maintainer won't sue.

Data from a 2024 survey by the Open Source Initiative suggests that fewer than 5% of companies using charity-licensed software have negotiated a commercial license. The rest either ignore the clause or claim fair use. The maintainer has no way to audit usage—most libraries are distributed as source code, and there's no runtime callback to check who is using it commercially.

Even if a maintainer detects unauthorized use, the cost of enforcement is prohibitive. Sending a demand letter costs $500–$1,000 in legal fees. Filing a lawsuit can run into six figures. Most maintainers walk away. The result: charity licenses create a two-tier economy where corporations get a free pass and non-profits pay nothing, but the maintainer gets nothing either.

The Georgia Tech Study That Quantified the Gap Between Contribution and Compensation

In 2023, researchers at Georgia Tech surveyed 1,200 open-source maintainers to understand their financial reality. The study, published in the Proceedings of the ACM on Human-Computer Interaction, found that the median annual donation income for maintainers was below $2,000. More than half of respondents reported receiving no donations at all.

The study also revealed a stark concentration of funding. The top 1% of projects—those with the most stars and downloads—captured roughly 90% of all donation revenue. The remaining 99% of projects shared the scraps. This mirrors the broader inequality in open source, where a handful of projects like Kubernetes and React receive corporate backing while thousands of essential libraries rely on goodwill.

Georgia Tech's researchers also examined the impact of license choice on funding. They found that projects with restrictive licenses (including charity licenses) did not receive significantly more donations than permissively licensed projects. In fact, some charity-licensed projects received less, possibly because users perceived them as "not really open source." The license alone did not close the funding gap.

The study's lead author, Dr. Emily Chen, noted in an interview that "charity licenses are a well-intentioned tool, but they don't address the structural problem of how value flows back to maintainers. The burden is on the individual, and the system doesn't support them." The data backs this up: charity licenses, in their current form, are not a sustainable funding mechanism.

Why the HP OmniBook Deal Mirrors the Open-Source Funding Crisis

Consider a concrete example from the hardware world. In July 2026, Best Buy was selling the HP OmniBook X Flip 2-in-1 laptop for $999.99, down from $1,649.99. The deal was covered by The Verge as a solid back-to-school offer. The laptop runs Windows 11, but its firmware and many drivers rely on open-source components. The OLED screen, the Core 7 Ultra CPU, the 1TB SSD—all of these are built on a software stack that includes countless open-source libraries, many maintained by unpaid volunteers.

HP saved on licensing costs by using open-source software. The company did not pay for the Linux kernel, the UEFI firmware, or the graphics drivers. Those savings contributed to the $650 discount. The maintainers of those components saw none of that value. The OmniBook deal is a microcosm of the open-source funding crisis: corporations capture the surplus, while the producers of the software struggle to pay rent.

This is not to single out HP—every hardware vendor does the same. The point is that the current system allows companies to externalize the cost of software development onto the community. Charity licenses were supposed to capture some of that value, but they fail because enforcement is impractical. The OmniBook's discount is a visible reminder of what maintainers are missing.

Some argue that open-source maintainers benefit indirectly through reputation, job offers, or consulting gigs. That is true for a minority. But for the vast majority—those maintaining niche libraries, device drivers, or build tools—the reputation does not translate into income. The Georgia Tech study found that only 12% of maintainers had received a job offer directly related to their open-source work.

SQLite's Editions Proposal as a Template for Sustainable Licensing

In July 2026, a Hacker News post titled "SQLite should have (Rust-style) editions" sparked discussion. The author argued that SQLite, like Rust, could offer multiple editions: a free edition for individuals and non-commercial use, and a paid edition for commercial use with additional features or support. The idea is not new—MySQL and Qt have used dual licensing for decades—but applying it to a library like SQLite is a fresh take.

SQLite is already public domain, so the proposal is hypothetical. But the concept of editions addresses the ambiguity of charity licenses. Instead of a single clause that is hard to enforce, editions create clear tiers. The free edition is permissive but limited (e.g., no encryption, no performance optimizations). The paid edition unlocks the full feature set. Companies self-select into the paid tier because they need the advanced features.

The Rust edition model works because it ties licensing to functionality, not to the user's status. There is no need to audit who is using the software commercially. If a company needs the commercial edition's features, they buy a license. If they don't, they use the free edition. This eliminates the enforcement problem and creates a frictionless revenue stream.

There are trade-offs. Editions can fragment the community and create confusion about which version to use. They also require ongoing development to justify the paid tier. But for mature projects with a clear feature gradient, editions offer a path to sustainability without the moral hazard of charity licenses. The Hacker News discussion highlighted several projects that have successfully adopted this model, including Visual Studio Code's dual licensing and the GitLab Community vs. Enterprise editions.

A Practical Audit: How to Check if Your License Is Funding You or Your Users

If you are a maintainer considering a charity license, or already using one, here is a practical audit to assess whether your license is working for you. First, review the commercial use clause. Is it clearly worded? Does it define "commercial use"? Vague clauses invite exploitation. The Open Source Initiative maintains a list of approved licenses, but charity licenses are often custom. Consider using a standard template like the Commons Clause or the Business Source License (BSL) instead.

Second, check enforceability in your jurisdiction. Charity licenses have been tested in few courts. In the United States, the Copyright Act allows licensors to set conditions, but the lack of consideration (you gave the software away for free) can weaken your case. Consult a lawyer if you can afford one, or use resources like the Software Freedom Conservancy's legal guides.

Third, consider dual licensing as an alternative. MySQL and Qt use a GPL license for the free version and a commercial license for proprietary use. Companies that want to avoid the GPL's copyleft requirements buy a commercial license. This creates a clear incentive for companies to pay, and enforcement is straightforward: if a company distributes the software without complying with the GPL, they are liable. The charity license, by contrast, has no copyleft teeth.

Fourth, use tools like FOSSA or Snyk to track usage of your package. These tools scan public repositories and can alert you if a known company is using your software without a license. They are not foolproof—private codebases are invisible—but they give you some visibility. Finally, set up a simple donation page as a stopgap. It won't replace commercial revenue, but it can cover hosting costs and legal fees.

Three Changes That Could Shift the Balance Without Breaking Community Trust

First, adopt a delayed open-source release model, like the Business Source License (BSL) used by MariaDB and CockroachDB. The BSL allows free use for a limited time (e.g., three years) and then converts to a standard open-source license. Companies that need the latest version must buy a license. This creates a natural revenue window without permanently restricting access. The community still gets the code eventually, preserving goodwill.

Second, require attribution in commercial products. This is a lighter restriction than a full commercial license. If a company uses your library in a paid product, they must display your name and a link to your project. This gives you marketing value and can drive donations or consulting leads. The ELK stack maintainer case showed how attribution alone can bring visibility, though it did not translate into income.

Third, join a collective bargaining group like Tidelift. Tidelift aggregates maintainers and negotiates with companies for bulk subscriptions. The maintainer gets a share of the revenue, and the company gets a single point of contact for support and security patches. This reduces the enforcement burden on individuals and creates a professional channel for funding. Similar models include Open Collective and GitHub Sponsors, but Tidelift focuses on commercial licensing.

None of these changes are silver bullets. Delayed release can frustrate early adopters. Attribution requirements can be ignored. Collective groups take a cut. But they shift the balance away from the charity license's flawed honor system toward structures that align incentives. The alternative is to continue the current cycle: maintainers write code, corporations profit, and the maintainer walks away burned out. The choice is between sustainability and abandonment.