langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-08-27 03:01:54 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Are there any restrictions on the use of the locally deployed version of dify? #8463

New Issue
Closed
opened 2026-02-21 18:25:48 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 18:25:48 -05:00
Owner
Copy Link
Copy Source

Originally created by @Jimmy-L99 on GitHub (Feb 20, 2025).

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • 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.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Are there any restrictions on the use of the locally deployed version of dify? Such as the number of users, concurrency limits, chat assistant and workflow limits, etc just like the Sandbox version?

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @Jimmy-L99 on GitHub (Feb 20, 2025). ### Self Checks - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [x] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. Are there any restrictions on the use of the locally deployed version of dify? Such as the number of users, concurrency limits, chat assistant and workflow limits, etc just like the Sandbox version? ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 🙋‍♂️ question label 2026-02-21 18:25:48 -05:00
yindo closed this issue 2026-02-21 18:25:48 -05:00
yindo commented 2026-02-21 18:25:49 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 20, 2025):

The locally deployed version of Dify does have some restrictions, particularly regarding concurrency limits. The SERVER_WORKER_CONNECTIONS environment variable is set to a default of 10, which limits the number of concurrent connections per server worker. Additionally, the SERVER_WORKER_AMOUNT is set to 1 by default, indicating the number of server workers. These settings can be adjusted in the configuration to change the concurrency limits. Furthermore, the APP_MAX_ACTIVE_REQUESTS environment variable can be set to limit the maximum number of active requests for the application, with a default value of 0 indicating no limit [1][2].

However, I couldn't find specific information on restrictions regarding the number of users, chat assistants, or workflows in the locally deployed version. If you need more detailed information, you might want to check the configuration files or documentation for any additional settings that could apply.

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Feb 20, 2025): <!-- Answer --> The locally deployed version of Dify does have some restrictions, particularly regarding concurrency limits. The `SERVER_WORKER_CONNECTIONS` environment variable is set to a default of 10, which limits the number of concurrent connections per server worker. Additionally, the `SERVER_WORKER_AMOUNT` is set to 1 by default, indicating the number of server workers. These settings can be adjusted in the configuration to change the concurrency limits. Furthermore, the `APP_MAX_ACTIVE_REQUESTS` environment variable can be set to limit the maximum number of active requests for the application, with a default value of 0 indicating no limit <sup>[[1]](https://github.com/langgenius/dify/blob/main/docker/docker-compose.yaml)</sup><sup>[[2]](https://github.com/langgenius/dify/blob/main/docker/.env.example)</sup>. However, I couldn't find specific information on restrictions regarding the number of users, chat assistants, or workflows in the locally deployed version. If you need more detailed information, you might want to check the configuration files or documentation for any additional settings that could apply. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/f597bfd5-e477-46ce-b723-8c0cefac1673?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/f597bfd5-e477-46ce-b723-8c0cefac1673?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/f597bfd5-e477-46ce-b723-8c0cefac1673?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/f597bfd5-e477-46ce-b723-8c0cefac1673?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/f597bfd5-e477-46ce-b723-8c0cefac1673?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/f597bfd5-e477-46ce-b723-8c0cefac1673?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/f597bfd5-e477-46ce-b723-8c0cefac1673?feedback_type=other)</sup>
yindo commented 2026-02-21 18:25:49 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Feb 20, 2025):

See our open. source license. https://github.com/langgenius/dify?tab=License-1-ov-file

a. Multi-tenant 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, 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.
- Frontend Definition: For the purposes of this license, the "frontend" of Dify includes all components located in the web/ directory when running Dify from the raw source code, or the "web" image when running Dify with Docker.

Please contact business@dify.ai by email to inquire about licensing matters.

Besides that we do not have limitations on the function.

@crazywoola commented on GitHub (Feb 20, 2025): See our open. source license. https://github.com/langgenius/dify?tab=License-1-ov-file > a. Multi-tenant 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, 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. > - Frontend Definition: For the purposes of this license, the "frontend" of Dify includes all components located in the `web/` directory when running Dify from the raw source code, or the "web" image when running Dify with Docker. > > Please contact business@dify.ai by email to inquire about licensing matters. Besides that we do not have limitations on the function.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🙋‍♂️ question
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#8463
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?