License to Build
Your team uses open-source frameworks, libraries, and tools. Which ones affect your license obligations? Pick your product type.
Mobile App
iOS or Android. You distribute through app stores, which means every library in your bundle ships to users. Each dependency's license conditions apply.
Learn more →Web App
SaaS, dashboards, web platforms. Frontend JavaScript ships to the browser. Backend code stays on your server. Different obligations apply to each side.
Learn more →Public API
Backend services others consume over HTTP. Your code stays on your server. Most copyleft conditions do not apply, but AGPL and SSPL have specific terms for this scenario.
Learn more →CLI Tool
Command-line tools you distribute to users. Like mobile apps, you are shipping binaries, so every dependency license matters.
Learn more →The Core Distinction
Tools you use to build (IDEs, editors, compilers, linters, bundlers) impose no obligations on your output. Components that ship in your product (libraries, frameworks, fonts) carry their license conditions into your product.
Not sure where to start?
The Cheat Sheet has every license type and product combination in one table.