Dify
Dify review: AI apps, knowledge bases and pricing
Dify builds AI apps with visual workflows, knowledge bases and agents. Explore its features, workspace pricing, self-hosting and alternatives.
Free plan availableAccount optional

- Access
- Free and paid plans
- Example plan
- USD 59 / monthProfessional — monthly
- Available on
- Web, API
Build and publish AI applications around your data
Dify builds AI applications through a shared visual canvas. A Workflow processes an input from start to finish; a Chatflow adds a conversation, with each message passing through the configured logic before an answer returns. Workflows can also start from schedules, webhooks and integration events, while Chatflows start from user messages. Model calls, knowledge retrieval, code and conditional branches connect the steps, making the platform useful for document-processing apps as well as interactive assistants.
Knowledge bases give an app access to its own documents rather than relying only on a model’s training. Dify retrieves relevant passages and passes them into the model with the question. Knowledge settings cover indexing, embedding models and retrieval strategies; document metadata can narrow the search. Multi-source retrieval can blend keyword and semantic scores or use an external reranking model. The latter needs a provider connection and can add costs. Retrieval quality still depends on the documents and configuration, so adding a knowledge base does not guarantee a correct answer.
Model connections are shared across a workspace and managed by its owner or admins. Cloud credits cover supported providers without an initial API key, while your own provider keys can coexist with those credits. Usage priority determines which is used first. A model response is one call with an input and output, and the credit rate varies by model. An app that calls models several times can consume several responses in one run. Embedding and reranking models have their own roles alongside the model producing the final answer.
Tools, custom APIs, HTTP requests, MCP connections and code extend what a flow can do. Dify’s new Agent, currently in beta, adds a separate kind of AI worker with its own sandbox: it can run commands, install programs and read or write files. Its configuration includes a role, model, skills, tools and files. The same agent can serve as a standalone chat app or handle a task inside a larger workflow. Its sessions collect in Logs with their source identified. This is distinct from the legacy Agent app.
A Human Input node pauses a workflow and presents a form with defined decision buttons and input fields. A person can approve an output, supply corrections or choose another path before the process continues. Forms can appear in a web app or arrive by email; web-app delivery is unavailable for trigger-started workflows. Email recipients can respond without a Dify account, and the first response closes the request. A configured timeout branch handles requests that receive no response; without that branch, the workflow ends when the request expires.
Workflow Studio exposes intermediate values, node outputs and execution paths for debugging. LLM, HTTP, Code and Tool nodes can route failures to recovery paths or return defaults. Chatflow and Workflow apps separate the working draft from the latest published version and keep a history of releases. Paid plans add restoration, exporting a specific version’s DSL and running a specific published version through the Service API. Sandbox apps run the latest published version.
Published apps can reach users through a web interface, an embedded widget or frame, an API endpoint, or MCP. These routes use the app’s configuration rather than requiring a separate build for every channel. Publishing activates the current configuration for the live app and its endpoints. API integration suits teams that want their own product interface, while a hosted web app provides a direct way to share an assistant or workflow with users.
Cloud hosting avoids operating the platform yourself, while Community runs on your infrastructure. Cloud subscriptions cover a workspace and its member, app, knowledge, trigger and API limits; included model credits and outside provider charges are separate. Community uses Apache 2.0 with additional conditions: a commercial licence is needed for unauthorized multi-tenant hosting, and its licence defines each workspace as a tenant. Removing or changing logo and copyright information is restricted when using Dify’s frontend. Self-hosting also brings responsibility for maintenance, storage, backups and any connected model services.
Best for
- Teams building AI assistants around their own documents
- Developers delivering AI apps through a web interface, API or MCP
- Document-processing and agent workflows with configured human review
Limitations
Cloud resource limits vary by workspace plan, and model credits do not equal complete app runs. New Agent is in beta. Some version-control actions require a paid plan. Self-hosting needs infrastructure maintenance; Community licensing restricts multi-workspace hosting and changes to frontend branding. External model services can still receive app data.
Dify features
Workflow and Chatflow builders
Create one-pass AI processes or conversational apps with shared visual nodes. Workflows also support scheduled, webhook and integration-event triggers.
Knowledge bases and retrieval
Connect documents to apps, filter by metadata and configure keyword, semantic or reranked retrieval.
Provider models and custom tools
Use supported Cloud credits or your own model accounts, alongside custom APIs, HTTP requests, MCP tools and code.
New Agent with a sandbox
The beta Agent can run commands and work with files. Use the same configured agent as a chat app or a step inside a workflow.
Human Input forms
Pause a flow for a decision or corrections through web-app or email forms, with configured timeout handling.
Debugging and release history
Inspect node values and failure paths. Chatflow and Workflow keep published versions; restoration and version-specific API runs require a paid plan.
Web apps, embeds, APIs and MCP
Deliver an app through a shareable interface, website embed, API endpoint or MCP connection.
Dify pricing
Dify Cloud offers a free Sandbox and paid Professional and Team workspace subscriptions; Enterprise is custom-priced. Plans set member, app, knowledge, trigger and API allowances. Professional includes three members and Team includes 50, so builder access can matter as much as model usage. Included model credits are consumed per model response at model-specific rates; your own provider accounts charge separately. Community software has no subscription fee under its licence, with hosting and model costs extra. Monthly and annual billing differ, and advertised prices exclude applicable taxes.
Example plans.
Professional — monthly
USD 59 / month
Dify Cloud workspace
Plan details
One workspace, up to three members; 5,000 model credits/month, 50 apps. Provider charges and taxes separate.
Team — monthly
USD 159 / month
Dify Cloud workspace
Plan details
One workspace, up to 50 members; 10,000 model credits/month, 200 apps. Provider charges and taxes separate.
Technical specifications
Automation and agents
| Feature | Dify |
|---|---|
| Connectors and tool access | Visual model, knowledge, tool, HTTP and code nodes; custom APIs and MCP. The beta Agent adds a sandbox for commands, programs and files.Workspace models; beta new Agent has a distinct capability |
| Triggers and scheduling | Workflows accept inputs or schedule, webhook and integration-event triggers. Chatflows start from a user message and do not have Triggers.Cloud trigger-event quotas vary by plan |
| Human approval controls | Human Input pauses for decision forms and edits. Email links need no Dify account and close after the first response; web-app delivery is unavailable for trigger-started workflows.Configured decisions and timeout paths |
| Hosting and deployment | Managed Cloud, self-hosted Community and custom Enterprise. Community has modified Apache 2 terms for multi-tenant workspaces and frontend branding.Commercial licence required for uses outside Community conditions |
| Execution accounting | Cloud subscriptions are per workspace. Each model response consumes a model-specific credit amount; multiple calls can occur in one run. Own provider keys, trigger quotas and knowledge limits are separate.Provider keys and credits can coexist with usage priority |
| API access | SupportedPublished app endpoints; Cloud API quotas vary by plan |
Dify alternatives
Explore visual AI components, self-hosted app automation and hosted business workflows.
Dify FAQs
Is Dify free?
Dify Cloud has a free Sandbox with 200 model credits, one member and five apps, plus limited knowledge, trigger and API resources. Community software has no subscription fee under its licence; hosting and external model services can cost extra.
How much does Dify cost?
Dify Cloud uses paid Professional and Team workspace plans, with monthly and annual billing, while Enterprise is custom-priced. Professional includes three members and Team includes 50. See the dated plan examples below for rates. Model-provider usage and applicable taxes are separate.
What is the difference between a Workflow and a Chatflow?
A Workflow runs a process from input to result and can start from a schedule, webhook or integration event. A Chatflow processes each user message through the flow before replying, adding a conversational interface. Both share the visual canvas and node system.
Do Dify model credits equal app runs?
No. Credits apply to individual model responses at rates that depend on the model. One application run can make several model calls. Trigger-event allowances and knowledge or API limits are separate; your own provider keys bill through those provider accounts.
Can Dify require human approval?
Yes. A Human Input node pauses the workflow for a form response and sends it through a configured decision path. It can collect edits or other input as well as approval. Web-app forms do not support trigger-started workflows; email links can be answered without a Dify account and close after the first response.
Can I self-host Dify commercially?
Community licensing allows commercial use with additional conditions. Unauthorized multi-tenant hosting requires a commercial licence, with each workspace defined as a tenant. Dify’s frontend logo and copyright information cannot be removed or changed under the Community terms. Infrastructure and provider costs remain yours.
What are the best Dify alternatives?
Langflow focuses on visual AI components and agent applications. n8n combines app automation, code and AI with Cloud or self-hosted deployment. Make focuses on hosted business-app scenarios and branching automation. Dify is especially useful when knowledge retrieval and AI app delivery belong in the same platform.
Is this your product? Claim this page to update your listing.