# Permissive Licensing Preserves the Code Not the Product ## Claim An Apache-style permissive license keeps a shuttered tool's code forkable, but it doesn't keep the maintained product or its team alive for the people who depended on them. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Holds when an acquirer shutters a product post-acqui-hire and leaves the repository public under its original license. - Breaks down when the acquirer keeps the product running under the new owner (the source article's own counter-example: Graphite stayed independent in the same market). - Doesn't establish anything about whether a fork will actually happen or succeed — only that the legal path to one remains open. ## Evidence Cursor's acquisition of Continue — an Apache 2.0-licensed, open-source coding assistant — has "the hallmarks of an acqui-hire," with the product itself shuttered while the code, per its license, remains forkable by anyone. ## Links - [[AI & the Future of Knowledge Work MOC]] — what survives when a tool knowledge workers depend on is shut down - [[3. Resources/Permanent Notes/Permissive Licenses Define a Floor But Don't Constitute a Community]] — because extends; that note establishes the general floor-not-community claim, this one supplies the acquisition-specific evidence. - [[3. Resources/Permanent Notes/The Hard Part of Replacing SaaS Is Recovering Your Data]] — because contrasts; that note is about data portability under vendor lock-in, this one is about code portability under acquisition — different assets, same risk-management logic. - [[3. Resources/MOCs/Open Source Governance MOC]] — because applies-in; this is a concrete case study for any adoption checklist weighing acquisition/EOL risk. ## Tests / falsifiers - Track whether a maintained fork of Continue actually emerges within, say, 12 months — if none does despite the permissive license, "preserves the code" is true in theory but not in practice for tools without an existing engaged community. - Find a counter-case where a permissively licensed tool's acquirer keeps both the product and the team — that would show the shutdown pattern isn't inherent to acqui-hires generally. ## Maintenance - Last tended: 2026-08-16 - Next review: 2026-11-16 ## Source - [[3. Resources/Readwise/Full Document Contents/Articles/Cursor Quietly Acquires Continue, an Open-Source Alternative to GitHub Copilot]] — reports the acqui-hire pattern and Continue's Apache 2.0 licensing.