Open source, source-available, or proprietary? Reading a software license before you commit
A public GitHub repo doesn't make a tool open source. Here's how to tell open source from source-available, with Terraform, OpenTofu and Sentry as examples.
“Is it open source?” used to be a yes-or-no question. It isn’t 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 — but restrict how you can use it commercially. Those tools are source-available, not open source, and the distinction can matter a great deal when you’re choosing something to build on.
Three buckets
- Open source — 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’s conditions (for example, copyleft obligations under the GPL).
- Source-available — 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).
- Proprietary — the code is not available; you get a product under commercial terms.
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’t enough.
The examples worth knowing
Terraform and OpenTofu
Terraform 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 — but it’s source-available, and we record it that way. The community response was OpenTofu, 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 infrastructure-as-code category.
Sentry
Sentry publishes its code and allows self-hosting, under the Functional Source License — a “fair source” license that isn’t 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’s fine. For anyone planning to offer a competing service, it isn’t. We record it as source-available.
Wazuh and Langfuse
For contrast, Wazuh (a security monitoring platform) is open source under the GPL, and Langfuse (LLM observability) publishes an open-source core under a permissive license alongside its paid cloud. Open source and a commercial business are not opposites — many vendors sell hosting, support or enterprise features on top of an open core.
Questions to ask before you commit
- What exactly is the license? Read the LICENSE file, not the marketing page. Look up whether it’s OSI-approved.
- Does it restrict your use case? Source-available licenses usually target competing hosted services. Internal use is often permitted — confirm it.
- Is the license per-release? Licenses can change for future versions. Older versions keep their old terms, which is how forks like OpenTofu become possible.
- Who governs the project? A foundation-hosted project and a single-vendor project carry different risks of future license changes.
- What does the paid tier add? With open-core products, check whether the features you need (SSO, audit logs, scale) are in the open part.
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’s part of the comparison from the start rather than a surprise during procurement.