{"id":7,"date":"2026-11-12T09:00:00","date_gmt":"2026-11-12T09:00:00","guid":{"rendered":"https:\/\/bestaitoolix.com\/blog\/open-source-vs-source-available\/"},"modified":"2026-11-12T09:00:00","modified_gmt":"2026-11-12T09:00:00","slug":"open-source-vs-source-available","status":"publish","type":"post","link":"https:\/\/bestaitoolix.com\/blog\/open-source-vs-source-available\/","title":{"rendered":"Open source, source-available, or proprietary? Reading a software license before you commit"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">\u201cIs it open source?\u201d used to be a yes-or-no question. It isn\u2019t anymore. A growing number of developer and infrastructure tools publish their code on GitHub under licenses that let you read it, run it, and even modify it \u2014 but restrict how you can use it commercially. Those tools are <strong>source-available<\/strong>, not open source, and the distinction can matter a great deal when you\u2019re choosing something to build on.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Three buckets<\/h2>\n\n\n\n<ul class=\"wp-block-list\"><li><strong>Open source<\/strong> \u2014 released under a license approved by the Open Source Initiative (OSI), such as MIT, Apache 2.0, GPL or MPL. You can use, modify and redistribute it, including commercially, subject to the license\u2019s conditions (for example, copyleft obligations under the GPL).<\/li><li><strong>Source-available<\/strong> \u2014 the code is public, but the license is not OSI-approved and usually restricts some commercial uses, often competing hosted offerings. Examples include the Business Source License (BUSL), the Server Side Public License (SSPL) and the Functional Source License (FSL).<\/li><li><strong>Proprietary<\/strong> \u2014 the code is not available; you get a product under commercial terms.<\/li><\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">On BestAIToolix the license model is its own field, and a tool is only flagged as open source when its license is an OSI-approved one. A public repository alone isn\u2019t enough.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The examples worth knowing<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Terraform and OpenTofu<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/bestaitoolix.com\/tools\/terraform\">Terraform<\/a> is the clearest recent case. In 2023 HashiCorp moved it from the Mozilla Public License to the Business Source License, which limits use in products that compete with HashiCorp. The code is still on GitHub, so it looks open \u2014 but it\u2019s source-available, and we record it that way. The community response was <a href=\"https:\/\/bestaitoolix.com\/tools\/opentofu\">OpenTofu<\/a>, a fork that continues under the open-source MPL 2.0. If license terms matter to your organization, that difference is a real selection criterion in the <a href=\"https:\/\/bestaitoolix.com\/categories\/infrastructure-as-code-iac-tools\">infrastructure-as-code category<\/a>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Sentry<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/bestaitoolix.com\/tools\/sentry\">Sentry<\/a> publishes its code and allows self-hosting, under the Functional Source License \u2014 a \u201cfair source\u201d license that isn\u2019t OSI-approved and that converts each release to a permissive open-source license after a delay. For most teams self-hosting for their own use, that\u2019s fine. For anyone planning to offer a competing service, it isn\u2019t. We record it as source-available.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Wazuh and Langfuse<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">For contrast, <a href=\"https:\/\/bestaitoolix.com\/tools\/wazuh\">Wazuh<\/a> (a security monitoring platform) is open source under the GPL, and <a href=\"https:\/\/bestaitoolix.com\/tools\/langfuse\">Langfuse<\/a> (LLM observability) publishes an open-source core under a permissive license alongside its paid cloud. Open source and a commercial business are not opposites \u2014 many vendors sell hosting, support or enterprise features on top of an open core.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Questions to ask before you commit<\/h2>\n\n\n\n<ol class=\"wp-block-list\"><li><strong>What exactly is the license?<\/strong> Read the LICENSE file, not the marketing page. Look up whether it\u2019s OSI-approved.<\/li><li><strong>Does it restrict your use case?<\/strong> Source-available licenses usually target competing hosted services. Internal use is often permitted \u2014 confirm it.<\/li><li><strong>Is the license per-release?<\/strong> Licenses can change for future versions. Older versions keep their old terms, which is how forks like OpenTofu become possible.<\/li><li><strong>Who governs the project?<\/strong> A foundation-hosted project and a single-vendor project carry different risks of future license changes.<\/li><li><strong>What does the paid tier add?<\/strong> With open-core products, check whether the features you need (SSO, audit logs, scale) are in the open part.<\/li><\/ol>\n\n\n\n<div class=\"wp-block-group btx-callout\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n<p class=\"wp-block-paragraph\">Not legal advice: license questions with real business impact belong with your counsel. What we can do is make the license model visible and sourced for every tool, so it\u2019s part of the comparison from the start rather than a surprise during procurement.<\/p>\n<\/div><\/div>\n","protected":false},"excerpt":{"rendered":"<p>A public GitHub repo doesn&#8217;t make a tool open source. Here&#8217;s how to tell open source from source-available, with Terraform, OpenTofu and Sentry as examples.<\/p>\n","protected":false},"author":0,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"btx_cta_url":"https:\/\/bestaitoolix.com\/categories\/infrastructure-as-code-iac-tools","btx_cta_label":"Explore infrastructure-as-code tools","btx_cta_text":"See license model and deployment options, sourced, for every IaC tool we track.","footnotes":""},"categories":[3],"tags":[8,9],"class_list":["post-7","post","type-post","status-publish","format-standard","hentry","category-pricing-licensing","tag-licensing","tag-open-source"],"_links":{"self":[{"href":"https:\/\/bestaitoolix.com\/blog\/wp-json\/wp\/v2\/posts\/7","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bestaitoolix.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/bestaitoolix.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/bestaitoolix.com\/blog\/wp-json\/wp\/v2\/comments?post=7"}],"version-history":[{"count":0,"href":"https:\/\/bestaitoolix.com\/blog\/wp-json\/wp\/v2\/posts\/7\/revisions"}],"wp:attachment":[{"href":"https:\/\/bestaitoolix.com\/blog\/wp-json\/wp\/v2\/media?parent=7"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/bestaitoolix.com\/blog\/wp-json\/wp\/v2\/categories?post=7"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/bestaitoolix.com\/blog\/wp-json\/wp\/v2\/tags?post=7"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}