Dify Commercial Use: Open Source License Conditions and Cautions

This article summarizes the license and terms on Dify's official pages as checked on October 2, 2026. It is not legal advice. Licenses and terms may change. If you are unsure whether your use case applies, check with Dify.

The first thing to check for Dify commercial use is where it runs. The open source version you run on your own server follows Dify's license. The cloud version operated by Dify (Dify Cloud) follows the Terms of Service.

Overview of Dify's license

Dify's source code is published on GitHub. Its license is Dify's own, based on Apache License 2.0 with added conditions. The LICENSE states that Dify may be used commercially. This includes using it as a backend service for other apps and as a platform for developing enterprise apps.

On top of that, you must obtain a commercial license from the provider in the following two cases.

1. Multi-tenant services: running a multi-tenant environment with Dify's source code without written permission
2. Logo and copyright notice: removing or changing the logo or copyright notice in the console or apps while using Dify's frontend

Apart from these two, rights and restrictions follow Apache License 2.0. The LICENSE also has a clause in which contributors agree that the provider may make the license stricter or looser. It also states that the product's interaction design is protected by design patents.

Extra condition 1: multi-tenant services

The LICENSE defines one tenant in Dify as one workspace. A workspace is where data and settings are kept separate for each tenant.

So if you run Dify yourself and provide a separate workspace for each customer, this condition applies. Without written permission, you need a commercial license. Treat this separately from using one workspace inside your own company and publishing the apps built there. The LICENSE counts tenants by workspace, not by number of customers. If you are unsure about a setup, check with Dify before you start building.

As of October 2026, the pricing page describes the self-hosted Community edition as a single workspace. Multiple workspaces and enterprise administration are listed as features included only in the Enterprise edition.

Extra condition 2: logo and copyright notice

If you use Dify's frontend, you cannot remove or change the logo and copyright notice in Dify's console or apps. The LICENSE defines the frontend as follows.

• When running from source code: all components in the web/ directory
• When running with Docker: the web image

This condition does not apply if you do not use the frontend, for example when you use Dify as a backend API and build your own interface. If you want to show the interface under your own brand, first decide whether to use the frontend or build your own interface.

Separately from how the logo is handled, the Dify name and logo are trademarks. The Dify Cloud Terms of Service state that no right to use Dify's trademarks is granted without prior written consent. When you mention Dify on a sales page, limit it to explaining that the app was built with Dify.

When you sell or deliver an app you built

What you need to check depends on how you hand over the app.

Whatever the format, decide who pays for AI model usage. If customers enter their own API keys, state on the sales page that those costs fall on the customer. The steps to export an app as a configuration file are explained in Exporting a Dify DSL.

Publishing as a template

You can publish apps you built as templates on Dify Marketplace. Submit them from the Creator Center, and they go live once approved in review. Before submitting, you must install every plugin the app uses from the Marketplace and run the app at least once to check it. DSL files in .yaml or .yml format can be uploaded up to 10MB.

Where to ask when you need a commercial license

As of October 2026, the pricing page includes commercial license rights in the Enterprise edition. Enterprise pricing is quoted individually, and the pricing page directs you to contact sales. Prices are not published.

The pricing page presents the Community edition as being for open source users, individual developers and non-commercial projects. The LICENSE, however, allows commercial use. Check the LICENSE text to see whether your use falls under the two extra conditions, and contact Dify if you are unsure.

Dify Cloud Terms of Service

If you use Dify Cloud, you follow its Terms of Service. According to the pricing page, as of October 2026, Professional costs $590 per workspace per year and Team costs $1,590 per year. Prices and plan limits affect how you run the apps you sell.

Message credits are for trying various AI models inside Dify. After you use them up, you can switch to your own API keys. The main Terms of Service clauses that matter when selling are as follows.

• Ownership of content such as uploaded data stays with the user
• The user is responsible for the safety of the apps they build and for what they publish from their account
• Do not use outputs in a way that misleads people into thinking they were made only by humans
• Do not use it for automated decisions that could adversely affect individual rights without human review
• Verify facts, workflows and code in the output yourself before using them
• Do not use it for high-risk purposes. Do not upload sensitive personal data
• Not using the service, or being unsatisfied with the output, is not grounds for a refund or price reduction

The terms state that they may change. For material changes, Dify says it will give notice before the new terms take effect. For apps you keep selling, check for changes to the terms regularly. A detailed price comparison is in Dify Pricing.

List on Employee Store

Employee Store is a marketplace where companies adopt AI agents built by developers, through a one-time purchase or a monthly plan. Dify Workflows can be listed too. One person (or company) can list several AIs. There is no listing fee and no upfront cost. The commission is 20% of the deal amount and applies only when a deal closes.

After you register through the listing form, the operations team reviews it (usually within 3 business days) and then publishes it. When you are hired, you get a notification and deliver through the delivery box on the site. In your listing, explain where the AI runs, how it is delivered and who pays for AI model costs.