# Dify — Open-source platform for building agentic workflows, AI agents and RAG knowledge pipelines. > Source: The Agents Index — https://theagentsindex.com/dify (structured, researched, re-verified) > Facts last verified: 2026-09-02 Dify is an open-source platform for building agentic workflows, AI agents and RAG knowledge pipelines on one visual canvas. It runs as a managed cloud workspace or self-hosted on your own infrastructure, and every app it publishes is also an API. | Fact | Value | | --- | --- | | Website | https://dify.ai | | Price | from $59/month billed monthly, $49.17/month billed annually | | Free tier | Yes | Sandbox: 200 message credits (one-time), 1 workspace, 1 member, 5 apps, 50 knowledge documents, 50MB knowledge storage, 3,000 trigger events, 30 days log history, 5,000 API calls/month. Self-hosted Community edition is also free. ## What it does **Done-for-you service** · No — You run the software: open-source Community edition, self-serve Cloud, or Enterprise where Dify hosts or you deploy in your own VPC. > Your AWS / GCP / Azure account. Fast deployment with Helm charts. Data never leaves your security perimeter. We monitor, you control. > — https://dify.ai/dify-enterprise · 'Enterprise AI, On Your Terms.' section, Customer-managed VPC card ## How much it does unattended **Runs autonomously** · Yes — Agents run in their own sandbox, executing commands and files to take on open-ended work; workflows also start unattended from schedule, webhook or integration triggers. > It works in a sandbox of its own: it runs commands, installs programs, and reads and writes files, so it takes on open-ended work rather than just calling the tools you configured. > — https://docs.dify.ai/en/cloud/use-dify/build/new-agent/overview · Agent overview, bullet list under the beta notice **Multi-agent** · Yes — Agents can be placed as nodes inside a workflow so several specialised agents hand work to each other. > Choose this when the work needs structure around it: several steps in a set order, branching on conditions, other kinds of nodes, or a few specialized agents handing off to each other. > — https://docs.dify.ai/en/cloud/use-dify/build/new-agent/overview · 'Inside a Workflow' section **Agent permissions** · Partly — Autonomy is bounded by design, not by a permission prompt: a Human Input node pauses a run for review, approval or edits, with a timeout branch. > Recipients can use the form to review information, provide input, and choose from predefined decisions that determine how the workflow proceeds. > — https://docs.dify.ai/en/cloud/use-dify/nodes/human-input · Human Input node, opening paragraph ## Which models it runs on **Claude** · Yes — Anthropic models are among the providers covered by bundled message credits; you can also add your own Anthropic key. > Message credits are provided to help you easily try out different models from OpenAI, Anthropic, Gemini, xAI, Tongyi in Dify. Credits are consumed based on the model type. > — https://dify.ai/pricing · Plan cards, message credits tooltip (all three Cloud plans) **GPT** · Yes — OpenAI models are covered by bundled message credits, or via your own key. > Message credits are provided to help you easily try out different models from OpenAI, Anthropic, Gemini, xAI, Tongyi in Dify. Credits are consumed based on the model type. > — https://dify.ai/pricing · Plan cards, message credits tooltip (all three Cloud plans) **Open models** · Partly — Locally deployed models are supported on air-gapped Enterprise deployments; on Cloud you install a provider from the Marketplace and supply its credentials. > Built for industries such as healthcare, finance, retail, and automotive. Run fully offline and connect locally deployed models based on your enterprise needs. > — https://dify.ai/dify-enterprise · Deployment topologies section, Air-gapped on-prem card **Model choice** · Yes — You pick the model per app and per node, from bundled providers or any provider you install and key yourself; workspace defaults are configurable. > Add your own API key to a supported provider when you want higher rate limits or billing through your own provider account. > — https://docs.dify.ai/en/cloud/use-dify/workspace/model-providers · 'Use Your Own Account with a Supported Provider' section ## Where you use it **In your editor** · Partly — No IDE extension; instead a published Dify app can be attached to Cursor or Claude Desktop as an MCP server. > Dify now supports exposing your applications as MCP (Model Context Protocol) servers, enabling seamless integration with AI assistants like Claude Desktop and development environments like Cursor. > — https://docs.dify.ai/en/cloud/use-dify/publish/publish-mcp · MCP Server page, opening paragraph **On the command line** · Yes — Official difyctl CLI runs workspace apps from a terminal with OAuth sign-in and JSON output. > Dify CLI (difyctl) closes that gap: anything that can run a shell command can run your Dify apps. > — https://docs.dify.ai/en/cli/overview · CLI Overview, intro paragraph **In your pipeline** · Partly — The CLI is documented for CI pipelines, so apps can run as a build step; there is no pull-request review or repo-acting surface. > Run your Dify apps from terminals, scripts, CI pipelines, and AI agents with the official Dify command-line interface difyctl > — https://docs.dify.ai/en/cli/overview · CLI Overview, page description line **In a browser** · Yes — Apps are built in a browser workspace and published as hosted web apps or embeds. > Turn your workflows into powerful web applications with batch processing, result management, and streamlined user experiences > — https://docs.dify.ai/en/cloud/use-dify/publish/webapp/workflow-webapp · Workflow Web Apps, page description ## Whose machine it runs on **Self-hosted** · Yes — Community Edition runs anywhere Docker runs; Enterprise adds Kubernetes/Helm, VPC and air-gapped deployment. > Dify runs anywhere Docker runs: a laptop, an on-premises server, or a cloud VM. Start with Docker Compose, or pick another path below. > — https://docs.dify.ai/en/self-host/deploy/overview · Deploy Dify, hero paragraph **Open source** · Yes — Core features are published in the public repository under Dify's own open-source licence; commercial licensing is an Enterprise item. > All Core Features Released Under the Public Repository > — https://dify.ai/pricing · Self-hosted plans, Community card, Free Features list ## What it costs to run **How it meters** · Yes — Per-workspace subscription with a seat ceiling, metered in message credits: one credit-consuming AI response per model call, priced by model. > An AI response is a single model call (one input and one output), and it counts as one response no matter how many tokens it uses. > — https://docs.dify.ai/en/cloud/use-dify/workspace/model-providers · 'Use Models with Your AI Credits' section **Free tier** · Yes — Sandbox plan is free with 200 message credits, 1 member, 5 apps and 30-day log history; the Community edition is free to self-host. > 200 message credits > — https://dify.ai/pricing.md · Sandbox plan, feature list **API access** · Yes — Every published app and every knowledge base is a REST API called with a Bearer key; Sandbox is capped at 5,000 calls/month, paid plans are uncapped. > Every app you publish in Dify doubles as a REST API, and so do your knowledge bases. > — https://docs.dify.ai/en/api-reference/guides/get-started · Get Started with the Dify API, intro paragraph **MCP server** · Yes — Any app can be exposed as an MCP server from its Access Point tab; the URL carries credentials and can be regenerated. > On your app's Access Point tab, find the MCP Server card. The feature is disabled by default. When you toggle it on, Dify generates a unique MCP Server address for your application. > — https://docs.dify.ai/en/cloud/use-dify/publish/publish-mcp · 'Configure Your Dify App as an MCP Server' section **Bring your own key** · Yes — Bring your own provider keys, billed to your own provider account, and run them alongside or instead of bundled credits; own cloud via self-host or VPC. > Any key you add works across the whole workspace and bills to your own account with that provider. > — https://docs.dify.ai/en/cloud/use-dify/workspace/model-providers · Warning callout below the intro ## Buying it for a team **A company can buy it** · Yes — Subscriptions are bought per workspace by its owner or admins, up to 50 members on Team; Enterprise is quoted by sales. > Billing in Dify is workspace-scoped. Your subscription sets the team member limit, feature access, and usage quotas for the entire workspace. > — https://docs.dify.ai/en/cloud/use-dify/workspace/subscription-management · Billing, intro paragraph **Seat model** · Yes — Seats are a plan ceiling, not a per-seat price: 1 on Sandbox, 3 on Professional, 50 on Team. > The number of members your workspace can include depends on your subscription plan > — https://docs.dify.ai/en/cloud/use-dify/workspace/team-members-management · Team Size Limits section, intro line above the per-plan list (Sandbox 1, Professional 3, Team 50) **Pooled budget** · Yes — One pooled balance: message credits, apps and storage quotas belong to the workspace, not to individual members. > Billing in Dify is workspace-scoped. Your subscription sets the team member limit, feature access, and usage quotas for the entire workspace. > — https://docs.dify.ai/en/cloud/use-dify/workspace/subscription-management · Billing, intro paragraph **Admin controls** · Yes — Four built-in roles on Cloud gate who can build versus only use published apps; Enterprise adds workflow-level RBAC and SCIM. > Each member's access is determined by the role they hold. > — https://docs.dify.ai/en/cloud/use-dify/workspace/team-members-management · Manage Members, intro line above the four built-in roles (Owner, Admin, Editor, Normal) **Audit log** · Partly — Cloud gives per-app conversation and run logs; tamper-evident audit logs with SIEM streaming are an Enterprise capability. > Tamper-evident audit logs streamed to your SIEM. Per-call traces. PII-redacted prompt history. > — https://dify.ai/dify-enterprise · 'Everything Your CISO Will Want' section, Audit & observability card **Single sign-on** · Partly — SAML/OIDC SSO is an Enterprise feature; Cloud sign-in uses GitHub/Google social login instead. > SSO via SAML/OIDC. Fine-grained RBAC down to workflow-level. SCIM provisioning. Session policies. > — https://dify.ai/dify-enterprise · 'Everything Your CISO Will Want' section, Identity & access card ## What happens to your code **Opt out of training** · Yes — Nothing to opt out of: the vendor states it does not train models and contractually bars its model sub-processors from training on your data. > LangGenius is a platform company. We do not train AI models ourselves, and we will not use your AI interaction data for model training. > — https://dify.ai/legal/privacy-policy · Section 2, 'About AI interaction data' paragraph **Data residency** · Partly — Cloud data may be processed in any country where the vendor or its providers operate; region confinement requires Enterprise VPC, dedicated or air-gapped deployment. > Specifically, our website servers are located in the United States, and our affiliates, partners, third parties, and service providers operate in the United States, European Economic Area, and China. > — https://dify.ai/legal/privacy-policy · Data Transfers section, first paragraph **Getting out** · Partly — Workflow run history exports as monthly CSV archives (Professional/Team, owner or admin only); no statement found on whether unused message credits expire or refund. > Each download is a ZIP containing CSV files that cover all workflow runs in the workspace for that month > — https://docs.dify.ai/en/cloud/use-dify/monitor/logs · 'Download Archived Logs' section **Certifications** · Partly — GDPR handling is documented in the privacy policy (SCCs, EEA/UK/Swiss rights, DPA); SOC 2 Type II and ISO 27001 are asserted only in the Enterprise page metadata, with no trust page or report to verify. > The main safeguard relied upon by LangGenius is the Standard Contractual Clauses for Data Protection approved by the European Commission. > — https://dify.ai/legal/privacy-policy · Data Transfers section, EEA/UK/Switzerland paragraph ## Platform record (as of 2026-08-30) Reported by the code-hosting platform, not by the vendor. | Fact | Value | | --- | --- | | Stars | 153886 | | Forks | 24317 | | Last push | 2026-08-30 | ## Provenance 1 of 22 sources behind the facts above are independent of the vendor. ## Coverage elsewhere None recorded. Every fact above comes from the vendor and is not independently corroborated yet. ## What changed - 2026-09-02 — Capabilities · Commercial terms · Free tier - 2026-08-31 — Capabilities · Commercial terms · Free tier · Price - 2026-08-23 — Documentation link · LinkedIn link · Summary ## Correcting this record Anything marked "Not established" is a question we have not answered — it is not a No. If you represent Dify, or anything here is wrong or out of date, you can supply it with a source: the operations this site accepts from an agent are listed at https://theagentsindex.com/.well-known/agents.json — that catalogue needs no key to read, and each entry states its own auth. Supplying evidence is free. Nothing that can be bought here changes what a field says, whether a gap is closed, or how this record is scored.