Veja em ação
Workflow canvas and test panel
The author-provided UI illustration shows a node picker, connected workflow blocks and the test-run panel.
Licença
Lossless PNG-to-WebP conversion; original dimensions and decoded pixels preserved. No crop, generated input, execution claim or site test. Existing interface marks remain visible. Source UI illustrations contain placeholder content. Full modified license and branding are retained; no Dify frontend code is deployed or operated.
# Open Source License
Dify is licensed under a modified version of the Apache License 2.0, with the following additional conditions:
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 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.
2. As a contributor, you should agree that:
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 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.
© 2025 LangGenius, Inc.
Knowledge-ingestion pipeline
The author-provided pipeline preview connects document sources to extraction and chunking, with a source-selection panel beside the canvas.
Licença
Lossless PNG-to-WebP conversion; original dimensions and decoded pixels preserved. No crop, generated input, execution claim or site test. Existing interface marks remain visible. Source UI illustrations contain placeholder content. Full modified license and branding are retained; no Dify frontend code is deployed or operated.
# Open Source License
Dify is licensed under a modified version of the Apache License 2.0, with the following additional conditions:
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 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.
2. As a contributor, you should agree that:
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 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.
© 2025 LangGenius, Inc.
Agent tools and conversation preview
The author-provided UI illustration shows agent instructions, tool selection and a travel-assistant conversation preview.
Licença
Lossless PNG-to-WebP conversion; original dimensions and decoded pixels preserved. No crop, generated input, execution claim or site test. Existing interface marks remain visible. Source UI illustrations contain placeholder content. Full modified license and branding are retained; no Dify frontend code is deployed or operated.
# Open Source License
Dify is licensed under a modified version of the Apache License 2.0, with the following additional conditions:
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 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.
2. As a contributor, you should agree that:
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 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.
© 2025 LangGenius, Inc.
Chatbot features and knowledge sources
The author-provided UI illustration combines instructions, variables and knowledge sources with conversation feature controls.
Licença
Lossless PNG-to-WebP conversion; original dimensions and decoded pixels preserved. No crop, generated input, execution claim or site test. Existing interface marks remain visible. Source UI illustrations contain placeholder content. Full modified license and branding are retained; no Dify frontend code is deployed or operated.
# Open Source License
Dify is licensed under a modified version of the Apache License 2.0, with the following additional conditions:
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 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.
2. As a contributor, you should agree that:
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 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.
© 2025 LangGenius, Inc.
Visão geral do produto
O Dify reúne configuração de modelos, recuperação de conhecimento e desenho de fluxos num ambiente de desenvolvimento. Uma equipe pode criar um assistente com seus documentos ou conectar várias etapas de processamento. A aplicação final pode ser publicada na web ou chamada por API REST.
Escolha entre Dify Cloud gerenciado e Community Edition auto-hospedada antes de implantar. Na auto-hospedagem, aplicação, armazenamento, atualizações e operação ficam sob sua responsabilidade. Modelos, plugins e ferramentas são dependências separadas; suas credenciais e franquias não vêm automaticamente com a plataforma.
O que o Dify oferece
- 01Criar agentes, assistentes e fluxos visualmente.
- 02Conectar uma base documental e configurar a recuperação.
- 03Publicar aplicações web ou integrar por API REST.
Um fluxo prático
- 01Escolher Cloud ou auto-hospedagem e conectar um provedor de modelo.
- 02Configurar uma tarefa com poucos documentos e as etapas necessárias.
- 03Comparar respostas com as fontes e testar falhas antes de publicar.
Resumo baseado na fonte; as afirmações do produto não foram testadas de forma independente.
O que o diferencia
O foco é montar aplicações com modelos e dados. As etapas visíveis facilitam a inspeção, mas a qualidade depende dos documentos, da recuperação, das instruções e do modelo.
Para quem é indicado
- Equipes que criam assistentes com documentos próprios.
- Desenvolvedores que conectam modelos e ferramentas em processos repetíveis.
O que confirmar
- Separar custos de plataforma, modelos, plugins, armazenamento e servidores.
- Planejar atualizações, backups e controle de acesso na auto-hospedagem.
- Verificar onde documentos internos e requisições aos modelos são processados.
Perguntas frequentes
Auto-hospedar inclui modelos gratuitos?
Não. A instalação própria não fornece créditos de provedores pagos. Cada serviço conectado tem suas próprias condições.
É possível integrar a aplicação a outro produto?
A documentação descreve publicação web e APIs REST. Confira o contrato da API e a autenticação da aplicação publicada.
As informações foram conferidas em 26 de out. de 2026 com o site oficial ou documentação primária.
