Relicense to AGPL-3.0 (adoption-first strategy)#20
Merged
Conversation
Switches to AGPL-3.0 to optimize for adoption while retaining meaningful protection against proprietary forks. AGPL is OSI-approved open source (unlike ELv2), which unblocks honest "open source" marketing claims and eliminates the enterprise stigma around non-OSI licenses. Network copyleft forces any hosted competitor to publish modifications, and the existing CLA preserves the option to offer commercial licenses to organizations that cannot comply with AGPL's disclosure requirements. - LICENSE: replaced ELv2 with full AGPL-3.0 text - README: badge, License section - CONTRIBUTING.md: license reference - apps/marketing/src/app/page.tsx: CTA copy + footer label Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Switches the license from Elastic License 2.0 back to AGPL-3.0 to optimize for adoption. The stated product strategy is adoption-first with a managed hosted service on top (Supabase/PostHog/Plausible playbook) — AGPL is the battle-tested license for that business model.
Why AGPL-3.0 over ELv2 for this strategy
What AGPL doesn't prevent
Acknowledging honestly: AGPL does not prevent someone from forking and reselling — it just forces them to do so under AGPL terms (no proprietary features, all modifications public, can't sell to enterprises with AGPL bans). The real reselling moat is trademark, not license.
Changes
LICENSE— full GNU Affero GPL v3 textREADME.md— AGPL badge, rewritten License sectionCONTRIBUTING.md— license reference updatedapps/marketing/src/app/page.tsx— CTA copy restored to "Free and open source" (accurate under AGPL), footer label updatedNo changes to CLA.md / CLA-entity.md — the relicense-grant language is license-agnostic.
Test plan
Generated with Claude Code