Open Source Business Models
I am apparently missing FOSSCamp because of my high workload, but I offer these notes from the excellent MIT Enterprise Forum Event on Open Source from last year, excerpted from my post MITEFC Open Source Conference Notes
Open Source licenses gemerally fall into in three buckets (Props to Simon Philips for his clear description):
- “A”: market forming models allow free use, modification and redistribution. Examples: BSD, Apache.
- “B”: Community based (or file-based) models allow free addition, but restrict modification. Such that adding a new file is external to license restrictions, but changing a file triggers the license (i.e. must open-source the changes you made). Examples: Solaris, maybe LGPL?
- “C”: Competitor threatening: any innovation needs to use same license: GPL
Almost all open source licenses only trigger when you redistribute - so you can use your modifications or addons internally all you like, as long as the code doesn’t leave your shop.
The previous phenomenon may be a big driver of SAAS/on-demand - a legalistic driver for this new delivery mechanism, rather than the economic/technical drivers often discussed.
Business models for open-source
- Support: give away s/w, sell service contracts, subscriptions. Examples: JBoss, RedHat (Is this really an insurance product?)
- Dual License: Have a second license that allows commercial use/redistribution. Example: Mysql
- Two products: Have a free software product that drives value of a second, proprietary software or content. (interesting)
- Hosted: offer as a service/on-demand (per the previous main point above)
- Hardware sales / appliance (give away FOSS, sell all-in-one (IBM’s motive?)
Hope all the folks are doing well at the Hilton @MIT, just one block away from my apartment!

Beautiful Evidence