Open Source Software Licenses and Business Models Explained
summary
History links license choices to business outcomes and gives concrete tradeoffs: choose goals first, then license to match whether revenue comes from support and managed services, dual license and enhanced commercial editions, or SaaS deployments. The cloud undermines copy‑left enforcement so commercial forks and source‑available licenses rise, exemplified by MySQL dual licensing and MongoDB shifting licensing; expect permissive licenses to drive adoption while cloud breaks GPL forces product teams to protect monetization and adopt contributor agreements and trademark and patent policies.
AI-written summary · about
chapters (15)
- 0:00Start
- 8:39Business: Lower Costs, Short Term and Long Term
- 13:20Not Quite Open Source
- 16:53Cloud Services tend to bundle your Hardware usage costs with those of software
- 24:52Open Source Project vs Product
- 38:14Development
- 38:32Business Models: The Outcome
- 39:06Big Exit
- 41:04Lifestyle Business
- 42:13Distribution vs Monetization
- 45:06Open Source Business Models Overview
- 46:33Consulting and Custom Engineering
- 48:39Support and Managed Services
- 50:49Dual Licensing
- 51:35Enhanced Commercial Version
related talks
30mOpen Source Licensing: Use Versus Abuse
14mOpen Source Licensing in a Business World
31mCommercial Models and Open Source: How Revenue Generation & Open Source Fit Together
25mLicensing Tradeoffs in Open Source Startups
46mHow to Live Giving Away Your Software: Business and Free Software
22mChoosing the right software license.
51mThe Impact of Leveraging Open Source
01h 04mOpen Source, Open Mind: The Cost of Free Software