Jump to content

Open-core model: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
m Added citation needed for one of the examples
Added one more example. Improve intro paragraphs to be more robust with more citations.
Line 8: Line 8:
{{broader|Business models for open-source software}}
{{broader|Business models for open-source software}}
[[File:GitLabUI 8.png|thumb|GitLab Community Edition]]
[[File:GitLabUI 8.png|thumb|GitLab Community Edition]]
The '''open-core model''' is a [[business model]] for the [[monetization]] of commercially-produced [[open-source software]]. Coined by Andrew Lampitt in 2008,<ref>{{cite book|last1=Phipps|first1=Simon|title=Open Source Strategies for the Enterprise|date=July 2012|publisher=O'Reilly Media|isbn=978-1-4493-4117-6}}</ref> the open-core model primarily involves offering a "core" or [[crippleware|feature-limited]] version of a software product as [[free and open-source software]], while offering "commercial" versions or add-ons as [[proprietary software]].<ref name="Riehle">{{cite conference
The '''open-core model''' is a [[business model]] for the [[monetization]] of [[open-source software]], which may or may not be originally created for the purpose of commercialization. Open-source software developed by existing companies to solve internal technological challenges (e.g. [[Apache Kafka]] by [[LinkedIn]]), as academic research (e.g. [[Apache Spark]] by Berkeley [[AMPLab]]), and by an individual (e.g. [[Git]] by [[Linus Torvalds|Linus Torvald]]) have all been commercialized eventually with an open-core model. Coined by Andrew Lampitt in 2008,<ref>{{cite book|last1=Phipps|first1=Simon|title=Open Source Strategies for the Enterprise|date=July 2012|publisher=O'Reilly Media|isbn=978-1-4493-4117-6}}</ref> the open-core model primarily involves offering a "core" or [[crippleware|feature-limited]] version of a software product as [[free and open-source software]], while offering "commercial" versions or add-ons as [[proprietary software]].<ref name="Riehle">{{cite conference
| first = Dirk
| first = Dirk
| last = Riehle
| last = Riehle
Line 22: Line 22:
| accessdate =
| accessdate =
| id =
| id =
}}</ref><ref>{{cite journal|first1=Anthony I.|last1=Wasserman|title=How the Internet transformed the software industry|journal=Journal of Internet Services and Applications |issn= 1867-4828 |pages= 11–22 |volume=2 |issue=1 |doi= 10.1007/s13174-011-0019-x |quote= Some companies have only a single version of their software, while others follow an “open core” model, providing a community release of the core version, and offering proprietary premium features using a commercial license. |date=2011}}</ref>
}}</ref><ref>{{cite journal|first1=Anthony I.|last1=Wasserman|title=How the Internet transformed the software industry|journal=Journal of Internet Services and Applications |issn= 1867-4828 |pages= 11–22 |volume=2 |issue=1 |doi= 10.1007/s13174-011-0019-x |quote= Some companies have only a single version of their software, while others follow an “open core” model, providing a community release of the core version, and offering proprietary premium features using a commercial license. |date=2011}}</ref> The open-source “core” is often sufficient in solving specific technical pain points of individual developers or small teams, while the “proprietary” layer around the core is needed to meet the business requirements of teams or large scale commercial or enterprise-grade deployments, such as security, auditing, and regulatory compliance; for example, [[HashiCorp|Hashicorp]]'s enterprise offering around the open-source software, Vault.<ref>{{Cite web|url=https://www.hashicorp.com/products/vault/enterprise|title=HashiCorp Vault: Enterprise Pricing, Packages & Features|last=HashiCorp|website=HashiCorp: Infrastructure enables innovation|access-date=2019-09-11}}</ref>


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 many open-source software companies.<ref name=li-opencore>{{cite web|title=Open Core Debate: The Battle for a Business Model|url=http://www.linuxinsider.com/story/66807.html|publisher=Linux Insider|accessdate=28 March 2013}}</ref>
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 many open-source software companies.<ref name=li-opencore>{{cite web|title=Open Core Debate: The Battle for a Business Model|url=http://www.linuxinsider.com/story/66807.html|publisher=Linux Insider|accessdate=28 March 2013}}</ref> The model has become popular and used by most of the largest commercial open source software (COSS) companies, as tracked by the Commercial Open Source Software Index (COSSI), which is a public list of such COSS companies that have reached $100 million or more in revenue.<ref>{{Cite web|url=https://docs.google.com/spreadsheets/d/17nKMpi_Dh5slCqzLSFBoWMxNvWiwt2R-t4e_l7LPLhU/edit?usp=embed_facebook|title=COSSI: $100M+ Revenue Commercial Open-Source Software Company Index|website=Google Docs|language=en-US|access-date=2019-09-11}}</ref>


==Use of contributor license agreements==
==Use of contributor license agreements==
Line 31: Line 31:
==Examples==
==Examples==
*[[Apache Kafka|Kafka]], a data streaming service under the Apache 2.0 license, is the open-source core to the company, Confluent, which issues a Confluent Community License, a source-available license that governs additional features in the Confluent Platform.<ref>{{Cite web|url=https://www.confluent.io/confluent-community-license-faq|title=Confluent Community License FAQ|website=Confluent|language=en-US|access-date=2019-09-09}}</ref>
*[[Apache Kafka|Kafka]], a data streaming service under the Apache 2.0 license, is the open-source core to the company, Confluent, which issues a Confluent Community License, a source-available license that governs additional features in the Confluent Platform.<ref>{{Cite web|url=https://www.confluent.io/confluent-community-license-faq|title=Confluent Community License FAQ|website=Confluent|language=en-US|access-date=2019-09-09}}</ref>
*[[Apache Spark|Spark]], a distributed data analytics cluster-computing framework under the Apache 2.0 license, is the open-source core to the company, [[Databricks]], which builds the proprietary Databricks Unified Analytics Platform product on top of Spark.<ref>{{Cite web|url=https://databricks.com/spark/comparing-databricks-to-apache-spark|title=Comparing Databricks to Apache Spark|website=Databricks|language=en-US|access-date=2019-09-11}}</ref>
*[[Apache Cassandra|Cassandra]], an open-source database under the Apache 2.0 license, is the core to the company, [[DataStax|Datastax]], which issues enterprise subscription license for additional management and security features inside DataStax Enterprise.<ref>{{Cite web|url=https://www.datastax.com/terms/product-specific-license-terms|title=Product Specific License Terms {{!}} DataStax|date=2018-02-21|website=DataStax: Active Everywhere, Every Cloud {{!}} Hybrid Cloud {{!}} Apache Cassandra {{!}} NoSQL|language=en-US|access-date=2019-09-09}}</ref>
*[[Apache Cassandra|Cassandra]], an open-source database under the Apache 2.0 license, is the core to the company, [[DataStax|Datastax]], which issues enterprise subscription license for additional management and security features inside DataStax Enterprise.<ref>{{Cite web|url=https://www.datastax.com/terms/product-specific-license-terms|title=Product Specific License Terms {{!}} DataStax|date=2018-02-21|website=DataStax: Active Everywhere, Every Cloud {{!}} Hybrid Cloud {{!}} Apache Cassandra {{!}} NoSQL|language=en-US|access-date=2019-09-09}}</ref>
*[[Instructure]]'s Canvas learning management software.{{citation needed|date=October 2013}}
*[[Instructure]]'s Canvas learning management software.{{citation needed|date=October 2013}}

Revision as of 05:33, 11 September 2019

"Open core" and "COSS" redirect here. For the open-source hardware community, see OpenCores. For railway term, see Controller of site safety.
For broader coverage of this topic, see Business models for open-source software.
GitLab Community Edition

The open-core model is a business model for the monetization of open-source software, which may or may not be originally created for the purpose of commercialization. Open-source software developed by existing companies to solve internal technological challenges (e.g. Apache Kafka by LinkedIn), as academic research (e.g. Apache Spark by Berkeley AMPLab), and by an individual (e.g. Git by Linus Torvald) have all been commercialized eventually with an open-core model. 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 open-source “core” is often sufficient in solving specific technical pain points of individual developers or small teams, while the “proprietary” layer around the core is needed to meet the business requirements of teams or large scale commercial or enterprise-grade deployments, such as security, auditing, and regulatory compliance; for example, Hashicorp's enterprise offering around the open-source software, Vault.[4]

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 many open-source software companies.[5] The model has become popular and used by most of the largest commercial open source software (COSS) companies, as tracked by the Commercial Open Source Software Index (COSSI), which is a public list of such COSS companies that have reached $100 million or more in revenue.[6]

Use of contributor license agreements

Some open-core products require their contributors to sign a contributor license agreement, which either dictates 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 is in contrast with 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.[7][8][9]

Examples

  • Kafka, a data streaming service under the Apache 2.0 license, is the open-source core to the company, Confluent, which issues a Confluent Community License, a source-available license that governs additional features in the Confluent Platform.[10]
  • Spark, a distributed data analytics cluster-computing framework under the Apache 2.0 license, is the open-source core to the company, Databricks, which builds the proprietary Databricks Unified Analytics Platform product on top of Spark.[11]
  • Cassandra, an open-source database under the Apache 2.0 license, is the core to the company, Datastax, which issues enterprise subscription license for additional management and security features inside DataStax Enterprise.[12]
  • Instructure's Canvas learning management software.[citation needed]
  • 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.[13]
  • Elasticsearch's core, which includes Elasticsearch, Kibana, Logstash and Beats, is under an Apache 2.0 license, while additional plugins are distributed under Elastic's own proprietary license.[14]
  • Eucalyptus, private cloud software, has a proprietary enterprise edition which provides additional features.[15][16][17]
  • GitLab CE (Community Edition) is under a MIT-style open source license,[18] while GitLab EE (Enterprise Edition) is under a commercial license.[19]
  • Neo4j CE (Community Edition) is under GPLv3, while Neo4j EE (Enterprise Edition) is under a commercial license, providing additional features including clustering and hot backups.
  • Redis is under a 3-clause BSD open source license,[20] while Redis Labs offers Redis Enterprise is under a commercial license which provides additional features including a search engine and JSON support.[21]

A new variation of the practice emerged in 2018 among several open core products intended for server-side use, under which there are restrictions on making the software available as part of a service offered to third-parties (targeting, in particular, use of the software by cloud application service providers such as Amazon Web Services, which create proprietary services built around the components, but with what they perceive to be inadequate compensation or contributions back to the software). MongoDB changed its license from the GNU Affero General Public License (a variation of the GPL which requires that the software's source code be offered to those who use it as a service over a network) to a modified version of the GNU General Public License version 3 titled the "Server Side Public License", where the source code of the entire service must be released under the same license if it incorporates an SSPL-licensed component. Several major Linux distributions dropped MongoDB after the change, considering the new license to be discriminatory against commercial use. Redis Labs made its Redis plugins subject to the "Commons Clause", a restriction on sale of the software on top of the existing Apache License terms. After criticism, this was changed in 2019 to the "Redis Source Available License", a non-free license which restricts sale of the software as part of "a database, a caching engine, a stream processing engine, a search engine, an indexing engine or an ML/DL/AI serving engine"[22][23][24][25][26]

See also

References

  1. ^ Phipps, Simon (July 2012). Open Source Strategies for the Enterprise. O'Reilly Media. ISBN 978-1-4493-4117-6.
  2. ^ Riehle, Dirk (2009). "The Commercial Open Source Business Model". Value Creation in e-Business Management. Springer Verlag. pp. 18–30. {{cite conference}}: Cite has empty unknown parameter: |coauthors= (help); Unknown parameter |booktitle= ignored (|book-title= suggested) (help)
  3. ^ Wasserman, Anthony I. (2011). "How the Internet transformed the software industry". Journal of Internet Services and Applications. 2 (1): 11–22. doi:10.1007/s13174-011-0019-x. ISSN 1867-4828. Some companies have only a single version of their software, while others follow an "open core" model, providing a community release of the core version, and offering proprietary premium features using a commercial license.
  4. ^ HashiCorp. "HashiCorp Vault: Enterprise Pricing, Packages & Features". HashiCorp: Infrastructure enables innovation. Retrieved 2019-09-11.
  5. ^ "Open Core Debate: The Battle for a Business Model". Linux Insider. Retrieved 28 March 2013.
  6. ^ "COSSI: $100M+ Revenue Commercial Open-Source Software Company Index". Google Docs. Retrieved 2019-09-11.
  7. ^ "MySQL mistake is a wake-up call on open source ownership". InfoWorld. Retrieved 11 September 2015.
  8. ^ "FSFE welcomes KDE's adoption of the Fiduciary Licence Agreement (FLA)". 2008-08-22.
  9. ^ "6.1 Copyright Papers". Retrieved 2011-01-03.
  10. ^ "Confluent Community License FAQ". Confluent. Retrieved 2019-09-09.
  11. ^ "Comparing Databricks to Apache Spark". Databricks. Retrieved 2019-09-11.
  12. ^ "Product Specific License Terms | DataStax". DataStax: Active Everywhere, Every Cloud | Hybrid Cloud | Apache Cassandra | NoSQL. 2018-02-21. Retrieved 2019-09-09.
  13. ^ "Open core or dual licensing? The example of MySQL". The H. Retrieved 11 September 2015.
  14. ^ "War Unfolding for Control of Elasticsearch". Datanami. 2019-03-12. Retrieved 2019-09-09.
  15. ^ Bort, Julie (18 April 2012). "This Startup That Angered A Lot Of Open Source Fans Just Got $30 Million In Funding". Business Insider. Retrieved 19 February 2016. It was one of the first commercial companies to champion a concept called "open core."
  16. ^ Bort, Julie (22 June 2010). "Marten Mickos says open source doesn't have to be fully open". Network World. Retrieved 19 February 2016. "We deliver a fully functional cloud with Eucalyptus software. You can download it on a GPL v3 license. But, additionally, we provide enterprise features only if you pay for them ... it's open core," he says.
  17. ^ Jackson, Jacob. "Eucalyptus Strengthens Its Back End". PCWorld. Retrieved 19 February 2016. To make money, Eucalyptus Systems uses an open-core business model, offering one version of the software free through an open-source license and selling a commercial version with support and additional features ...
  18. ^ "CONTRIBUTING.md · master · GitLab.org / GitLab Community Edition". GitLab. Retrieved 2018-06-05.
  19. ^ "GitLab Enterprise Edition license change". GitLab. 2014-02-11. Retrieved 2018-06-05.
  20. ^ "Redis license and trademark information". redis.io. Retrieved 2018-08-24.
  21. ^ "Licenses". Retrieved 2018-08-24.
  22. ^ Vaughan-Nichols, Steven J. "Redis Labs drops Commons Clause for a new license". ZDNet. Retrieved 2019-08-01.
  23. ^ "When Open Source Software Comes With a Few Catches". Wired. ISSN 1059-1028. Retrieved 2019-08-01.
  24. ^ Vaughan-Nichols, Steven J. "MongoDB "open-source" Server Side Public License rejected". ZDNet. Retrieved January 17, 2019.
  25. ^ "MongoDB's licensing changes led Red Hat to drop the database from the latest version of its server OS". GeekWire. January 16, 2019. Retrieved January 17, 2019.
  26. ^ Baer, Tony. "It's MongoDB's turn to change its open source license". ZDNet. Retrieved 2019-08-01.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Open-core_model&oldid=915093933"