business model monetizing commercial open-source software
"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 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 many open-source software companies.[4]
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.[5][6][7]
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.[8]
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.[9]
Oracle's MySQL database software is dual-licensed under a proprietary license, and the GNU General Public License (GPL); proprietary versions offer additional features and enterprise support plans.[10]
Elastic's core, which includes Elasticsearch, Kibana, Logstash and Beats, was under an Apache 2.0 license, while additional plugins are distributed under Elastic's own proprietary license.[11] In January 2021, Elastic re-licensed its software under the non-free Server Side Public License and Elastic License, which restrict use of the software as part of managed services, and circumvention of software locks on premium features.[12]
Eucalyptus, private cloud software, has a proprietary enterprise edition which provides additional features.[13][14][15]
GitLab CE (Community Edition) is under a MIT-style open source license,[16] while GitLab EE (Enterprise Edition) is under a commercial license.[17]
Neo4j CE (Community Edition) is licensed under GPL version 3, 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,[18] while Redis Labs offers Redis Modules under a Source-available software license, and Redis Enterprise under a commercial license which provides additional enterprise features such as on-the-fly scaling, replication performance tuning, and clustering support for Redis Modules.[19]
Restrictions on use in services
A new variation of the practice emerged in 2018 among several open core products intended for server-side use, seeking to control use of the product as part of a service offered to a customer. These practices, in particular, target incorporation of the software into proprietary services by cloud application service providers such as Amazon Web Services, but with what vendors perceive to be inadequate compensation or contributions back to the upstream software in return.[20][21]
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 over a network) to a modified version of GPL version 3 titled the "Server Side Public License" (SSPL), where the source code of the entire service must be released under the SSPL if it incorporates an SSPL-licensed component.[22]Bruce Perens, co-author of The Open Source Definition, argued that the SSPL violated its requirement for an open source license to not place restrictions on software distributed alongside the licensed software.[20] The Open Source Initiative (OSI) ruled that the SSPL violates the Open Source Definition and is therefore not a free software license, as it is discriminatory against commercial use.[23]Debian, Fedora, and Red Hat Enterprise Linux pulled MongoDB from their distributions after the license change, considering the new license to be in violation of their licensing policies.[22][24]
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 forbids 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".[25][21][26] The last versions of the modules licensed solely under the Apache License were forked and are maintained by community members under the GoodFORM project.[20]
^Wasserman, Anthony I. (2011). "How the Internet transformed the software industry". Journal of Internet Services and Applications. 2 (1): 11–22. doi:. 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.
^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.
^Jackson, Jacob (25 August 2010). "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 ...
8:49
