Contents
- Verdict
- What is Dify?
- Best for, and not for
- Strengths and limits
- Pricing
- What people actually build with Dify
- What Dify actually costs at small-business volume
- The pricing gotcha: trigger events, and the licence
- What breaks in production, and how you find out
- What it connects to that you already run
- Dify alternatives: what to pick instead, and when
- Migration and lock-in: can you get your work out?
- FAQ
Dify is the strongest free option for a technical small business that wants an LLM app platform on its own servers. The Community Edition is free to self-host and the cloud pricing published as of August 2026 is unusual in this category for being annual and per-workspace rather than per-seat: Professional at $590 a year with 5,000 monthly message credits and three team members, Team at $1,590 a year with 10,000 monthly credits and fifty members. That fifty-member allowance on a $1,590 plan is remarkable value against per-seat competitors. The catch is the same as every self-hostable tool: free software plus your own operations time is not free, and Dify is built for developers.
What is Dify?
Dify is an open-source platform for developing LLM applications, including chat assistants, agents, and retrieval-augmented workflows. It combines a visual workflow builder with model management, prompt tooling, and a knowledge base for RAG. It can be self-hosted or used through a managed cloud offering, which appeals to teams that want control over their AI stack.
Best for
Developers and teams building LLM apps and RAG assistants who want open-source and self-hosting.
Not for
A business with nobody technical. Dify's value is concentrated in the self-hosted edition, and running it means running a container stack and a vector database - which is a fine trade for a developer and an impossible one for an office manager.
Strengths
- Community Edition is free to self-host, so an LLM app platform costs you infrastructure rather than licence fees
- Built-in RAG with knowledge base, document ingestion and chunking, which removes the most fiddly part of a document assistant
- Model-agnostic: supports many providers, so you can route cheap work to a budget model and judgement steps to a flagship
- Annual per-workspace cloud pricing with generous member counts, which is far kinder to a small team than per-seat billing
- Visual workflow builder alongside prompt and agent tooling, so non-trivial pipelines do not require dropping to code
- Active community and steady release cadence, with a large body of published deployment guidance
- Self-hosting means customer documents never leave your infrastructure, which is often the only way to satisfy a client contract
Limitations
- Clearly developer-oriented; the concepts assume you know what an embedding and a vector store are
- Self-hosting means you own upgrades, backups, the vector database and the inevitable 2am restart
- Focused on LLM app building rather than broad app-to-app automation, so it is a poor Zapier replacement
- Message credits on cloud plans are consumed by app usage, and the rate is not broken down per feature on the pricing page
- The licence is Apache 2.0 plus two extra conditions - no multi-tenant operation without written authorisation, and no removing Dify's logo or copyright from the console - so read it before building a commercial product on it
- Storage limits on cloud tiers are modest relative to real document sets, and 5GB fills faster than people expect
Dify pricing
Dify prices cloud workspaces annually with a monthly message-credit allowance, rather than per seat or per task. Published pricing as of August 2026: Sandbox free with 200 message credits, one team member and 50MB of knowledge storage; Professional at $590 a year per workspace with 5,000 monthly message credits, three team members and 5GB of storage; Team at $1,590 a year per workspace with 10,000 monthly credits, fifty team members and 20GB; Enterprise custom quoted. The Community Edition is free to self-host under Dify's own open-source licence. Note the shape of that pricing: the jump from three to fifty team members costs $1,000 a year, which is far cheaper than the equivalent seat count on almost any per-seat competitor.
| Plan | Price | What you get |
|---|---|---|
| Community (self-host) | $0 | Free to self-host under Dify's open-source licence; you pay hosting and your own vector database |
| Sandbox | $0 | 200 message credits, 1 team member, 5 apps, 50 knowledge documents, 50MB storage, 3,000 trigger events, 5,000/mo API rate limit (as of Aug 2026) |
| Professional | $590/yr | 5,000 monthly message credits, 3 team members, 50 apps, 500 knowledge documents, 5GB storage, 20,000 trigger events/mo, unlimited API rate limit |
| Team | $1,590/yr | 10,000 monthly message credits, 50 team members, 200 apps, 1,000 knowledge documents, 20GB storage, unlimited trigger events and API rate limit |
| Enterprise | Custom | Custom limits, private deployment, dedicated support |
Pricing reflects public plans as of August 6, 2026 and can change. Check Dify for the latest.
What people actually build with Dify
Dify is an LLM application platform, and the builds that succeed on it are applications with users rather than automations with schedules. The distinction sounds academic until you have watched someone try to use it as a Zapier replacement.
The builds that work
An internal staff assistant over the company's own documents. Someone uploads the handbook, the SOPs, the supplier contracts and the price list into a knowledge base, Dify handles the chunking and embedding, and staff ask questions in a browser or through Slack. A dental practice using it so front-desk staff can check what a treatment plan includes without interrupting a clinician is the sort of thing that quietly saves an hour a day.
A customer-facing product assistant embedded in a website, answering from your documentation rather than the model's training data. Dify's citation support matters here, because a grounded answer with a link to the source page is defensible in a way a confident paragraph is not.
A document extraction workflow behind an API. Dify's visual workflow builder chains an ingestion step, an extraction prompt and a validation step, and the whole thing is exposed as an endpoint your automation platform calls. This is the pattern for an accounting firm pulling structured fields out of supplier invoices before they reach the ledger.
A multi-model routing app that sends high-volume classification to a cheap model and escalates the judgement calls to a flagship. Because Dify is model-agnostic across OpenAI, Anthropic, Google and open-weight models run locally, this is configuration rather than engineering, and it is usually the single largest lever on an AI bill.
A shared workspace where a whole department builds small internal tools. This is where the fifty-member allowance on the Team plan stops being a spec-sheet number and starts being the reason to buy it.
What Dify is genuinely bad at
App-to-app automation. There is no connector catalogue in the sense a general automation tool means it, so moving a record from a web form into your CRM is work Dify makes harder rather than easier. Use n8n or Make.com for that and call Dify for the reasoning.
It is also a poor fit for anyone without a technical owner. The concepts assume you know what a vector embedding is, and the value is concentrated in the self-hosted edition, which means containers, a database and upgrades.
Bottom line: Dify is for LLM applications with users - a document assistant, a grounded support bot, an extraction endpoint - and it is the wrong layer for moving records between business systems.
What Dify actually costs at small-business volume
Dify's cloud meter is message credits, billed annually per workspace rather than per seat. As of August 2026 that is 200 credits on the free Sandbox, 5,000 a month on Professional at $590 a year, and 10,000 a month on Team at $1,590 a year. Converted to a monthly figure, Professional is about $49 and Team about $133. If your use is an internal assistant that answers staff questions, 5,000 messages a month is roughly 250 conversations of twenty turns - comfortable for a team of twenty, tight for a customer-facing bot on a busy website.
The genuinely unusual part of that pricing is the seat allowance, and it is worth pausing on. Professional includes 3 team members; Team includes 50. The step from three people to fifty costs $1,000 a year. Almost every competitor in this directory would charge per seat for that difference and arrive at a number several times larger. If you have a team of fifteen who all need to build or administer apps, Dify's Team plan is one of the best-value line items on this site.
The limits that will actually stop you are not the credits. As of August 2026 Sandbox allows 5 apps and 50 knowledge documents, Professional 50 apps and 500 documents with 5GB of storage, and Team 200 apps and 1,000 documents with 20GB. For a document assistant, the document count is the real ceiling: 500 documents sounds generous until you point it at a policy library or three years of contracts. Count your actual corpus before you choose a tier, because that is the number that forces an upgrade, not message volume.
And remember the credits do not include the model. Dify is model-agnostic, so on top of the subscription you pay OpenAI, Anthropic or whoever you route to. Self-hosting the Community Edition removes the subscription entirely and leaves only that model spend plus a server - which for a technical business is usually the right answer.
| Line item | Dify Cloud (Professional) | Community Edition, self-hosted |
|---|---|---|
| Software licence | $590/yr, about $49/mo | $0, under a modified Apache 2.0 licence |
| Server and database | Included | $30-$60/mo for app, Postgres, Redis and a vector store |
| Upgrades | Vendor's job | 2-4 hrs/mo; releases carry ordered migration steps |
| Document limit | 500 documents, 5GB on Professional | Your disk, which is the main reason to self-host |
| Model tokens | Billed by your provider | Billed by your provider |
| Realistic all-in monthly | About $49 plus tokens | $30-$60 plus 2-4 hrs of staff time plus tokens |
| Self-hosting wins when | Never on cash alone at this volume | Your corpus exceeds the cloud document caps, or the data cannot leave |
Self-host versus cloud at the reference workload
Our reference workload is 1,000 triage items a month with one AI step, which is 1,000 message credits. That is five times the free Sandbox allowance and a fifth of Professional's, so the cloud answer is $590 a year, about $49 a month, with 4,000 credits spare.
Self-hosting is where the arithmetic gets interesting, and it is not the container that costs you. Dify needs more than a small box: the stack includes the API and worker services, a Postgres database, Redis and a vector store, and once you index a real document corpus the vector store is the component that grows. A realistic figure is $30 to $60 a month of server rather than the $5 people quote for lighter tools.
Then count the person. The GitHub API on 6 August 2026 showed 151,483 stars, 937 open issues and a last push on 6 August 2026, the same day. That is one of the most actively developed projects in this entire directory, which is excellent for capability and a real maintenance obligation: releases carry migration steps that must be run in order, and a deployment that skips several of them will meet them all at once. Two to four hours a month is an honest budget for upgrades, backups and vector store housekeeping.
Bottom line: At 1,000 messages a month, self-hosted Dify costs more in cash than the $49-a-month cloud plan once you count the server, so self-host for data control or corpus size, not to save money.
The pricing gotcha: trigger events, and the licence
The allowance nobody budgets for is trigger events. Sandbox includes 3,000, Professional 20,000 a month, and Team unlimited, as of August 2026. If you are using Dify as an interactive assistant that is irrelevant. If you are using it as an automation that fires on a schedule or a webhook, 20,000 events a month is your real ceiling and it is a different number from your message credits entirely. Two meters, two ways to run out. Check which one your use case actually consumes.
The API rate limit follows the same pattern: Sandbox is capped at 5,000 API calls a month while paid tiers are listed as unlimited. That makes the free tier unsuitable for anything programmatic beyond a demo, which is presumably the intention.
The bigger gotcha is not a price at all - it is the licence, and it catches exactly the businesses most attracted to Dify. The Community Edition is Apache 2.0 with two additional conditions written into the licence file. First, you may not use the Dify source code to operate a multi-tenant environment without written authorisation, where a tenant means one workspace with separated data and configuration. Second, you may not remove or modify the logo or copyright information in the Dify console or applications, a restriction that applies to the frontend. Read together, those two clauses rule out the obvious agency play: you cannot self-host one Dify instance, carve it into per-client workspaces, white-label it and resell it. Running it for your own business is fine. Running it as a product for others needs a commercial licence, and finding that out after you have built the product is expensive.
Bottom line: Message credits and trigger events are two separate meters, and the licence forbids operating Dify multi-tenant or removing its branding without written authorisation.
What breaks in production, and how you find out
Self-hosted Dify is a container stack with a vector database attached, and the failure modes are the ones that come with that territory rather than anything peculiar to Dify. Upgrades are the recurring cost: the project moves quickly, and a deployment that skips several releases will meet migration steps it has to run in order. Pin your version, read the release notes, and upgrade deliberately rather than pulling the latest tag. The GitHub API on 6 August 2026 recorded a push that same day, so the pace is not slowing.
The operationally important failure is specific to retrieval apps and it is the one that damages trust rather than uptime: the knowledge base goes stale. Documents get ingested once, the underlying policy changes, and the assistant carries on answering confidently from the superseded version. Nothing errors, nothing alerts, and the first sign is a member of staff acting on wrong information. Whoever owns a Dify deployment owns a re-ingestion schedule and a habit of spot-checking answers against source documents. That is not optional maintenance; it is the job.
The second retrieval-specific problem is chunking. Dify handles document splitting for you, which is exactly why it is worth using, but default chunk settings that work for prose fail on tables, forms and long structured contracts - the retrieval returns fragments that read plausibly and answer the wrong question. If your documents are structured, expect to tune chunk size and overlap, and expect that tuning to be the difference between a useful assistant and an embarrassing one.
On the cloud side, storage is the quiet ceiling: 5GB on Professional and 20GB on Team as of August 2026 sounds like a lot until scanned PDFs are involved, at which point it is not.
Bottom line: The failure that costs you users is not downtime, it is a stale knowledge base answering confidently from last quarter's policy, so a re-ingestion schedule is part of the build, not an extra.
What it connects to that you already run
Dify's integration strength is on the model side rather than the SaaS side, and being clear about that saves disappointment. It is genuinely model-agnostic - OpenAI, Anthropic, Google, open-weight models via local runtimes and a long list of others - which lets you do the thing that actually controls an AI bill: route cheap, high-volume classification to a small model and reserve a flagship for the steps that need judgement. Vector storage is similarly pluggable rather than locked to one provider.
For business systems, the honest framing is that Dify builds the AI application and you integrate it, rather than Dify integrating for you. Apps are exposed as APIs and as embeddable web apps, so the normal pattern is to call Dify from the automation platform you already run, or to embed the assistant in a site or an internal tool. If what you need is a record moved from a form into a CRM, Dify is the wrong layer and a general automation tool does it in an afternoon.
Where a small business gets the most from it: an internal assistant over its own documents - the staff handbook, the SOPs, the supplier contracts - reachable from a browser and from Slack or Teams via whatever automation glue you already have. That is a well-defined job Dify does properly and cheaply.
Bottom line: Dify integrates models and document sources, not business SaaS, so the working architecture is your automation platform calling a Dify app over its API.
Dify alternatives: what to pick instead, and when
The commonest reason to walk away from Dify is that you did not want an LLM app platform, you wanted automation. If your problem is that a form submission should create a CRM record and notify someone, every tool below beats Dify and it is not close. Pick n8n if you want that plus a competent AI agent node, which for most businesses removes the need for a second platform entirely. Pick Make.com if the workflows are branchy and deterministic and you want the cheapest per-step meter in the category. Pick Zapier if the deciding factor is the connector you cannot find anywhere else, and accept that its per-task meter makes a five-step workflow five times more expensive than a per-execution one.
Within the LLM app category, pick Flowise if you want to prototype fast and a developer will own it, and accept that you are giving up knowledge base management and the operations view. Pick Activepieces if the reason you were drawn to Dify was self-hosting, because MIT licensing carries none of Dify's multi-tenant and branding conditions. And pick Stack AI if what you actually need is a compliance attestation and a contract rather than software, which is a legitimate thing to need and not something a self-hosted project can give you.
| Tool | Billing unit | Monthly cost at the reference workload | Who it suits | Does better than Dify |
|---|---|---|---|---|
| Dify | Message credit, per workspace per year | About $49/mo on Professional, or $30-$60 of server self-hosted | Teams shipping an LLM app to colleagues | Knowledge base, model routing and 50 seats for $1,590/yr |
| n8n | Execution (whole workflow run) | EUR 20/mo Starter covers 2,500 executions | Businesses automating across real business systems | Connectors, scheduling, retries and error branches |
| Make.com | Operation (one step) | $9/mo Core covers 10,000 credits; 5,000 used here | Branchy deterministic workflows on a budget | Cheapest per-step price in this comparison |
| Zapier | Task (one step after the trigger) | $89/mo annual, $133.50 monthly, for 5,000 tasks | Teams that need the long-tail connector | The largest connector catalogue by a wide margin |
| Activepieces | Credit: 1 per flow run, steps free | $20/mo Plus, or free self-hosted with no run cap | Self-hosters who want a clean licence | MIT licensing with no multi-tenant restriction |
| Flowise | Prediction (one flow run) | $35/mo Starter, or roughly $10-$20 of server | Developers prototyping a chain quickly | Lower operational weight to stand up and run |
Bottom line: If your workflow is mostly moving records between systems, n8n or Make.com will beat Dify on both effort and cost; Dify wins only when the document reasoning is the product.
Migration and lock-in: can you get your work out?
Dify's lock-in position is among the best in this directory, for one structural reason: the Community Edition is the same software as the cloud product and it is free to run. If the vendor's pricing changes, or the company's direction changes, you have a fully functional escape hatch that does not depend on the vendor's cooperation. That is worth more over five years than most feature comparisons.
Say the licence part plainly, though, because no vendor page does. Dify is not open source in the strict sense. The LICENSE file describes it as a modified Apache License 2.0 with additional conditions, and GitHub does not recognise it as a standard licence. Two conditions matter. You may not use the Dify source code to operate a multi-tenant environment without written authorisation from Dify, where a tenant is one workspace with separated data and configuration. And you may not remove or modify the logo or copyright information in the console or in the applications you build with its frontend. So the escape hatch is unconditional for a business running its own assistant, and conditional for an agency planning to host client workspaces or ship a white-labelled product. That is a source-available restriction wearing an open-source name, and it changes the lock-in answer for exactly the buyers who care most about it.
On data specifically, the thing to protect is the corpus, not the app. Apps and workflows are configuration you can rebuild in a day; a curated, cleaned, chunked knowledge base is weeks of work. Keep the source documents in a store you own - a drive, a repository, a document management system - and treat Dify's knowledge base as a derived index that can be rebuilt from them. Do that, and moving to a different platform is an ingestion job rather than an archaeology project. Skip it, and the only clean copy of your organised knowledge lives inside somebody else's product.
Bottom line: Dify's licence is a modified Apache 2.0, not true open source: self-hosting for your own business is unrestricted, but operating it multi-tenant or removing its branding requires written authorisation.
Dify FAQ
How much does Dify cost?
Self-hosted, nothing for the software - your cost is a server capable of running the stack plus a vector database, which for a small deployment is realistically $20 to $80 a month depending on how much you index. On cloud, published pricing as of August 2026 is $590 a year for Professional with 5,000 monthly message credits and three members, or $1,590 a year for Team with 10,000 credits and fifty members. Model tokens are billed separately by whichever provider you point it at.
Why is Dify's cloud pricing shaped so differently?
Because it bills per workspace per year with a member allowance, not per seat per month. The practical effect is dramatic for a small business: going from three users to fifty costs $1,000 a year, whereas a per-seat competitor charging $30 a seat monthly would want over $16,000 for the same headcount. If you want a lot of people to have access to an internal AI tool but each person uses it lightly, this pricing model is one of the friendliest in the category.
What goes wrong with self-hosted Dify in production?
Vector database growth is the quiet one - indexes get large, disks fill, and retrieval slows before anything actually errors. Second is upgrades: the project moves fast and jumping several versions can require migration work, so pin a version and upgrade deliberately. Third is retrieval quality drifting as documents are added, because chunking settings that worked for twenty policy documents behave differently at two thousand. Schedule a quarterly check of retrieval accuracy against a fixed set of test questions and you will catch it early.
Who should not choose Dify?
Any business without a technical owner, and any business whose problem is app-to-app automation rather than AI applications. Dify will not replace a workflow automation tool - it has nothing like the connector catalogue - and self-hosting it without someone who is comfortable with containers, environment variables and database backups turns a free platform into an expensive outage. Cloud removes the operational burden but keeps the developer-shaped concepts.
Does Dify work with what we already use?
It integrates at the model and data layer rather than the SaaS layer: many model providers, common vector databases, and document ingestion from files and URLs. It does not have deep native connectors for QuickBooks, Shopify or your CRM the way a general automation tool does. The common pattern we build is Dify or a similar RAG layer doing the document work, with a workflow tool such as n8n or Make handling the business plumbing around it.
How locked in are we with Dify?
Materially less than with any proprietary competitor, which is the strongest practical argument for it. Because you can run the Community Edition yourself, no vendor can raise your price, change your terms or discontinue your tier. Even on cloud, the existence of a self-hostable escape route is real leverage. What still has to be rebuilt if you leave the ecosystem entirely is the workflow definitions - but your prompts, your document corpus and your evaluation set are all portable artefacts you keep regardless.
Is Dify's licence actually open source?
It is open source in the everyday sense - the code is public and free to self-host - but it is published under Dify's own licence rather than a standard OSI-approved one, and that licence carries conditions. If you are simply running it for your own business, this is unlikely to affect you. If you plan to build a commercial product or an agency offering on top of it, read the licence terms properly first, because that is exactly the scenario these bespoke licences are written to govern.
Dify or Flowise for building an AI assistant?
Both are open-source visual builders for LLM applications and both self-host. Dify is the more complete product: knowledge base management, model routing, prompt tooling and an operations view come as part of the platform. Flowise is closer to a visual layer over familiar framework primitives, which suits developers who already think in chains and want to prototype fast. For a business assistant that other people will actually use day to day, Dify's surrounding tooling generally saves more time than Flowise's flexibility.
Can you set up a document assistant for us?
Yes, and this is one of the most requested builds we get - staff asking questions of policy documents, quotes, contracts or product manuals. We scope it on a free automation audit, pick the platform on the merits of your data and privacy constraints rather than a preference, and hand over the deployment, the prompts and documentation you own, plus a recurring report of what it answered and where it struggled. Self-hosting is often the right answer, and we will tell you when it is not.
Looking at alternatives? Dify is a solid pick if you want an open-source base for AI apps and RAG assistants and you have the skills to run it - and on lock-in it is one of the better positions available, because self-hosting means nobody can change your pricing or terms out from under you. What you trade is that the operational burden is permanently yours. Autonoly is the managed, no-code alternative for people who want agents doing tasks now rather than a platform to build on, and who would rather describe a job than assemble a retrieval pipeline. If you have a developer who enjoys this, Dify; if you do not, do not pretend otherwise. See the Autonoly review.
