The short answer
Most open-source AI tools in our catalog use permissive licenses, MIT or Apache 2.0, which allow commercial use with few conditions. A few use AGPL-3.0, which requires sharing changes if you offer a modified version as a network service, and some are source-available rather than open source, such as Arize Phoenix under the Elastic License 2.0. Several 'open core' projects add a separate license for enterprise features. Check the license before you build a product on top of a tool.
| License type | What it generally allows | Examples in our catalog |
|---|---|---|
| MIT | Use, modify and sell, keeping the copyright and license notices | llama.cpp, OpenCode, Kilo Code, OpenHands, Langflow |
| Apache 2.0 | Like MIT, plus an explicit patent grant and notice requirements | vLLM, Unsloth (core), goose, Qdrant, Milvus, Chroma, Mem0, Letta, Jan |
| AGPL-3.0 | Share source of modified versions, including when offered over a network | Firecrawl, Skyvern, Unsloth (optional studio/* and unsloth_cli/* files) |
| Open core | Permissive core (MIT or Apache 2.0), enterprise directories under a commercial license | Langfuse, Activepieces, Tabby |
| Source-available | Code is public, but the license restricts some uses | Arize Phoenix (Elastic License 2.0), Open WebUI (branding terms), Weaviate (BSD-3-Clause and Weaviate License) |
Read this first
This guide summarizes licenses as stated in each project's repository on November 2, 2026. It is not legal advice; for a product decision, read the license text and ask a lawyer.
Permissive licenses: MIT and Apache 2.0
MIT and Apache 2.0 let you use, modify and redistribute the software, including in commercial products, as long as you keep the required notices. Apache 2.0 also includes an explicit patent license. Most of the open-source inference and data tools in our catalog use one of these two, including llama.cpp (MIT), vLLM (Apache 2.0), Qdrant (Apache 2.0) and OpenCode (MIT).
Jan also uses Apache 2.0. Its LICENSE file requests attribution in user-facing documentation and materials where appropriate.
Copyleft for network services: AGPL-3.0
AGPL-3.0 requires that if you modify the software and let people use it over a network, you make your modified source available to them. Firecrawl and Skyvern use AGPL-3.0 for their open-source editions. Using them as separate services is common; building them into a closed product needs more care.
Unsloth keeps its core under Apache 2.0, but its LICENSE identifies the optional studio/* and unsloth_cli/* files as AGPLv3. Check which parts you are installing.
Open core: one repository, two licenses
Open-core projects keep their core under a permissive license and enterprise directories under a commercial license. Langfuse and Activepieces use MIT for the core; Tabby uses Apache 2.0. The open parts still require compliance with their license terms, and the enterprise parts have separate terms for production use.
Langfuse's enterprise license covers ee/, web/src/ee/, worker/src/ee/ and, since October 23, 2026, packages/shared/src/server/ee/. Activepieces separates packages/ee/ and packages/server/api/src/app/ee; Tabby separates ee/. Read the license for the directory you plan to use.
Source-available is not the same as open source
Arize Phoenix is licensed under the Elastic License 2.0, which restricts offering it to third parties as a hosted or managed service that exposes a substantial set of its features.
Open WebUI added its branding clause in v0.6.6 (April 2025). Clause 4 exempts deployments or distributions with no more than 50 end users, defined as individual natural persons with direct access to the application, within any rolling 30-day period. Above that threshold, branding must stay unless the copyright holder gives specific prior written permission or an enterprise license expressly permits the change. Materials governed by prior licenses retain their original terms.
Weaviate licenses code outside wl/ under BSD-3-Clause. Code in wl/ and its subdirectories is only available under a separate enterprise license, the Weaviate License, and those enterprise features are enabled with a license key.
These restrictions matter if you resell the software, host it for others or rebrand it.
Before you build on an open-source AI tool
Read the LICENSE file in the repository, not the marketing page. Check whether the features you need sit in an enterprise directory. If you will host the tool for customers, check for AGPL or source-available terms. Record the license and version you adopted, since licenses can change in later releases.
An acquisition does not necessarily change the license. ClickHouse acquired Langfuse in January 2026 and said the core would keep its existing MIT license. The current LICENSE names ClickHouse, Inc. as copyright holder and still uses MIT for the core, with the enterprise directories licensed separately.
Sources & method
Official documentation was checked on 2026-11-02. Selection advice is our assessment. Interfaces and requirements may change; check the linked source for the version you intend to use.
- MIT License (Open Source Initiative)
- Apache License 2.0 (Open Source Initiative)
- GNU AGPL v3 (Open Source Initiative)
- Elastic License 2.0
- Open WebUI license
- llama.cpp: LICENSE
- OpenCode: LICENSE
- Kilo Code: LICENSE
- OpenHands: LICENSE
- Langflow: LICENSE
- vLLM: LICENSE
- Unsloth: LICENSE
- goose: LICENSE
- Qdrant: LICENSE
- Milvus: LICENSE
- Chroma: LICENSE
- Mem0: LICENSE
- Letta: LICENSE
- Jan: LICENSE
- Firecrawl: LICENSE
- Skyvern: LICENSE
- Langfuse: LICENSE
- Activepieces: LICENSE
- Tabby: LICENSE
- Arize Phoenix: LICENSE
- Open WebUI: LICENSE
- Weaviate: LICENSE
- Tabby: Enterprise License
- Langfuse: Enterprise License
- Activepieces: Enterprise License
- ClickHouse: Langfuse acquisition and unchanged MIT core license
How SOTA reviews projects · Suggest a correction · Download the evaluation checklist