Citation and evidence

Open core

27 min full readUpdated 59 references

This article's verification

Report a problem with this article

Edit article
More

Use this article

Raw MarkdownExplore connections

Improve this page

Revision historyDiscuss this article

Topics

Developer ToolsOpen Source AISoftware Development

Cite this article

Open core is a business model in which a company publishes the main part of a software product under an open-source license and sells additional features under a proprietary license, often together with a hosted version of the product.[2][3] The Open Source Initiative (OSI) describes it as "a business strategy: basic version is FOSS, advanced version is proprietary".[2] The name was proposed in a blog post of August 29, 2008, in which Andrew Lampitt suggested calling one form of dual licensing "open-core licensing"; two days later he credited the model itself to two people who had devised it at Jaspersoft.[1]

GitLab describes its own business in these terms, and Elastic used the phrase for its commercial X-Pack extensions.[4][6] Several single-vendor companies that sold commercial editions or hosted services beside an open-source core, including MongoDB, Elastic, HashiCorp and Redis, later changed the license of the core itself to source-available terms, and two of them have since added an open-source option again.[19][16][21][25][17][26] In artificial intelligence, the developer tool Langfuse describes itself as an open core project, LiteLLM and Weaviate likewise keep commercially licensed enterprise code in a marked directory beside an open-source core, and one commentator has applied the term by analogy to open-weight models whose licenses require large hosting businesses to negotiate with the developer.[31][32][35][37][47]

The model has been disputed since the term appeared. Posts on the OSI's board blog and free-software advocates have argued that an open-core vendor is a proprietary software company and that customers of the paid edition get none of the benefits of open source.[14][10][12] Vendors reply that the paid extensions fund the open-source work, and the researcher Dirk Riehle notes that the single-vendor model to which open core belongs has long dominated venture capital funding of open-source software firms.[4][6][3]

How the model works

Core and extensions

Riehle, who studies commercial open source, places open core among the strategies of what he calls single-vendor open source firms: companies that exclusively own a piece of software, publish it under an open-source license and earn money from complementary products and services. In his description, a vendor "withholds some functionality from the open source version and provides this functionality only as part of a paid-for version", and the distinction "between an open source core and non-open-source extensions that customers pay for has been called the open core model"; his general term for it is intellectual property modularity.[3] He contrasts such firms with two other kinds of open-source business, service and support firms and distributors, which typically do not own the software they work with.[3]

The split is usually visible in the source repository. GitLab's top-level LICENSE file applies the MIT License to everything outside a few named directories, chiefly ee/, and the license in that directory allows production use only with a valid GitLab Enterprise Edition subscription.[5][55] Langfuse marks its commercial code with ee/ directories in the same way, LiteLLM uses litellm/enterprise/, Weaviate uses wl/, and in Elasticsearch the code licensed solely under the Elastic License 2.0 sits in the x-pack folder.[32][35][37][7] The paid features often ship in the same build as the free ones and are switched on with a license key.[33][36][38]

Because the vendor sells the code under terms other than the public license, it needs the right to do so. The OSI's guidance says this usually means being the sole author or having contributors sign a contributor license agreement.[2]

What goes into the paid tier varies. GitLab says it decides by asking who cares most about a feature: "If the likely buyer is an individual contributor the feature will be open source, otherwise it will be source-available (proprietary)."[4] In two of the AI tools described below, Langfuse and LiteLLM, the paid features are mostly administrative and security functions such as SCIM user provisioning, audit logs and data retention controls. Langfuse keeps regular single sign-on in its MIT-licensed code, while LiteLLM requires an Enterprise license for single sign-on beyond five users.[31][33][36]

Open core is one of several ways of earning money from software whose source is public, and vendors often combine them.[3]

ModelWhat the public getsWhat the vendor sells
Open coreA core product under an open-source license [2]Proprietary extensions, often with support and hosting [2][3]
Dual licensing, or selling exceptionsThe whole program, usually under a copyleft license [2][8]The same code under different terms, for example for use inside proprietary products [2][8]
Support and servicesA community project that the firm does not necessarily own [3]Support and consulting [3]
Hosted serviceThe software itself [3]Operation of the software in the vendor's cloud [3]
Delayed open sourceReadable source that converts to an open-source license on a later date [9]Production use beyond what the license grants [9]
Source-available coreReadable source under a license that restricts use [42]Commercial rights and enterprise features [42]

Expanded article table

Lampitt presented open core as a variety of dual licensing, in which the commercial license covers "a super-set of the open source product".[1] Others separate the two. Richard Stallman, founder of the Free Software Foundation, accepts the sale of exceptions to the GNU General Public License, where the same code remains free software for everyone, but treats proprietary extensions as a different matter: "An extension or a modified version that is only available under a proprietary license is proprietary software, pure and simple, and just as wrong as any other proprietary software."[8] MariaDB, which owns the text and trademark of the Business Source License, markets that license as "a new alternative to closed source or open core licensing models" because all of the code is published and each version later becomes open source.[22][9] GitLab makes the opposite choice and promises not to release features to its open-source edition after a fixed delay.[4]

Origin of the term

Lampitt's post, published on his blog "Lampitt or Leave It", was titled "Open-Core Licensing (OCL): Is this Version of the Dual License Open Source Business Model the New Standard?". It started from a list of commercial open-source business models by Marten Mickos of MySQL and took up the sixth item, "Commercial Extensions". Lampitt wrote: "I propose to rename this #6 dual license strategy as 'open-core licensing', to remove confusion and promote a great business model for open source communities, paying customers, and vendors alike."[1]

The model he outlined had a core under the GPL, a fee for embedding that core in closed-source products, and an annual commercial subscription that "includes: indemnity, technical support, and additional features and/or platform support". He argued that a new name would defuse accusations of "bait and switch" against vendors that added paid features, and that revenue from services alone "does not scale well for a software vendor". He named Sugar, Jaspersoft, Zimbra and Talend as companies already using the model, and left two questions open: whether the code of the paid extensions should be viewable, and whether paid features should pass to the GPL after 18 to 24 months.[1]

Two days later Lampitt added a note saying that Barry Klawans and Paul Doscher "deserve credit for being the ones that devised the OCL business model that I am describing" while they were at Jaspersoft, taking inspiration from MySQL and Sugar. Matt Aslett commented on the post that the same model had also been called "Split Licensing".[1]

In September 2009 Simon Phipps wrote on the OSI's blog about "the 'open core' view" that any business with an open-source element could be called an open-source business. Bradley M. Kühn wrote the following month that there had been "some debate recently" about open-core business models, and in July 2010 a post on the OSI's blog referred to a "debate in the press about 'Open Core'".[11][10][14] Vendors adopted the word too. Shay Banon, the original author of Elasticsearch, wrote in February 2018 that offering high-value features as commercial extensions to the core, a model "sometimes called 'open core'", was what had led to the company's X-Pack product.[6]

Open core and relicensing in general software

GitLab

GitLab's handbook states: "We have an open core business model and generate almost all our revenue with subscriptions to paid tiers." The company describes the paid code as source-available and proprietary, and the Community Edition as MIT-licensed.[4] It publishes a list of "stewardship" promises about the open-source edition, among them that an open-source feature will not be moved to a paid tier, that the open-source codebase will contain no artificial limits, that most new features made by the company will be open source, and that proprietary and open-source code will be kept in clearly separate places.[4] As of November 2026 the license file in GitLab's repository still follows that structure.[5]

Elastic

Elastic offered proprietary features for Elasticsearch and Kibana, some paid and some free, as X-Pack while the core was under the Apache License 2.0. On February 27, 2018 Banon announced that the X-Pack source code would be published under a separate Elastic License so that users could read it and contribute, with an Apache-only distribution still available.[6] On January 14, 2021 the company changed the core as well: from version 7.11 the Apache-licensed code would be offered under a choice of the Server Side Public License (SSPL) or the Elastic License, a step Banon said was aimed at cloud providers that offered the products as a service.[16] Amazon Web Services responded on April 12, 2021 with OpenSearch, an Apache-licensed fork derived from version 7.10.2. The project also became the home of AWS's earlier Open Distro for Elasticsearch, which includes features such as enterprise security, alerting and machine learning.[18]

On August 29, 2024 Banon announced that Elastic would add the GNU Affero General Public License (AGPL) as a further option. "We had issues with AWS and the market confusion their offering was causing", he wrote of the 2021 change, adding that the company was "adding another option, and not removing anything".[17] As of November 2026 the repository's default is a triple license (AGPL version 3, SSPL or Elastic License 2.0), and the x-pack folder remains under the Elastic License 2.0 alone, so the repository still separates code under the default licenses from code available only under the Elastic License.[7]

Relicensing of the core: MongoDB, HashiCorp and Redis

The three companies in this section sold commercial editions or hosted services beside an open-source core and later changed the license of the core. Riehle lists MongoDB and Redis Labs among the current generation of single-vendor open source firms; the company statements cited here do not themselves use the term open core.[3]

MongoDB published its Community Server under the AGPL version 3 until October 16, 2018 and under its own SSPL after that date, while selling commercial licenses through MongoDB Enterprise Advanced and running the Atlas cloud service.[20][19] MongoDB's own FAQ notes that software under the SSPL "is not considered open source by the OSI".[19]

HashiCorp, which sold enterprise and cloud-managed versions of its infrastructure tools, announced on August 10, 2023 that future releases of its products would move from the Mozilla Public License 2.0 to the Business Source License 1.1, citing vendors that used its open-source code commercially without contributing back.[21] The Linux Foundation announced OpenTofu, an open-source successor to the MPL-licensed version of HashiCorp's Terraform, on September 20, 2023.[24] IBM completed its acquisition of HashiCorp on February 27, 2025, and the Terraform license file now names IBM as licensor, bars hosted or embedded offerings that compete with IBM's paid versions, and converts each release to the MPL 2.0 four years after publication.[23][22]

Redis distributed an open-source edition under the 3-clause BSD license beside its Enterprise and Cloud products. On March 20, 2024 it announced that Redis 7.4 and later would instead be offered under a choice of the Redis Source Available License version 2 or the SSPL, and acknowledged that "this change means Redis is no longer open source under the OSI definition".[25] The Linux Foundation announced Valkey, a BSD-licensed continuation of Redis 7.2.4, eight days later.[28] On May 1, 2025 Rowan Trollope announced on the company's blog that Redis 8 added the AGPL version 3 as a third option, writing that the earlier move had achieved its aim regarding cloud providers but that "the change hurt our relationship with the Redis community".[26][27]

Relicensing does not always move away from open source. Unleash, a feature-management vendor, announced on June 2, 2026 that its open-source repository would move from Apache 2.0 to the AGPL version 3 with version 8.0.0, while its Enterprise distribution stayed under a commercial license.[29]

CompanyOriginal open-source license of the coreChanges to the core licenseCore license as of November 2026
GitLabMIT (Community Edition) [4]None; GitLab says it does not use "a limiting license such as SSPL" [4]MIT outside the ee/ directories [5]
ElasticApache 2.0, before version 7.11 [16]2021: SSPL or Elastic License; 2024: AGPL added [16][17]AGPL v3, SSPL or Elastic License 2.0; x-pack Elastic License 2.0 only [7]
MongoDBAGPL v3, before October 16, 2018 [20]2018: SSPL [19]SSPL [20]
HashiCorp (IBM)MPL 2.0 [21]2023: Business Source License 1.1 [21]Business Source License 1.1, converting to MPL 2.0 after four years [22]
Redis3-clause BSD, through version 7.2 [25][27]2024: RSALv2 or SSPL; 2025: AGPL v3 added [25][26]RSALv2, SSPL or AGPL v3 [27]

Expanded article table

What happened to the forks

Dawn Foster of the CHAOSS project compared contributor data for three of these cases in a 2024 paper: Elasticsearch and OpenSearch, Redis and Valkey, and Terraform and OpenTofu. She described relicensing as a response by vendors to investor pressure, made "in the hopes of generating more revenue", and found that the resulting forks had more organizational diversity than the original projects, especially when they were created under a neutral foundation such as the Linux Foundation. She added that it was too early to judge the eventual success of either the originals or the forks.[30]

In artificial intelligence

Three different things in AI are described with open-core vocabulary and are kept apart here: open-source software with paid proprietary extensions, which fits the definition given above whether or not the vendor uses the term; source-available software, which does not; and open-weight models, where the term is at most an analogy.

Open-source AI software with proprietary extensions

Langfuse, a platform for tracing and evaluating large language model applications, states in its enterprise license file that "Langfuse is an open core project".[32] Code outside the ee/ directories is MIT-licensed; enterprise modules such as SCIM, audit logging and data retention policies need a commercial license when self-hosted.[32][33] On June 4, 2025 the company moved its remaining product features, including LLM-as-a-judge evaluations, annotation queues, prompt experiments and the playground, from the commercial tier to the MIT license, writing: "Langfuse has been an open core company from the start. Our core just expanded significantly and our periphery shrunk."[31] ClickHouse announced its acquisition of Langfuse on January 16, 2026; Langfuse said there were "no planned changes to licensing", and the license files now name ClickHouse, Inc. as copyright holder.[34][56][32]

LiteLLM, an LLM gateway, is MIT-licensed outside its litellm/enterprise/ directory. The vendor describes LiteLLM Enterprise as "a license key on the same Gateway image" that adds single sign-on, audit logs and support.[35][36]

Weaviate, a vector database, added a proprietary enterprise directory in August 2026.[37][57] Its license file now separates BSD-3-Clause code from a wl directory that is "only available under a separate enterprise license", under a Weaviate License Agreement dated August 26, 2026. The company says its Enterprise Edition is the same code as the Community Edition with added production features, starting with shard self-recovery and deduplicated backups, unlocked by a license key and included in every Weaviate Cloud plan.[37][57][38]

Open-source tools with a separate commercial product, and source-available tools

Other AI companies keep the open-source project free of gated features and sell something beside it. The LangChain framework is MIT-licensed, while the company's LangSmith platform is a commercial service whose self-hosted version is "an add-on to the Enterprise plan" and needs a license key.[39][40] The Ollama repository is MIT-licensed, and the company sells paid plans for models run in its cloud.[41][58]

A third group publishes its code under licenses that the OSI has not approved, so the public part is not an open-source core. n8n uses its own Sustainable Use License and keeps files marked .ee under a separate enterprise license.[42] Dify uses a modified Apache License 2.0 that requires a commercial license for multi-tenant services.[44] Open WebUI uses a BSD-style license with an added clause that forbids removing its branding in deployments with more than 50 users unless the licensee has written permission or an enterprise license.[45] The AutoGPT repository mixes the two approaches: its autogpt_platform folder is under the PolyForm Shield License and everything else is under the MIT License.[43] These cases are covered in the source-available article.

ProjectPublic licenseWhat is paid or restrictedArrangement
LangfuseMIT outside ee/ [32]Enterprise modules; Langfuse Cloud [33]Open core, in the project's own words [32]
LiteLLMMIT outside litellm/enterprise/ [35]Enterprise features enabled by license key [36]Open-source core with a commercially licensed enterprise directory
WeaviateBSD-3-Clause outside wl/ [37]Enterprise Edition; Weaviate Cloud [38]Open-source core with an enterprise directory under a separate license
LangChainMIT [39]LangSmith platform [40]Separate commercial product
OllamaMIT [41]Paid cloud plans [58]Hosted service
n8nSustainable Use License [42].ee files under an enterprise license [42]Source-available core
DifyModified Apache 2.0 with added conditions [44]Commercial license for multi-tenant use [44]Source-available
AutoGPTMIT, except autogpt_platform [43]Platform code under PolyForm Shield [43]Open source plus source-available

Expanded article table

Open-weight models

Model developers that publish trained weights often also sell API access, larger closed models or commercial licenses. Describing this as open core is an analogy, drawn by the commentator quoted below, and not a use of the term in its software sense. Under the OSI's Open Source AI Definition, an open-source AI system requires training-data information and the complete code as well as the parameters, each under OSI-approved terms, and the OSI states that open weights "differ significantly from Open Source AI".[53][54] This article therefore calls such models open-weight.

David Gray Widder, Meredith Whittaker and Sarah Myers West wrote in Nature in 2024 that companies such as Hugging Face and Stability AI base their business not on licensing proprietary models but on "charging for extra features and labour on top of open models", such as API access, training on custom data, and security and technical support.[46]

Matt Asay, an InfoWorld contributing writer and emeritus OSI board member, drew the open-core comparison directly in August 2026 under the heading "'Open core' comes to open weights". He noted that developers such as Alibaba, with its Qwen models, and Z.ai release open-weight models while charging for proprietary models, cloud compute or API access, and argued that model developers were starting to do what database vendors had done to cloud providers: "We're starting to see the same dynamic with model weights, perhaps ushering in the latest instantiation of so-called open core models."[47] His examples were licenses that leave weights downloadable but require large hosting businesses to negotiate. The Kimi K3 license from Moonshot AI, for instance, grants broad rights to use, modify, distribute and sell the model in wording close to that of the MIT License, but adds conditions: if the licensee or one of its affiliates operates a model-as-a-service business, and their aggregate revenue exceeds 20 million US dollars over any 12 consecutive months, the licensee must sign a separate agreement with Moonshot AI before any commercial use. Internal use, and use through Moonshot AI's official products or certified inference partners, are exempt.[47][49] Asay's other example was MiniMax M3, which he said requires prior authorization once products or services built on the model exceed 20 million dollars in annual revenue.[47] Asay contrasted these with models released under the plain MIT License, and wrote that the market was dividing between models meant to commoditize the model layer and "models designed to win adoption while preserving tollbooths around the most valuable commercial uses".[47]

Some model releases follow the older dual-licensing pattern instead. When Mistral AI released Codestral on May 29, 2024, it published the weights under a non-production license for research and testing and offered commercial licenses on request.[48] No part of such a release is under an open-source license, so it falls outside the definition of open core used in this article.

Criticism

Early criticism came from free-software advocates. Kühn wrote in October 2009 that open core was "a glorified shareware situation" in which users must "take a proprietary license or be stuck with cripple-ware". He objected in particular to pairing the model with the GPL and copyright assignment, which lets only the copyright-holding company build proprietary add-ons: "It creates two classes of users: those precious few that can proprietarize and subjugate others, and those that can't." His advice to users of such codebases was to fork them and refuse to assign copyright. He later added a note that the term should be abandoned in favor of "proprietary relicensing".[10]

In July 2010 two posts on the OSI Board Blog addressed the subject.[15] The first, published on July 17 under the byline "nelson", argued that open-core vendors could not transfer the benefits of open-source development to their proprietary editions: "The more they differentiate their proprietary version from the open source version, the more obvious it becomes that the open source effect isn't contributing to the proprietary version. The less they differentiate it, the less reason to buy the proprietary version."[13] The second, published on July 20 under the byline "acoliver", stated that "'Open Core' has NOTHING to do with 'Open Source'", that an open-core company "is a proprietary software vendor like any other", and that vendors who imply their proprietary software has the advantages of open source "are engaging in deception".[14]

Simon Phipps, an OSI director from April 2010, published "Open Core Is Bad For You" after Mickos described his new company Eucalyptus as open core.[15][12] Phipps accepted that the core package can be used freely but argued that a business will usually need the paid extras in production, and that at that point it depends on one supplier: "the open core business model induces dependency on closed software and lock-in to a vendor". He called the model "a bait-and-switch".[12]

GitLab's handbook says "There are valid criticisms of Open Core" and lists four raised by Deb Bryant of Red Hat at the Open Core Summit in 2019: participation is constrained because vendors may decline contributions that duplicate paid features, premium features create vendor lock-in, the community is treated as a marketing tool, and customers fear confusing or unsanctioned licenses entering their business.[4] MariaDB makes a similar lock-in argument when promoting the Business Source License as an alternative.[9]

A separate concern is what happens later. Foster's study of the relicensing cases above notes that such events and the forks that follow them "can be disruptive to the organizations and individuals using these open source projects".[30]

Defenses

Lampitt's original argument was that everyone gains: customers can use a GPL core permanently and free of charge, with what he called a kind of "guaranteed escrow" of the source code if the vendor fails, and the vendor obtains a revenue source that scales better than services.[1]

Banon made a related case in 2018. Support-only business models, he wrote, "trend towards a conflict between what's best for the user and what's best for the company", because a company that lives on support has less reason to make its software easier to use, while a separate enterprise edition "results in a fracturing of the community". Commercial extensions to a single shared core were, in his account, what allowed Elastic to spend most of its engineering time on the open-source products.[6]

GitLab answers Bryant's four criticisms point by point in its handbook and argues that the open-source edition benefits from the company's revenue through new open-source features, security fixes, release management and packaging.[4] Langfuse gave a competitive reason for enlarging its core in 2025: to be "the first choice in the market", the free version had to cover the whole development cycle.[31]

Riehle's assessment is economic. He writes that the single-vendor model, whose strategies include open core, "has long dominated venture capital funding for open source software firms", and that no other open-source business model has produced as many companies with comparable returns for investors. He also identifies the model's central difficulty: "how to turn non-paying users into paying customers".[3] Open Core Ventures, a firm founded by GitLab founder Sid Sijbrandij to start companies around existing open-source projects, argues that commercialization "funds the maintainers and governance that make open source sustainable".[51]

Relation to source-available licensing and openwashing

Open core and source-available licensing overlap in two ways. First, the proprietary half of an open-core product is often source-available: Lampitt's post already discussed "viewable code" for commercial extensions, GitLab calls its paid features source-available, and in February 2026 Open Core Ventures published a license written specifically "to protect the proprietary components of an open core codebase while enabling code access".[1][4][52] Second, several vendors later applied source-available terms to the core itself, as described above. After such a change the product falls outside the definition given above, because its core is no longer under an open-source license, unless an open-source option is restored as Elastic and Redis did.[7][27]

The dispute over what such products may be called is related to openwashing, a word Michelle Thorne defined in 2009 as "to spin a product or company as open, although it is not".[50] The 2010 OSI blog post quoted above directed its charge of deception at vendors who implied that proprietary editions carried the advantages of open source.[14] In January 2021 the OSI made the same charge about relicensed cores, calling the SSPL a "fauxpen" license and stating: "It's deception, plain and simple, to claim that the software has all the benefits and promises of open source when it does not."[59] In AI the equivalent argument is about calling open-weight releases "open source"; the open-source AI and openwashing articles cover it.

Continue reading

More to read

Topics:Developer ToolsOpen Source AISoftware Development

References

  1. ^1 ^2 ^3 ^4 ^5 ^6 ^7Andrew Lampitt. "Open-Core Licensing (OCL): Is this Version of the Dual License Open Source Business Model the New Standard?". Lampitt or Leave It (blog), August 29, 2008 (archived copy, September 15, 2008). web.archive.org/...open-core-licen
  2. ^1 ^2 ^3 ^4 ^5 ^6 ^7Open Source Initiative. "What's dual licensing?". opensource.org, September 14, 2026. opensource.org/...whats-dual-licensing
  3. ^1 ^2 ^3 ^4 ^5 ^6 ^7 ^8 ^9 ^10 ^11 ^12Dirk Riehle. "Single-Vendor Open Source Firms". Computer, vol. 53, no. 4, pp. 68-72, April 2020. doi:10.1109/MC.2020.2969672. Author's version, "Single-Vendor Open Source Firms (and Their Intellectual Property Strategies)": dirkriehle.com/...intellectual-property-strategies
  4. ^1 ^2 ^3 ^4 ^5 ^6 ^7 ^8 ^9 ^10 ^11GitLab. "Our stewardship of GitLab". The GitLab Handbook, last modified August 27, 2026. handbook.gitlab.com/...stewardship
  5. ^1 ^2 ^3GitLab Inc. "LICENSE". gitlab-org/gitlab repository, read November 19, 2026. gitlab.com/...LICENSE
  6. ^1 ^2 ^3 ^4 ^5Shay Banon. "Doubling Down on Open". Elastic Blog, February 27, 2018. elastic.co/...doubling-down-on-open
  7. ^1 ^2 ^3 ^4Elastic. "LICENSE.txt". elastic/elasticsearch repository, read November 19, 2026. github.com/...LICENSE.txt
  8. ^1 ^2 ^3Richard Stallman. "Selling Exceptions to the GNU GPL". GNU Project, Free Software Foundation. gnu.org/...selling-exceptions.en
  9. ^1 ^2 ^3 ^4MariaDB. "MariaDB Business Source License (BSL)" (frequently asked questions). mariadb.com, read November 19, 2026. mariadb.com/bsl-faq-mariadb
  10. ^1 ^2 ^3Bradley M. Kühn. "'Open Core' Is the New Shareware". ebb.org, October 16, 2009. ebb.org/...open-core-shareware
  11. ^Simon Phipps. "Mind Your Own Business (Model)". Open Source Initiative blog, September 23, 2009. opensource.org/...mind-your-own-business-model
  12. ^1 ^2 ^3Simon Phipps. "Open Core Is Bad For You". Wild Webmink, November 5, 2010 (first published in ComputerWorldUK). webmink.com/...open-core
  13. ^Open Source Initiative (post bylined "nelson"). "Why Open Core has a problem and is not a problem." OSI Board Blog, July 17, 2010 (archived copy of December 22, 2010, showing the byline). web.archive.org/...537
  14. ^1 ^2 ^3 ^4Open Source Initiative (post bylined "acoliver"). "A simple declaration about 'Open Core'". OSI Board Blog, July 20, 2010 (archived copy of July 23, 2010, showing the byline). web.archive.org/...OpenCore
  15. ^1 ^2Open Source Initiative. "OSI Board of Directors" (archived copy, July 16, 2010). web.archive.org/...board
  16. ^1 ^2 ^3 ^4Shay Banon. "Doubling down on open, Part II". Elastic Blog, January 14, 2021. elastic.co/...licensing-change
  17. ^1 ^2 ^3Shay Banon. "Elasticsearch Is Open Source. Again!". Elastic Blog, August 29, 2024. elastic.co/...elasticsearch-is-open-source-again
  18. ^Carl Meadows, Jules Graybill, Kyle Davis and Mehul Shah. "Introducing OpenSearch". AWS Open Source Blog, April 12, 2021. aws.amazon.com/...introducing-opensearch
  19. ^1 ^2 ^3 ^4MongoDB. "Server Side Public License FAQ". mongodb.com, read November 19, 2026. mongodb.com/...faq
  20. ^1 ^2 ^3MongoDB. "MongoDB Licensing". mongodb.com, read November 19, 2026. mongodb.com/...community-edition
  21. ^1 ^2 ^3 ^4Armon Dadgar. "HashiCorp adopts Business Source License". HashiCorp Blog, August 10, 2023 (archived copy, January 2, 2025). web.archive.org/...-adopts-business-source-license
  22. ^1 ^2 ^3International Business Machines Corporation. "LICENSE" (Business Source License 1.1 parameters). hashicorp/terraform repository, read November 19, 2026. github.com/...LICENSE
  23. ^IBM. "IBM Completes Acquisition of HashiCorp, Creates Comprehensive, End-to-End Hybrid Cloud Platform". IBM Newsroom, February 27, 2025. newsroom.ibm.com/...d-to-end-hybrid-cloud-platform
  24. ^The Linux Foundation. "Linux Foundation Launches OpenTofu: A New Open Source Alternative to Terraform". September 20, 2023. linuxfoundation.org/...announcing-opentofu
  25. ^1 ^2 ^3 ^4Redis. "Redis Adopts Dual Source-Available Licensing". Redis Blog, March 20, 2024. redis.io/...adopts-dual-source-available-licensing
  26. ^1 ^2 ^3Rowan Trollope. "Redis is now available under the AGPLv3 open source license". Redis Blog, May 1, 2025. redis.io/...agplv3
  27. ^1 ^2 ^3 ^4Redis. "LICENSE.txt". redis/redis repository, read November 19, 2026. github.com/...LICENSE.txt
  28. ^The Linux Foundation. "Linux Foundation Launches Open Source Valkey Community". March 28, 2024. linuxfoundation.org/...pen-source-valkey-community
  29. ^Ivar Østhus. "Evolving Our Open Source Commitment: Unleash is Moving to AGPLv3". Unleash Blog, June 2, 2026. getunleash.io/...unleash-moving-to-agplv3
  30. ^1 ^2Dawn Foster. "The New Dynamics of Open Source: Relicensing, Forks, & Community Impact". arXiv:2411.04739, November 7, 2024 (presented at the OpenForum Academy Symposium, November 13-14, 2024). arxiv.org/...2411.04739
  31. ^1 ^2 ^3 ^4Langfuse. "Doubling Down on Open Source". Langfuse Blog, June 4, 2025. langfuse.com/...-04-open-sourcing-langfuse-product
  32. ^1 ^2 ^3 ^4 ^5 ^6 ^7ClickHouse, Inc. "LICENSE" and "ee/LICENSE". langfuse/langfuse repository, read November 19, 2026. github.com/...LICENSE
  33. ^1 ^2 ^3 ^4Langfuse. "Why is Langfuse Open Source?". Langfuse Handbook, read November 19, 2026. langfuse.com/...open-source
  34. ^Ryadh Dahimene, Marc Klingen, Max Deichmann and Clemens Rawert. "ClickHouse welcomes Langfuse: The future of open-source LLM observability". ClickHouse Blog, January 16, 2026. clickhouse.com/...se-open-source-llm-observability
  35. ^1 ^2 ^3 ^4Berri AI. "LICENSE". BerriAI/litellm repository, read November 19, 2026. github.com/...LICENSE
  36. ^1 ^2 ^3 ^4LiteLLM. "Enterprise". LiteLLM documentation, read November 19, 2026. docs.litellm.ai/...enterprise
  37. ^1 ^2 ^3 ^4 ^5Weaviate. "LICENSE". weaviate/weaviate repository, read November 19, 2026. github.com/...LICENSE
  38. ^1 ^2 ^3Weaviate. "Enterprise Edition". weaviate.io, read November 19, 2026. weaviate.io/enterprise-edition
  39. ^1 ^2LangChain. "LICENSE" (MIT License). langchain-ai/langchain repository, read November 19, 2026. github.com/...LICENSE
  40. ^1 ^2LangChain. "Self-hosted LangSmith". Docs by LangChain, read November 19, 2026. docs.langchain.com/...self-hosted
  41. ^1 ^2Ollama. "LICENSE" (MIT License). ollama/ollama repository, read November 19, 2026. github.com/...LICENSE
  42. ^1 ^2 ^3 ^4 ^5n8n. "LICENSE.md". n8n-io/n8n repository, read November 19, 2026. github.com/...LICENSE.md
  43. ^1 ^2 ^3Significant Gravitas. "LICENSE". Significant-Gravitas/AutoGPT repository, read November 19, 2026. github.com/...LICENSE
  44. ^1 ^2 ^3LangGenius, Inc. "LICENSE". langgenius/dify repository, read November 19, 2026. github.com/...LICENSE
  45. ^Open WebUI Inc. "LICENSE" (Open WebUI License). open-webui/open-webui repository, read November 19, 2026. github.com/...LICENSE
  46. ^David Gray Widder, Meredith Whittaker and Sarah Myers West. "Why 'open' AI systems are actually closed, and why this matters". Nature, vol. 635, pp. 827-833, November 27, 2024. nature.com/...s41586-024-08141-1
  47. ^1 ^2 ^3 ^4 ^5Matt Asay. "Accelerating AI innovation through open weights". InfoWorld, August 18, 2026. infoworld.com/...i-innovation-through-open-weights
  48. ^Mistral AI. "Codestral". mistral.ai, May 29, 2024. mistral.ai/...codestral
  49. ^Moonshot AI. "Kimi K3 License". moonshotai/Kimi-K3 repository on Hugging Face, read November 19, 2026. huggingface.co/...LICENSE
  50. ^Michelle Thorne. "Openwashing". michellethorne.cc, March 14, 2009 (archived copy). web.archive.org/...openwashing
  51. ^Open Core Ventures. "About". opencoreventures.com, read November 19, 2026. opencoreventures.com/about
  52. ^Sid Sijbrandij and Heather Meeker. "OCV's new source available license is a simple alternative to closed-source licenses". Open Core Ventures, February 12, 2026. opencoreventures.com/...-to-closed-source-licenses
  53. ^Open Source Initiative. "The Open Source AI Definition - 1.0". opensource.org. opensource.org/...open-source-ai-definition
  54. ^Open Source Initiative. "Open Weights: not quite what you've been told". opensource.org. opensource.org/...open-weights
  55. ^GitLab Inc. "The GitLab Enterprise Edition (EE) license". gitlab-org/gitlab repository, read November 19, 2026. gitlab.com/...LICENSE
  56. ^Langfuse. "Langfuse joins ClickHouse". Langfuse Blog, read November 19, 2026. langfuse.com/...joining-clickhouse
  57. ^1 ^2Weaviate. "Weaviate License Agreement" (wl/LICENSE-WEAVIATE), posted August 26, 2026. weaviate/weaviate repository. github.com/...LICENSE-WEAVIATE
  58. ^1 ^2Ollama. "Pricing". ollama.com, read November 19, 2026. ollama.com/pricing
  59. ^Open Source Initiative. "The SSPL is Not an Open Source License". January 19, 2021. opensource.org/...pl-is-not-an-open-source-license

Improve this article

Add missing citations, update stale details, or write a clearer explanation. Anyone can edit: changes go live when you publish, and every edit is checked by an editor.

1 revision · v1 · 5,405 words · full history

Fact-checks are independent of edits: a reviewer re-verifies the article against its sources and stamps the date. How we verify

Research and drafting on this wiki are AI-assisted, under named human editorial standards. How AI is used here

Reviewer note: Independent fact-check before publication on November 19, 2026: 168 claims checked against 66 cited and independent sources; 3 material and 13 minor corrections applied before publication.

Cite this page: AI Wiki. "Open core." aiwiki.ai, updated 18 Nov 2026, fact-checked 18 Nov 2026. CC BY 4.0. https://aiwiki.ai/wiki/open_core

Edit article