If you've ever wondered whether it's possible to give something away for free and still build a six-figure business from it, the story of one JavaScript library offers a remarkably instructive answer — and the economic mechanics behind it deserve far more scrutiny than a typical developer blog post would suggest.

The story at the center of this analysis involves a developer who, over four years, generated over $350,000 from a JavaScript library called lightGallery — not through venture capital, not through a SaaS subscription model, but through the elegant and surprisingly underappreciated mechanism of dual licensing. As I noted in my analysis of AI search monetization, the digital economy is perpetually searching for sustainable revenue architectures. This one, it turns out, has been hiding in plain sight for decades.

---

The Economics of Deliberate Scarcity in a World of Free Code

There is a paradox at the heart of open-source software that economists find genuinely fascinating: how do you monetize something you've voluntarily made free? The naive answer is that you cannot. The sophisticated answer — the one that Oracle, Qt, and now a growing cohort of independent developers have discovered — is that you don't monetize the code. You monetize the legal permission to use it privately.

This is the core insight of dual licensing, and it is worth unpacking with some precision. When a developer releases software under the GNU General Public License (GPL), they are not simply being generous. They are, in economic terms, creating a conditional good — one whose value to commercial enterprises is deliberately encumbered. The GPL's "viral" or "copyleft" clause requires that any derivative work also be released under the same open-source terms. For a startup building a proprietary SaaS product, or an enterprise company whose website code represents genuine competitive advantage, this is not a minor inconvenience. It is an existential compliance risk.

"If a company uses your GPL-licensed JavaScript on their website, the viral nature of the license may require them to release their entire website's source code. Most enterprise companies cannot do this." — lightGallery dual licensing case study

The commercial license, then, is not a product competing with the free version. It is the release valve for a pressure system that the developer has carefully engineered. In the grand chessboard of global finance, this is the equivalent of controlling a critical square not by occupying it aggressively, but by making every path around it prohibitively costly.

---

GPL vs. AGPLv3: A Licensing Choice With Macroeconomic Implications

The technical distinction between GPLv3 and AGPLv3 may appear to be a matter of legal fine print, but it carries surprisingly broad economic implications — particularly as the software industry continues its tectonic shift toward cloud delivery.

GPLv3 is triggered by distribution: if you ship code to users, the copyleft obligations activate. AGPLv3 closes what practitioners call the "SaaS loophole" — the scenario where a company runs GPL-licensed code on a server, never distributes it to users, and therefore (under GPLv3) technically owes no open-source obligations. AGPLv3 extends the trigger to network interaction: if a user interacts with the software over a network, the obligations apply.

This distinction matters enormously in 2026, when the overwhelming majority of software is delivered as a service. A developer choosing between these licenses is, in effect, making a strategic bet about where their library will be deployed. The lightGallery case — a JavaScript gallery library primarily used on public-facing websites — made GPLv3 the appropriate choice. A backend analytics library or an AI inference tool embedded in a cloud service would almost certainly warrant AGPLv3.

The broader economic lesson here is one of market segmentation through legal architecture. This is not so different from how pharmaceutical companies use patent law to segment markets between branded and generic drugs, or how airlines use fare class structures to extract different prices from business and leisure travelers. The mechanism differs; the underlying economic logic is identical.

---

The Contribution Problem: Intellectual Property as a Balance Sheet Item

One of the most underappreciated economic dimensions of the dual licensing model is what happens when other developers contribute to your project. The article is admirably direct on this point:

"For a successful dual-licensing model, you cannot sell code you don't own. When others contribute, you need the legal rights to re-license their work." — lightGallery dual licensing case study

This is, at its core, a question of intellectual property as a balance sheet item. In traditional accounting, a company's codebase may appear as an intangible asset. But in the dual licensing model, the legal clarity of ownership over that codebase is the asset — and it can be eroded, contribution by contribution, if proper agreements are not in place.

The two instruments described — the Contributor License Agreement (CLA) and the Copyright Assignment Agreement (CAA) — represent different points on a spectrum of control. The CLA grants the project owner a license to use contributed code while the contributor retains ownership; the CAA transfers ownership outright. For a commercial open-source operation, the CAA is the more robust instrument, precisely because it eliminates the ambiguity that could later complicate licensing negotiations or, in a worst-case scenario, expose the developer to infringement claims from former contributors.

This is the kind of detail that separates a sustainable commercial operation from a hobby project that happens to generate some revenue. As I have observed across multiple technology sectors, the failure to properly structure intellectual property rights at the outset is one of the most common — and most expensive — mistakes that early-stage technology ventures make. The economic domino effect of a single unresolved IP dispute can cascade through a company's valuation, its fundraising prospects, and its ability to execute commercial agreements.

---

The Broader Context: India, Energy, and the Geopolitics of Digital Infrastructure

It would be tempting to treat the lightGallery story as a charming individual success narrative and leave it at that. But the related coverage this week points toward a larger structural question that the dual licensing model implicitly addresses.

Raghuram Rajan and Rohit Lamba, writing about India's AI ambitions, pose a question that resonates far beyond South Asia: how does a nation — or, by extension, an individual developer or a startup — avoid becoming a tenant in someone else's digital infrastructure rather than an owner? Their concern is that India risks consuming AI tools built elsewhere, on terms set by others, without developing the sovereign capacity to shape those terms.

The dual licensing model, viewed through this lens, is a microcosm of that same tension. The developer who releases code under a permissive MIT license is, in economic terms, making a gift to the commons — generous, certainly, but strategically passive. The developer who employs dual licensing is asserting a form of digital property rights that generates ongoing economic returns. The difference between these two postures, aggregated across thousands of open-source projects, has meaningful implications for how value is distributed in the global software economy.

This connects, too, to the energy policy analysis coming out of New Zealand this week, which highlights how the erosion of resource sovereignty — in that case, declining domestic gas production — translates directly into economic constraint. Code, like energy, is infrastructure. The terms on which it is made available shape who captures the economic surplus it generates.

---

The Transaction Cost Architecture: Kelviq and the Infrastructure of Monetization

The article's disclosure that the author is a co-founder of Kelviq — the platform used to handle license delivery, key generation, and payment processing — is worth examining not as a conflict of interest, but as an economic phenomenon in its own right.

Kelviq charges 3.5% per transaction and handles tax compliance across jurisdictions. This is, in the language of economics, a transaction cost reduction service. The barrier to monetizing open-source software has historically been not the legal framework — dual licensing has existed for decades — but the operational overhead of managing license agreements, global tax obligations, and payment infrastructure at scale.

The emergence of platforms like Kelviq is, in many ways, analogous to what payment processors like Stripe did for e-commerce in the early 2010s: they collapsed the fixed costs of entering a market, enabling a much larger population of potential participants to reach commercial viability. This is a pattern I have observed repeatedly in financial markets — when transaction costs fall, market participation rises, and the aggregate economic activity in that sector expands.

For context, a 3.5% take rate is meaningfully higher than what a typical payment processor charges, but it bundles services — tax compliance, license file delivery, customer portal — that would otherwise require either significant engineering investment or expensive third-party integrations. Whether this represents fair value will depend heavily on the volume and geographic distribution of a given developer's sales. For someone generating $350,000 over four years, the implied fees of roughly $12,250 appear to represent reasonable value for the operational complexity managed.

---

The Symphonic Movement of Open-Source Monetization

If economic cycles are symphonic movements, then the history of open-source monetization has been a particularly interesting composition. The first movement — roughly the 1990s through mid-2000s — was characterized by the idealistic assertion that software wanted to be free, full stop. The second movement introduced the services model: give away the code, sell the support, the consulting, the customization. Red Hat built a billion-dollar business on this thesis before IBM acquired it for $34 billion in 2019.

The third movement — the one we are now in — is more nuanced and, frankly, more economically sophisticated. It acknowledges that software can be free for those willing to accept its terms, while simultaneously creating a commercial pathway for those who are not. This is not a betrayal of open-source principles; it is their maturation into a sustainable economic form.

The lightGallery case is a compelling data point in this third movement. $350,000 over four years from a JavaScript library is not, by venture capital standards, a remarkable outcome. But it is a sustainable one, generated without external funding, without a team of salespeople, and without the existential pressure of a growth-at-all-costs mandate. In an era when AI tools are reshaping cloud spending in ways that CFOs are struggling to control, the appeal of a business model that generates predictable, low-overhead revenue deserves serious consideration.

---

Actionable Takeaways: What This Means Beyond the Developer Community

For readers who are not software developers, it might be tempting to file this analysis under "interesting but not relevant." I would push back on that instinct firmly.

For investors and analysts: The dual licensing model represents a category of software asset that is systematically undervalued by traditional metrics. A library with strong developer adoption, a GPL license, and a clean CAA framework has a monetization pathway that does not require venture funding or a sales team. As the broader digital economy continues to evolve, these small but durable software assets may represent an overlooked asset class.

For policymakers: The dual licensing model is, in effect, a private-sector solution to the public goods problem of software infrastructure funding. Governments that are concerned about the health of their domestic software ecosystems — and the Rajan-Lamba argument about India's AI tenancy problem applies equally to many other nations — might consider how intellectual property frameworks can be structured to encourage this kind of sustainable commercial open-source development, rather than defaulting to either pure public funding or purely proprietary models.

For entrepreneurs: The key insight is not the mechanics of GPL vs. AGPLv3, but the underlying strategic principle: structure your offering so that the path of least resistance for commercial users leads to a revenue event for you. This principle applies far beyond software. It is, at its core, the logic of every successful two-sided market, every freemium model, and every platform that has ever generated sustainable revenue from a nominally free product. The Harvard Business Review has documented extensively how open-core and dual-licensing models are reshaping enterprise software economics — and the pattern shows no signs of reversing.

---

The Philosophical Coda

Markets are the mirrors of society, and the dual licensing model reflects something genuinely interesting about the current moment: the growing recognition that sustainability and openness are not in opposition, but can be engineered to reinforce each other. The developer who releases lightGallery under the GPL is not being naive about commerce; they are being sophisticated about it. They are betting that the value of their work will be recognized most clearly by those who most need to keep it private — and that this recognition will translate into a willingness to pay.

There is something almost classically economic about this insight — the kind of elegant mechanism design that makes a theorist smile. The question worth sitting with, as the open-source ecosystem continues to mature, is whether this model scales: not just to individual developers, but to the broader challenge of funding the digital infrastructure on which the global economy increasingly depends. The $350,000 answer is promising. The larger question remains open.