Nevar pievienot vairāk kā 25 tēmas Tēmai ir jāsākas ar burtu vai ciparu, tā var saturēt domu zīmes ('-') un var būt līdz 35 simboliem gara.

pirms 2 gadiem
pirms 2 gadiem
pirms 2 gadiem
pirms 1 gada
pirms 2 gadiem
pirms 2 gadiem
pirms 2 gadiem
pirms 2 gadiem
pirms 2 gadiem
pirms 2 gadiem
pirms 2 gadiem
pirms 2 gadiem
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239
  1. ![cover-v5-optimized](https://github.com/langgenius/dify/assets/13230914/f9e19af5-61ba-4119-b926-d10c4c06ebab)
  2. <p align="center">
  3. <a href="https://cloud.dify.ai">Dify Cloud</a> ·
  4. <a href="https://docs.dify.ai/getting-started/install-self-hosted">Self-hosting</a> ·
  5. <a href="https://docs.dify.ai">Documentation</a> ·
  6. <a href="https://udify.app/chat/22L1zSxg6yW1cWQg">Enterprise inquiry</a>
  7. </p>
  8. <p align="center">
  9. <a href="https://dify.ai" target="_blank">
  10. <img alt="Static Badge" src="https://img.shields.io/badge/Product-F04438"></a>
  11. <a href="https://dify.ai/pricing" target="_blank">
  12. <img alt="Static Badge" src="https://img.shields.io/badge/free-pricing?logo=free&color=%20%23155EEF&label=pricing&labelColor=%20%23528bff"></a>
  13. <a href="https://discord.gg/FngNHpbcY7" target="_blank">
  14. <img src="https://img.shields.io/discord/1082486657678311454?logo=discord&labelColor=%20%235462eb&logoColor=%20%23f5f5f5&color=%20%235462eb"
  15. alt="chat on Discord"></a>
  16. <a href="https://twitter.com/intent/follow?screen_name=dify_ai" target="_blank">
  17. <img src="https://img.shields.io/twitter/follow/dify_ai?logo=X&color=%20%23f5f5f5"
  18. alt="follow on X(Twitter)"></a>
  19. <a href="https://hub.docker.com/u/langgenius" target="_blank">
  20. <img alt="Docker Pulls" src="https://img.shields.io/docker/pulls/langgenius/dify-web?labelColor=%20%23FDB062&color=%20%23f79009"></a>
  21. <a href="https://github.com/langgenius/dify/graphs/commit-activity" target="_blank">
  22. <img alt="Commits last month" src="https://img.shields.io/github/commit-activity/m/langgenius/dify?labelColor=%20%2332b583&color=%20%2312b76a"></a>
  23. <a href="https://github.com/langgenius/dify/" target="_blank">
  24. <img alt="Issues closed" src="https://img.shields.io/github/issues-search?query=repo%3Alanggenius%2Fdify%20is%3Aclosed&label=issues%20closed&labelColor=%20%237d89b0&color=%20%235d6b98"></a>
  25. <a href="https://github.com/langgenius/dify/discussions/" target="_blank">
  26. <img alt="Discussion posts" src="https://img.shields.io/github/discussions/langgenius/dify?labelColor=%20%239b8afb&color=%20%237a5af8"></a>
  27. </p>
  28. <p align="center">
  29. <a href="./README.md"><img alt="README in English" src="https://img.shields.io/badge/English-d9d9d9"></a>
  30. <a href="./README_CN.md"><img alt="简体中文版自述文件" src="https://img.shields.io/badge/简体中文-d9d9d9"></a>
  31. <a href="./README_JA.md"><img alt="日本語のREADME" src="https://img.shields.io/badge/日本語-d9d9d9"></a>
  32. <a href="./README_ES.md"><img alt="README en Español" src="https://img.shields.io/badge/Español-d9d9d9"></a>
  33. <a href="./README_FR.md"><img alt="README en Français" src="https://img.shields.io/badge/Français-d9d9d9"></a>
  34. <a href="./README_KL.md"><img alt="README tlhIngan Hol" src="https://img.shields.io/badge/Klingon-d9d9d9"></a>
  35. <a href="./README_KR.md"><img alt="README in Korean" src="https://img.shields.io/badge/한국어-d9d9d9"></a>
  36. <a href="./README_AR.md"><img alt="README بالعربية" src="https://img.shields.io/badge/العربية-d9d9d9"></a>
  37. <a href="./README_TR.md"><img alt="Türkçe README" src="https://img.shields.io/badge/Türkçe-d9d9d9"></a>
  38. <a href="./README_VI.md"><img alt="README Tiếng Việt" src="https://img.shields.io/badge/Ti%E1%BA%BFng%20Vi%E1%BB%87t-d9d9d9"></a>
  39. </p>
  40. Dify is an open-source LLM app development platform. Its intuitive interface combines AI workflow, RAG pipeline, agent capabilities, model management, observability features and more, letting you quickly go from prototype to production. Here's a list of the core features:
  41. </br> </br>
  42. **1. Workflow**:
  43. Build and test powerful AI workflows on a visual canvas, leveraging all the following features and beyond.
  44. https://github.com/langgenius/dify/assets/13230914/356df23e-1604-483d-80a6-9517ece318aa
  45. **2. Comprehensive model support**:
  46. Seamless integration with hundreds of proprietary / open-source LLMs from dozens of inference providers and self-hosted solutions, covering GPT, Mistral, Llama3, and any OpenAI API-compatible models. A full list of supported model providers can be found [here](https://docs.dify.ai/getting-started/readme/model-providers).
  47. ![providers-v5](https://github.com/langgenius/dify/assets/13230914/5a17bdbe-097a-4100-8363-40255b70f6e3)
  48. **3. Prompt IDE**:
  49. Intuitive interface for crafting prompts, comparing model performance, and adding additional features such as text-to-speech to a chat-based app.
  50. **4. RAG Pipeline**:
  51. Extensive RAG capabilities that cover everything from document ingestion to retrieval, with out-of-box support for text extraction from PDFs, PPTs, and other common document formats.
  52. **5. Agent capabilities**:
  53. You can define agents based on LLM Function Calling or ReAct, and add pre-built or custom tools for the agent. Dify provides 50+ built-in tools for AI agents, such as Google Search, DALL·E, Stable Diffusion and WolframAlpha.
  54. **6. LLMOps**:
  55. Monitor and analyze application logs and performance over time. You could continuously improve prompts, datasets, and models based on production data and annotations.
  56. **7. Backend-as-a-Service**:
  57. All of Dify's offerings come with corresponding APIs, so you could effortlessly integrate Dify into your own business logic.
  58. ## Feature comparison
  59. <table style="width: 100%;">
  60. <tr>
  61. <th align="center">Feature</th>
  62. <th align="center">Dify.AI</th>
  63. <th align="center">LangChain</th>
  64. <th align="center">Flowise</th>
  65. <th align="center">OpenAI Assistants API</th>
  66. </tr>
  67. <tr>
  68. <td align="center">Programming Approach</td>
  69. <td align="center">API + App-oriented</td>
  70. <td align="center">Python Code</td>
  71. <td align="center">App-oriented</td>
  72. <td align="center">API-oriented</td>
  73. </tr>
  74. <tr>
  75. <td align="center">Supported LLMs</td>
  76. <td align="center">Rich Variety</td>
  77. <td align="center">Rich Variety</td>
  78. <td align="center">Rich Variety</td>
  79. <td align="center">OpenAI-only</td>
  80. </tr>
  81. <tr>
  82. <td align="center">RAG Engine</td>
  83. <td align="center">✅</td>
  84. <td align="center">✅</td>
  85. <td align="center">✅</td>
  86. <td align="center">✅</td>
  87. </tr>
  88. <tr>
  89. <td align="center">Agent</td>
  90. <td align="center">✅</td>
  91. <td align="center">✅</td>
  92. <td align="center">❌</td>
  93. <td align="center">✅</td>
  94. </tr>
  95. <tr>
  96. <td align="center">Workflow</td>
  97. <td align="center">✅</td>
  98. <td align="center">❌</td>
  99. <td align="center">✅</td>
  100. <td align="center">❌</td>
  101. </tr>
  102. <tr>
  103. <td align="center">Observability</td>
  104. <td align="center">✅</td>
  105. <td align="center">✅</td>
  106. <td align="center">❌</td>
  107. <td align="center">❌</td>
  108. </tr>
  109. <tr>
  110. <td align="center">Enterprise Features (SSO/Access control)</td>
  111. <td align="center">✅</td>
  112. <td align="center">❌</td>
  113. <td align="center">❌</td>
  114. <td align="center">❌</td>
  115. </tr>
  116. <tr>
  117. <td align="center">Local Deployment</td>
  118. <td align="center">✅</td>
  119. <td align="center">✅</td>
  120. <td align="center">✅</td>
  121. <td align="center">❌</td>
  122. </tr>
  123. </table>
  124. ## Using Dify
  125. - **Cloud </br>**
  126. We host a [Dify Cloud](https://dify.ai) service for anyone to try with zero setup. It provides all the capabilities of the self-deployed version, and includes 200 free GPT-4 calls in the sandbox plan.
  127. - **Self-hosting Dify Community Edition</br>**
  128. Quickly get Dify running in your environment with this [starter guide](#quick-start).
  129. Use our [documentation](https://docs.dify.ai) for further references and more in-depth instructions.
  130. - **Dify for enterprise / organizations</br>**
  131. We provide additional enterprise-centric features. [Log your questions for us through this chatbot](https://udify.app/chat/22L1zSxg6yW1cWQg) or [send us an email](mailto:business@dify.ai?subject=[GitHub]Business%20License%20Inquiry) to discuss enterprise needs. </br>
  132. > For startups and small businesses using AWS, check out [Dify Premium on AWS Marketplace](https://aws.amazon.com/marketplace/pp/prodview-t22mebxzwjhu6) and deploy it to your own AWS VPC with one-click. It's an affordable AMI offering with the option to create apps with custom logo and branding.
  133. ## Staying ahead
  134. Star Dify on GitHub and be instantly notified of new releases.
  135. ![star-us](https://github.com/langgenius/dify/assets/13230914/b823edc1-6388-4e25-ad45-2f6b187adbb4)
  136. ## Quick start
  137. > Before installing Dify, make sure your machine meets the following minimum system requirements:
  138. >
  139. >- CPU >= 2 Core
  140. >- RAM >= 4GB
  141. </br>
  142. The easiest way to start the Dify server is to run our [docker-compose.yml](docker/docker-compose.yaml) file. Before running the installation command, make sure that [Docker](https://docs.docker.com/get-docker/) and [Docker Compose](https://docs.docker.com/compose/install/) are installed on your machine:
  143. ```bash
  144. cd docker
  145. cp .env.example .env
  146. docker compose up -d
  147. ```
  148. After running, you can access the Dify dashboard in your browser at [http://localhost/install](http://localhost/install) and start the initialization process.
  149. > If you'd like to contribute to Dify or do additional development, refer to our [guide to deploying from source code](https://docs.dify.ai/getting-started/install-self-hosted/local-source-code)
  150. ## Next steps
  151. If you need to customize the configuration, please refer to the comments in our [.env.example](docker/.env.example) file and update the corresponding values in your `.env` file. Additionally, you might need to make adjustments to the `docker-compose.yaml` file itself, such as changing image versions, port mappings, or volume mounts, based on your specific deployment environment and requirements. After making any changes, please re-run `docker-compose up -d`. You can find the full list of available environment variables [here](https://docs.dify.ai/getting-started/install-self-hosted/environments).
  152. If you'd like to configure a highly-available setup, there are community-contributed [Helm Charts](https://helm.sh/) and YAML files which allow Dify to be deployed on Kubernetes.
  153. - [Helm Chart by @LeoQuote](https://github.com/douban/charts/tree/master/charts/dify)
  154. - [Helm Chart by @BorisPolonsky](https://github.com/BorisPolonsky/dify-helm)
  155. - [YAML file by @Winson-030](https://github.com/Winson-030/dify-kubernetes)
  156. #### Using Terraform for Deployment
  157. Deploy Dify to Cloud Platform with a single click using [terraform](https://www.terraform.io/)
  158. ##### Azure Global
  159. - [Azure Terraform by @nikawang](https://github.com/nikawang/dify-azure-terraform)
  160. ##### Google Cloud
  161. - [Google Cloud Terraform by @sotazum](https://github.com/DeNA/dify-google-cloud-terraform)
  162. ## Contributing
  163. For those who'd like to contribute code, see our [Contribution Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md).
  164. At the same time, please consider supporting Dify by sharing it on social media and at events and conferences.
  165. > We are looking for contributors to help with translating Dify to languages other than Mandarin or English. If you are interested in helping, please see the [i18n README](https://github.com/langgenius/dify/blob/main/web/i18n/README.md) for more information, and leave us a comment in the `global-users` channel of our [Discord Community Server](https://discord.gg/8Tpq4AcN9c).
  166. **Contributors**
  167. <a href="https://github.com/langgenius/dify/graphs/contributors">
  168. <img src="https://contrib.rocks/image?repo=langgenius/dify" />
  169. </a>
  170. ## Community & contact
  171. * [Github Discussion](https://github.com/langgenius/dify/discussions). Best for: sharing feedback and asking questions.
  172. * [GitHub Issues](https://github.com/langgenius/dify/issues). Best for: bugs you encounter using Dify.AI, and feature proposals. See our [Contribution Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md).
  173. * [Discord](https://discord.gg/FngNHpbcY7). Best for: sharing your applications and hanging out with the community.
  174. * [X(Twitter)](https://twitter.com/dify_ai). Best for: sharing your applications and hanging out with the community.
  175. ## Star history
  176. [![Star History Chart](https://api.star-history.com/svg?repos=langgenius/dify&type=Date)](https://star-history.com/#langgenius/dify&Date)
  177. ## Security disclosure
  178. To protect your privacy, please avoid posting security issues on GitHub. Instead, send your questions to security@dify.ai and we will provide you with a more detailed answer.
  179. ## License
  180. This repository is available under the [Dify Open Source License](LICENSE), which is essentially Apache 2.0 with a few additional restrictions.