From nag screen to network call
WinZip shipped its first trial version in 1991 with a simple proposition: use it free for a while, then pay. PKZIP, its command-line rival, worked the same way. The enforcement mechanism was a dialogue box and social pressure. Neither could technically prevent continued use; both relied on the user's willingness to comply. This was not a weakness anyone rushed to fix, because the friction of non-payment was low and the distribution cost of the software was also low — a floppy disk or a bulletin-board download.
What changed was not the economic logic but the infrastructure. Once software moved to the server, the vendor could move the enforcement there too. A SaaS product does not nag; it simply stops working when the quota runs out or the trial period expires. The nag screen was always a proxy for a gate the vendor could not technically place. Freemium places the gate.
Open core extends the same logic to source code. The core of the product is released under an OSI-approved licence, free to download, modify, and run. The features that matter most to enterprise buyers — single sign-on, audit logging, advanced analytics — are held back under a proprietary or commercial licence. The user gets genuine value from the free tier; the vendor captures revenue from the fraction that needs more. WinZip's modal dialogue, translated into a 2020s codebase, becomes a feature flag checked against a licence key on the vendor's authentication server.
The line from shareware to the SaaS gate
The transition was not abrupt. A middle period ran from roughly 2005 to 2015 in which open-source companies tried to survive on support contracts alone — the Red Hat model, generalised. That model worked for operating system distributions but proved fragile for developer tools, where users were technically sophisticated enough to self-support and cloud providers were willing to run hosted versions of popular open-source projects at scale without paying upstream. Amazon Web Services hosting Elasticsearch without contributing back to Elastic was the canonical grievance, one that drove Elastic to the SSPL in 2021 before returning to AGPL in 2024.
The licencing fights of the early 2020s — HashiCorp's move to the Business Source Licence, Redis Ltd's dual-licence pivot — are best understood as the open-core model tightening its grip. Each represented a vendor deciding that the honour system embedded in an OSI-approved licence was insufficient, just as WinZip's developers had implicitly decided that a nag screen was insufficient once the commercial stakes grew large enough. The BUSL and its variants impose a time delay before code becomes genuinely open; the practical effect is to restore, in legal form, the trial-period logic that shareware enforced through social convention.
- CHRONOLOGYAS RECORDED
- 1991WinZip trial version released; shareware honour-system model in mainstream use
- ~2005–2015open-source support-contract era; Red Hat model generalised
- 2018MongoDB writes the SSPL after AWS hosting friction
- January 2021Elastic moves Elasticsearch to SSPL
- August 2023HashiCorp moves Terraform to BUSL
- March 2024Redis Ltd dual-licences Redis under RSALv2 + SSPL
- 2024Elastic returns to AGPL
What the model actually enforces
Freemium and open core are more durable than the honour system for one structural reason: the cloud makes metering cheap. Counting API calls, measuring seats, tracking monthly active users — none of this required significant engineering investment by the mid-2010s. The vendor knows exactly who is using what, and the product can respond accordingly. WinRAR's permanent trial, still running in 2025, is a curiosity precisely because the infrastructure to enforce payment has existed for a decade; the decision not to use it is now the anomaly.
What open core cannot solve, and shareware never had to, is the contributor relationship. When a project relicences from an OSI-approved licence to the BUSL or SSPL, contributors who assigned rights through a Contributor Licence Agreement have no recourse; those who did not may have a claim. The CLA, in this framing, is the legal instrument that makes the relicensing moment possible — the equivalent of the vendor retaining the master copy of the floppy disk. The nag screen was never the point. Control of the asset always was.