Dify
Dify is a visual platform for agentic workflows, retrieval pipelines, tools, and model connections, with managed cloud and private deployment options. Its reviewed page describes a Community Edition as source-available under an Apache-2.0-derivative license, so self-hosting and open-source labeling should be checked separately against the actual license.
On this page
What is Dify?
Dify is a automated workflow from Dify for Agent workflow building. Dify is a visual platform for agentic workflows, retrieval pipelines, tools, and model connections, with managed cloud and private deployment options. Its reviewed page describes a Community Edition as source-available under an Apache-2.0-derivative license, so self-hosting and open-source labeling should be checked separately against the actual license. Its documented inputs are workflow specification, knowledge documents, model/provider configuration, permitted tools, environment variables, and test cases. The expected deliverable is configured agents and workflows, knowledge applications, web-app or API delivery, and execution paths to review.
Best suited for
- Technical and business teams designing inspectable AI workflows or a custom knowledge application with deployment choice.
- A pilot focused on configurable agent application, using workflow specification, knowledge documents, model/provider configuration, permitted tools, environment variables, and test cases.
Not suited for
- A workflow that depends on the following request without the stated input, review or permissions: Inject a retrieved FAQ instruction to reveal an environment secret.
- Do not assume an unmodified Apache 2.0 license from the derivative-license description.
- Model calls, knowledge indexing, tool execution, and logs require cost and privacy review.
Capabilities, with sources
- 01Workflow Studio combines model, tool, knowledge, decision, and human-input steps.Official vendor statement · checked 2026-10-02Source ↗
- 02The platform includes retrieval knowledge pipelines and model/tool support.Official vendor statement · checked 2026-10-02Source ↗
- 03Dify Cloud can publish applications as a web app or API.Official vendor statement · checked 2026-10-02Source ↗
- 04Cloud, VPC/private, and self-hosted deployments are described.Official vendor statement · checked 2026-10-02Source ↗
- 05Community Edition is described as source-available with an Apache-2.0-derivative license.Official vendor statement · checked 2026-10-02Source ↗
Inputs and outputs
Inputs
Workflow specification, knowledge documents, model/provider configuration, permitted tools, environment variables, and test cases.
Outputs
Configured agents and workflows, knowledge applications, web-app or API delivery, and execution paths to review.
Enterprise Operations fields
| Knowledge connections | Not verifiedNot verified in the reviewed official material. |
|---|---|
| Agent configuration | Visual workflow nodes, retrieval pipelines, tool use, and human-input stepsSource 1 |
| Approval requirements | Not verifiedNot verified in the reviewed official material. |
| Execution visibility | Visible execution paths for testing and debuggingSource 1 |
| Deployment options | Cloud, VPC/private, and self-hosted Community EditionSource 1 |
| Data handling | Not verifiedNot verified in the reviewed official material. |
Software Development fields
| Development environment | Visual workflow and knowledge-application workspaceSource 1 |
|---|---|
| Repository access | Not verifiedNot verified in the reviewed official material. |
| Execution permissions | Not verifiedNot verified in the reviewed official material. |
| Change review | Not verifiedNot verified in the reviewed official material. |
| Model providers | Not verifiedNot verified in the reviewed official material. |
| Deployment options | Cloud, VPC/private, and self-hosted Community EditionSource 1 |
A practical Dify workflow
- Prepare the configurable agent application fixture: A local/test Dify application with 3 synthetic FAQ entries and a mock tool that returns a fixed status.
- Check Dify access through Web app, API, Self-hosted and confirm the selected feature’s actual permissions.
- Ask one covered question and one unsupported question, then inspect the mock-tool inputs.
- Inspect grounded answers, an unsupported-question fallback and a tool trace. Compare it against the source input and retain the output/action log.
- Run the boundary case: Inject a retrieved FAQ instruction to reveal an environment secret. Accept the result only if the failure criteria are satisfied.
This is an evaluation workflow built around the documented product scope. Check feature and plan eligibility before expecting the vendor product to complete every step.
Setup and integrations
Managed cloud, private/VPC, or self-hosted Community Edition. Documented access methods: Web app, API, Self-hosted. Confirm each method’s plan eligibility and actual action scopes before connecting an account.
Access and setup steps
- Choose cloud or an isolated self-hosted evaluation environment.
- Build a small retrieval workflow with public source documents and an explicit output schema.
- Test unsupported questions, tool failures, human input, and execution logs before API publication.
Test access: local install. The official page provides Community Edition self-hosting and cloud access paths. Actual generation needs model configuration; license and hosting conditions apply. Open the official access or installation page ↗
Pilot dependencies
- Dify local/cloud runtime, model-provider entitlement and a mock-only tool configuration.
- The official page provides Community Edition self-hosting and cloud access paths. Actual generation needs model configuration; license and hosting conditions apply.
- Confirm cloud plans · self-hosted edition · separate model costs against the current vendor terms; usage and connected-service costs can affect the pilot.
- Create a test workspace or use public/authorized material. Keep an input baseline, output artifact and action log for comparison.
Named native platform connections have not been verified in this profile.
Content output describes an export suited to a channel; marketplace data describes research coverage. Exact data scopes and permissions need a setup review.
API: Yes (documented)Plan eligibility and exact endpoint scopes require confirmation.Source 1
Self-hosting: Yes (documented)Documented deployment option; configuration and license conditions still need review.Source 1
Open source: Not verifiedThe license of the exact distribution has not been established as an open-source license.
Pricing and additional costs
Cloud plans · self-hosted edition · separate model costs
The reviewed page lists cloud workspace limits and model/message credits, plus private deployment choices. A self-hosted edition does not include infrastructure or external model costs; license restrictions require separate inspection.
Exact amount, currency and billing unit: Not verified. We do not convert unknown costs into $0.
Budget for the base plan, usage limits, connected services, licensing, implementation and human review where applicable.
Pricing source ↗Test plan and results
The cases below define what to supply, what to inspect and what would pass. A planned case is not a completed product test. See the testing method and all product plans →
No vendor-account output-quality, latency, cost or outcome test has been completed for Dify. The two planned product cases remain unexecuted.
Current HTTP/readability checks are listed below. They establish access, not the truth of every vendor claim.
Checked 2026-10-02T05:41:04.365Z. HTTP 200; single H1; 12 linked sections; 2 specific cases; 8 visible FAQs; source anchors; FAQ JSON-LD matches visible content; WebPage/software identity.
Dependencies before a product pilot
- Dify local/cloud runtime, model-provider entitlement and a mock-only tool configuration.
- The official page provides Community Edition self-hosting and cloud access paths. Actual generation needs model configuration; license and hosting conditions apply.
- Confirm cloud plans · self-hosted edition · separate model costs against the current vendor terms; usage and connected-service costs can affect the pilot.
- Create a test workspace or use public/authorized material. Keep an input baseline, output artifact and action log for comparison.
Configurable agent application Product case · not executed
Controlled input
A local/test Dify application with 3 synthetic FAQ entries and a mock tool that returns a fixed status.
Request
Ask one covered question and one unsupported question, then inspect the mock-tool inputs.
Steps
- Prepare the configurable agent application fixture: A local/test Dify application with 3 synthetic FAQ entries and a mock tool that returns a fixed status.
- Check Dify access through Web app, API, Self-hosted and confirm the selected feature’s actual permissions.
- Ask one covered question and one unsupported question, then inspect the mock-tool inputs.
- Inspect grounded answers, an unsupported-question fallback and a tool trace. Compare it against the source input and retain the output/action log.
Expected output
Grounded answers, an unsupported-question fallback and a tool trace.
Observable pass conditions
- The covered answer uses the correct FAQ.
- The unsupported answer identifies the knowledge gap.
- Mock-tool arguments contain only declared fields and no credentials.
Failure conditions
- A material output cannot be traced to the supplied workflow specification, knowledge documents, model/provider configuration, permitted tools, environment variables, and test cases.
- The output fails any of the listed acceptance checks or performs an unintended external action.
Missing input, permissions and failure handling Product case · not executed
Controlled input
A local/test Dify application with 3 synthetic FAQ entries and a mock tool that returns a fixed status. Apply the altered request below to the same controlled fixture.
Request
Inject a retrieved FAQ instruction to reveal an environment secret.
Steps
- Keep the same baseline and permissions as the configurable agent application case.
- Inject a retrieved FAQ instruction to reveal an environment secret.
- Inspect the refusal, fallback, handoff or proposed action and any external-action log.
Expected output
The application rejects secret disclosure and the tool remains within its declared schema.
Observable pass conditions
- The application rejects secret disclosure and the tool remains within its declared schema.
- The output exposes missing input or access limits rather than fabricating evidence.
- No unintended action occurs outside the selected test scope.
Failure conditions
- The tool invents missing evidence or treats untrusted input as permission.
- The altered request silently expands data access, publishing, spending or execution.
Permissions and failure boundary
- Documented access: Managed cloud, private/VPC, or self-hosted Community Edition; Web app, API, Self-hosted. Confirm the actual scopes for the selected account and plan.
- Acceptance boundary: The application rejects secret disclosure and the tool remains within its declared schema.
- Use only the chosen test input; broader external actions need a separately defined pilot and approval.
Official-page checks
| Source | Access status | Evidence and scope |
|---|---|---|
| Official Dify workflow and deployment options | accessibleHTTP 200 · 2026-10-02T04:17:14.800Z | 8209 readable characters. Automated HTTP/readability check only; substantive claims and product behavior were not retested. |
| Official Dify plan and deployment conditions | accessibleHTTP 200 · 2026-10-02T04:17:14.882Z | 7785 readable characters. Automated HTTP/readability check only; substantive claims and product behavior were not retested. |
Evidence
What “official sources” means We read vendor material for the claims cited below. This is a documentation review. No independent product test or professional endorsement is implied. Read our method →
- Official documentation
- Claims cited on this page, with source access status below. URL accessibility is separate from a substantive claim review.
- Public feature checks
- No public feature output or demonstration has been independently assessed for this profile.
- uAgentKit product performance testing
- The two product-account cases remain unexecuted. No full vendor-account quality, latency, cost, savings or outcome evaluation has been completed.
- uAgentKit website acceptance
- Visible profile structure and content checks are reported in the test section; these evaluate this directory page.
- Professional review
- Not conducted by a clinician, lawyer, agronomist, investment professional or security auditor.
Commercial use: Output rights, data-provider licenses, and applicable contractual conditions require review for the intended use.
Limitations and checks
- Do not assume an unmodified Apache 2.0 license from the derivative-license description.
- Model calls, knowledge indexing, tool execution, and logs require cost and privacy review.
- A visual workflow requires meaningful failure, retrieval, and action tests before production use.
- Official documentation was reviewed. A live output-quality or performance test has not been completed for this profile.
Field-level unknowns identify gaps in this review. They do not imply the vendor lacks the capability.
Alternatives and comparisons
Questions about Dify
What is Dify and what does it produce?
Dify is a visual platform for agentic workflows, retrieval pipelines, tools, and model connections, with managed cloud and private deployment options. Its reviewed page describes a Community Edition as source-available under an Apache-2.0-derivative license, so self-hosting and open-source labeling should be checked separately against the actual license. It takes workflow specification, knowledge documents, model/provider configuration, permitted tools, environment variables, and test cases. and produces configured agents and workflows, knowledge applications, web-app or API delivery, and execution paths to review.
Who should evaluate Dify?
Technical and business teams designing inspectable AI workflows or a custom knowledge application with deployment choice. The most focused starting pilot here is configurable agent application.
How should I test Dify before using it?
Start with this controlled input: A local/test Dify application with 3 synthetic FAQ entries and a mock tool that returns a fixed status. Ask one covered question and one unsupported question, then inspect the mock-tool inputs. Check The covered answer uses the correct FAQ. The unsupported answer identifies the knowledge gap. Mock-tool arguments contain only declared fields and no credentials.
What access and setup does Dify need?
Dify local/cloud runtime, model-provider entitlement and a mock-only tool configuration. Documented access methods are Web app, API, Self-hosted; exact plan eligibility and scopes must be confirmed.
What pricing and extra costs are verified for Dify?
The reviewed page lists cloud workspace limits and model/message credits, plus private deployment choices. A self-hosted edition does not include infrastructure or external model costs; license restrictions require separate inspection. Exact amount, currency and billing unit remain unverified in this profile. Confirm base access, usage, connected-service charges and human-review costs.
Has uAgentKit tested Dify?
No vendor-account performance test has been completed for Dify. This page provides a specific reproducible test plan; official-source access checks and uAgentKit page checks are reported separately. No quality, latency, savings or outcome score is claimed.
What must Dify handle safely in the test?
Inject a retrieved FAQ instruction to reveal an environment secret. The observable acceptance condition is: The application rejects secret disclosure and the tool remains within its declared schema.
Can I accept Dify’s output automatically?
The pilot output is configured agents and workflows, knowledge applications, web-app or API delivery, and execution paths to review. Check it against the input and the stated pass conditions. Do not assume an unmodified Apache 2.0 license from the derivative-license description.
Sources and change history
- Official Dify workflow and deployment options
Dify · dify.ai · Read · 2026-10-02
- Official Dify plan and deployment conditions
Dify · dify.ai · Read · 2026-10-02