forked from langgenius/dify
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Doc/update license (langgenius#2666)
- Loading branch information
Showing
1 changed file
with
12 additions
and
10 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,24 +1,26 @@ | ||
| # Dify Open Source License | ||
| # Open Source License | ||
|
|
||
| The Dify project is licensed under the Apache License 2.0, with the following additional conditions: | ||
| Dify is licensed under the Apache License 2.0, with the following additional conditions: | ||
|
|
||
| 1. Dify is permitted to be used for commercialization, such as using Dify as a "backend-as-a-service" for your other applications, or delivering it to enterprises as an application development platform. However, when the following conditions are met, you must contact the producer to obtain a commercial license: | ||
| 1. Dify may be utilized commercially, including as a backend service for other applications or as an application development platform for enterprises. Should the conditions below be met, a commercial license must be obtained from the producer: | ||
|
|
||
| a. Multi-tenant SaaS service: Unless explicitly authorized by Dify in writing, you may not use the Dify.AI source code to operate a multi-tenant SaaS service that is similar to the Dify.AI service edition. | ||
| b. LOGO and copyright information: In the process of using Dify, you may not remove or modify the LOGO or copyright information in the Dify console. | ||
| a. Multi-tenant SaaS service: Unless explicitly authorized by Dify in writing, you may not use the Dify source code to operate a multi-tenant environment. | ||
| - Tenant Definition: Within the context of Dify, one tenant corresponds to one workspace. The workspace provides a separated area for each tenant's data and configurations. | ||
|
|
||
| b. LOGO and copyright information: In the process of using Dify's frontend components, you may not remove or modify the LOGO or copyright information in the Dify console or applications. This restriction is inapplicable to uses of Dify that do not involve its frontend components. | ||
|
|
||
| Please contact [email protected] by email to inquire about licensing matters. | ||
|
|
||
| 2. As a contributor, you should agree that your contributed code: | ||
| 2. As a contributor, you should agree that: | ||
|
|
||
| a. The producer can adjust the open-source agreement to be more strict or relaxed. | ||
| b. Can be used for commercial purposes, such as Dify's cloud business. | ||
| a. The producer can adjust the open-source agreement to be more strict or relaxed as deemed necessary. | ||
| b. Your contributed code may be used for commercial purposes, including but not limited to its cloud business operations. | ||
|
|
||
| Apart from this, all other rights and restrictions follow the Apache License 2.0. If you need more detailed information, you can refer to the full version of Apache License 2.0. | ||
| Apart from the specific conditions mentioned above, all other rights and restrictions follow the Apache License 2.0. Detailed information about the Apache License 2.0 can be found at http://www.apache.org/licenses/LICENSE-2.0. | ||
|
|
||
| The interactive design of this product is protected by appearance patent. | ||
|
|
||
| © 2023 LangGenius, Inc. | ||
| © 2024 LangGenius, Inc. | ||
|
|
||
|
|
||
| ---------- | ||
|
|
||