Open core

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Lua error in package.lua at line 80: module 'strict' not found.

Open core is a business model for the monetization of commercially-produced open source software. Coined by Andrew Lampitt in 2008,[1] the open core model primarily involves offering a "core" or feature-limited version of a software product as free and open-source software, while offering "commercial" versions or add-ons as proprietary software.[2][3]

The concept of open core software has proven to be controversial, as many developers do not consider the business model to be true open source software. Despite this, open core models are used by a large number of open source software companies.[4]

Examples

  • Oracle's MySQL database software is dual-licensed under a proprietary license, and the GNU GPL; proprietary versions offer additional features and enterprise support plans.[5]
  • Eucalyptus, private cloud software, has a proprietary enterprise edition which provides additional features.[6][7][8]
  • Rapid7, with its Metasploit Pro and Metasploit Express products which are based on the open source Metasploit core framework.
  • Talend uses an Open Code license for its data management, data integration and cloud products.

Use of contributor license agreements

Some open core products require their contributors to sign a contributor license agreement, which either dictate that the copyright of all contributions to the product become the property of its owner, or that the product's owner is given an unlimited, non-exclusive license to use the contributions, but the authors retain copyright ownership. In an open core scenario, these agreements are typically meant to allow the commercial owner of the product (which in some cases, is ultimately the copyright holder to all of its code, regardless of its original author) to simultaneously market versions of the product under open source and non-free licenses. This contrasts more traditional uses of CLAs, which are meant solely to allow the steward of an open source project to defend its copyright, or guarantee that the code will only ever be made available under open source terms, thus protecting it from becoming open core.[9][10][11]

See also

External links

  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.