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.
新内容
2h 前已验证> [!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
完整发布说明 →
> **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
官方下载源
以下每个来源均已针对批准的发布者域名进行验证并经编辑批准。链接通过安全的内部重定向进行路由。
已验证校验和 文件完整性
安装前验证您下载的文件与发布者的官方哈希值匹配。
SHA-256
13d38e0a0061eec6e25cfdf3aa287743d468d186a09621fa92de3550a1dc96e0
平台： Windows
Dify 对比
仅基于已验证数据的事实性并排概览。
| 属性 | Dify 本页 | Rats-search | Spacedrive | Lettura |
|---|---|---|---|---|
| 开发者 | langgenius | librats | spacedriveapp | Zhang Lun |
| 分类 | Utilities | Utilities | Utilities | Utilities |
| 平台 | Windows | Windows | Windows | Windows |
| 官方来源 | 1 | 1 | 1 | 1 |
| 已验证官方 | ✓ | ✓ | ✓ | ✓ |
Dify 的替代品
同一分类下的已验证官方下载。
常见问题
我可以在哪里安全下载 Dify？
使用本页列出的官方来源。每个链接都针对批准的发布者域名进行了验证，并通过安全的内部重定向进行路由——无第三方或捆绑安装程序。
Dify 支持哪些平台？
Dify 适用于 Windows。
这是 Dify 的官方下载吗？
是的。此处显示的每个来源都经过发布者批准域名验证，并在发布前经过编辑审核。
谁开发了 Dify？
Dify 由 langgenius 开发。
Dify 的最佳替代品是什么？
流行的替代品包括 NonSteamLaunchers-On-Steam-Deck, Cinny-desktop 和 Gopeed。查看上方对比以获取并排概览。
评论和评分
暂无评论——成为第一个分享体验的人。
写评论