Dify
Build Agentic workflows, RAG pipelines, with rich AI model and tool support on one collaborative workspace. Deploy on cloud, VPC, or self-hosted, so teams move from prototype to production without rebuilding the stack.
Apa yang baru
Diverifikasi 2h yang lalu> [!WARNING]
> **Self-hosted deployments using the bundled Weaviate must complete a manual, staged upgrade before starting 1.17.1.** The bundled Weaviate server moves from `1.27.0` to `1.39.2` — 12 minor versions — and skipping minors **is unsupported**. Pulling and restarting can silently and permanently break vector search. See Upgrade Guide below. Fresh deployments, external Weaviate, and other vector stores are unaffected.
### New Features
**Dataset-Scoped Knowledge Base API Keys**
- Knowledge base service-API keys were scoped to the whole workspace: one key could read and write every knowledge base in the tenant, so giving an integration access to a single knowledge base meant giving it access to all of them. Keys can now be bound to specific knowledge bases from the knowledge base's API access panel, with a workspace / this-knowledge-base scope selector at creation time. A bound key returns `403` for any other dataset — both documents and retrieval — and for endpoints that carry no dataset ID, such as list-all. Existing keys are unbound and keep their workspace-wide behavior, so nothing changes when you upgrade. (#37569)
**Keyboard Movement for Workflow Nodes and C
Catatan rilis lengkap →
> **Self-hosted deployments using the bundled Weaviate must complete a manual, staged upgrade before starting 1.17.1.** The bundled Weaviate server moves from `1.27.0` to `1.39.2` — 12 minor versions — and skipping minors **is unsupported**. Pulling and restarting can silently and permanently break vector search. See Upgrade Guide below. Fresh deployments, external Weaviate, and other vector stores are unaffected.
### New Features
**Dataset-Scoped Knowledge Base API Keys**
- Knowledge base service-API keys were scoped to the whole workspace: one key could read and write every knowledge base in the tenant, so giving an integration access to a single knowledge base meant giving it access to all of them. Keys can now be bound to specific knowledge bases from the knowledge base's API access panel, with a workspace / this-knowledge-base scope selector at creation time. A bound key returns `403` for any other dataset — both documents and retrieval — and for endpoints that carry no dataset ID, such as list-all. Existing keys are unbound and keep their workspace-wide behavior, so nothing changes when you upgrade. (#37569)
**Keyboard Movement for Workflow Nodes and C
Sumber unduhan resmi
Setiap sumber di bawah ini telah divalidasi terhadap domain penerbit yang disetujui dan disetujui secara editorial. Tautan dialihkan melalui pengalihan internal yang aman.
Checksum terverifikasi Integritas file
Verifikasi bahwa file yang diunduh cocok dengan hash resmi penerbit sebelum menginstal.
SHA-256
13d38e0a0061eec6e25cfdf3aa287743d468d186a09621fa92de3550a1dc96e0
Platform: Windows
Dify dibandingkan
Ikhtisar berdampingan faktual hanya berdasarkan data terverifikasi.
Alternatif untuk Dify
Unduhan resmi terverifikasi dalam kategori yang sama.
Pertanyaan yang sering diajukan
Di mana saya dapat mengunduh Dify dengan aman?
Gunakan sumber resmi yang tercantum di halaman ini. Setiap tautan divalidasi terhadap domain penerbit yang disetujui dan dialihkan melalui pengalihan internal yang aman — tidak ada penginstal pihak ketiga atau bundel.
Platform apa yang didukung Dify?
Dify tersedia untuk Windows.
Apakah ini unduhan resmi Dify?
Ya. Setiap sumber yang ditampilkan di sini divalidasi terhadap domain penerbit yang disetujui dan ditinjau secara editorial sebelum diterbitkan.
Siapa yang mengembangkan Dify?
Dify dikembangkan oleh langgenius.
Apa alternatif terbaik untuk Dify?
Alternatif populer meliputi Twinkle Tray, Omni-search dan ShareX. Lihat perbandingan di atas untuk ikhtisar berdampingan.
Ulasan & penilaian
Belum ada ulasan — jadilah yang pertama berbagi pengalaman.
Tulis ulasan