Will the use of the same Agent feature provided by Dify in all tenants of SaaS software lead to any license authorization issues?

[Gavinluo]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit report (我已阅读并同意 Language Policy).
• Please do not modify this template :) and fill in all the required fields.

Provide a description of requested docs changes

We are a SaaS software company specializing in supply chain management. We plan to use Dify for private deployment on the public cloud and create an Agent for all tenants to provide services, rather than offering each tenant a Dify workspace. For example, if I create an online help Agent for SaaS software to serve all tenants, could this potentially lead to authorization issues?
The reason for this question is because I came across this license statement.

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.

[dosubot[bot]]

Hello, @Gavinluo! I'm a bot here to assist you with bug fixes, questions, and contributing. How can I help you today?

Yes, using the same Agent feature provided by Dify in all tenants of your SaaS software could lead to license authorization issues. According to the Dify Open Source License, unless explicitly authorized by Dify in writing, you may not use the Dify source code to operate a multi-tenant SaaS service that is similar to the Dify.AI service edition. For commercial use, such as removing Dify's logo or requiring multiple workspaces, you will need to contact Dify for commercial licensing ^[1][2][3].

Details

About Dosu
This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

To continue the conversation, mention @dosu.

[Gavinluo]

I hope to have my question answered by a human.

[seijik42]

I'm building a similar product as yours.
If I understand correctly, your case shouldn't be a problem because:

Their license says

• 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.

You don't create workspace per tenant so this shouldn't apply.

Also, their website says

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.

The definition of similar to the Dify.AI service edition is unclear but UI and feature set is quite different, this shouldn't apply as well.

Of course, this is just my opinion. Any agreement from the official team would be really appreciated.