In Aktion ansehen
Workflow canvas and test panel
The author-provided UI illustration shows a node picker, connected workflow blocks and the test-run panel.

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

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

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

Lizenz
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.
Produktüberblick
Dify vereint Modellkonfiguration, Wissenssuche und Workflowgestaltung in einer Entwicklungsumgebung. Teams können aus eigenen Dokumenten einen Supportassistenten erstellen oder mehrere Verarbeitungsschritte zu einer Anwendung verbinden. Diese lässt sich über eine Weboberfläche veröffentlichen oder per REST API aufrufen.
Vor der Bereitstellung ist zwischen Dify Cloud und der selbst betriebenen Community Edition zu wählen. Beim Eigenbetrieb verantworten Sie Anwendung, Speicher, Updates und Betrieb. Modelle, Plugins und angeschlossene Werkzeuge sind eigene Abhängigkeiten; ihre Zugangsdaten und Kontingente sind nicht automatisch enthalten.
Was Dify bietet
- 01Agenten, Chatassistenten und Workflows visuell erstellen.
- 02Wissensquellen verbinden und Dokumentensuche konfigurieren.
- 03Anwendungen im Web oder über REST APIs bereitstellen.
Ein praktischer Ablauf
- 01Cloud oder Eigenbetrieb auswählen und einen Modellanbieter verbinden.
- 02Mit wenigen Dokumenten die Suche oder Workflowknoten für eine Aufgabe konfigurieren.
- 03Antworten mit Quellen und Fehlerfälle prüfen, dann Webanwendung oder API veröffentlichen.
Zusammenfassung auf Basis der Quelle; Produktangaben wurden nicht unabhängig getestet.
Was es unterscheidet
Der Schwerpunkt liegt auf Anwendungen aus Modellen und Daten. Sichtbare Verarbeitungsschritte erleichtern die Kontrolle; die Antwortqualität hängt weiterhin von Dokumenten, Sucheinstellungen, Prompts und Modell ab.
Für wen es geeignet ist
- Teams mit eigenen Dokumenten für Wissensassistenten.
- Entwickler wiederholbarer Abläufe aus Modellaufrufen und Werkzeugen.
Was zu prüfen ist
- Plattformkontingente von Modell-, Plugin-, Speicher- und Betriebskosten trennen.
- Beim Eigenbetrieb Updates, Backups und Zugriffsschutz planen.
- Vor internen Daten prüfen, wo Dokumente und Modellanfragen verarbeitet werden.
Häufige Fragen
Sind Modelle beim Eigenbetrieb kostenlos?
Nein. Selbsthosting enthält keine Guthaben kostenpflichtiger Modellanbieter. Für verbundene Dienste gelten eigene Bedingungen.
Kann ich die Anwendung in ein Produkt integrieren?
Die Dokumentation beschreibt Webveröffentlichung und REST APIs. Prüfen Sie Schnittstelle und Authentifizierung der veröffentlichten Anwendung.
Die Produktinformationen wurden am 26. Okt. 2026 mit der offiziellen Website oder Primärdokumentation abgeglichen.




