You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
[FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
Please do not modify this template :) and fill in all the required fields.
Content
We previously reached out to support@dify.ai regarding a licensing question but haven't received a response yet. Since this will affect our architecture and evaluation of Dify, we're posting here in the hope that someone from the team can provide some clarification.
We have an existing commercial SaaS platform that is already used by multiple customers. We are evaluating Dify as the AI backend while our users interact only with our own custom chat UI. Our customers will not access the Dify UI directly.
Our main questions are:
Is it permitted to self-host a single Dify Community Edition instance/workspace and use it as the backend for multiple customers of our SaaS application?
If, in the future, a specific customer requests complete isolation, can we deploy a separate self-hosted Community Edition instance exclusively for that customer?
If multiple Community Edition deployments are not permitted under the license, what licensing option would be required? Is there a commercial or enterprise license that covers this scenario, and how is it priced (per instance, per workspace, per customer, etc.)?
We're happy to purchase a commercial license if that's the appropriate approach. We simply want to understand the licensing model before we finalize our system architecture.
If there is a better contact or process for obtaining licensing clarification, we'd also appreciate knowing that, as we haven't received a response from support@dify.ai
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Self Checks
Content
We previously reached out to support@dify.ai regarding a licensing question but haven't received a response yet. Since this will affect our architecture and evaluation of Dify, we're posting here in the hope that someone from the team can provide some clarification.
We have an existing commercial SaaS platform that is already used by multiple customers. We are evaluating Dify as the AI backend while our users interact only with our own custom chat UI. Our customers will not access the Dify UI directly.
Our main questions are:
Is it permitted to self-host a single Dify Community Edition instance/workspace and use it as the backend for multiple customers of our SaaS application?
If, in the future, a specific customer requests complete isolation, can we deploy a separate self-hosted Community Edition instance exclusively for that customer?
If multiple Community Edition deployments are not permitted under the license, what licensing option would be required? Is there a commercial or enterprise license that covers this scenario, and how is it priced (per instance, per workspace, per customer, etc.)?
We're happy to purchase a commercial license if that's the appropriate approach. We simply want to understand the licensing model before we finalize our system architecture.
If there is a better contact or process for obtaining licensing clarification, we'd also appreciate knowing that, as we haven't received a response from support@dify.ai
All reactions