
# Dify Self-Hosted

Visual AI application and RAG workflow platform available as a self-hosted container stack.

Canonical page: https://launchinyourcloud.com/directory/dify/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


1 listing.


## Dify Self-Hosted

Visual AI application and RAG workflow platform available as a self-hosted container stack.

- Listing: https://launchinyourcloud.com/directory/dify/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: alibaba
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Modified Apache 2.0 terms; multi-workspace service operation and frontend branding can require commercial authorization.
- Licensing model: source-available
- Installation: Official Docker Compose deployment; pin a release and configure its required services.
- Architecture: Customer-operated application, workers, PostgreSQL and vector-store services
- Operations: Customer operates the containers, persistent stores, secrets, backups and upgrades; commercial edition support varies.
- Product website: https://dify.ai/
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Self-hosting Dify does not itself host every model used by a flow. Model-provider plugins, embedding services, tools and connectors may send inputs or retrieved content outside the deployment. Select local endpoints where required and review each dependency. This entry does not conflate the generic self-hosted stack with the separately licensed AWS Premium edition. Dify 1.20.0 changes deployment and API behavior: OPENAPI_ENABLED defaults to true, shared.env is retired, six migrations apply from 1.19, and HITL, plugin-daemon, OpenShell, and optional file-scanning requirements change. It also fixes OAuth callback reuse, member-role enforcement, vector deletion scope, public stream detail exposure, and CVE-2026-116591.

Classified here as source-available because the upstream license modifies Apache 2.0 with multi-workspace service and frontend-branding conditions. Some uses require separate commercial authorization; this is not an unmodified Apache-licensed core.

Docker Compose runs application services, workers and persistent database/vector-store containers on a host. This is provisioned server/container infrastructure; using a managed external model does not make this platform serverless.


### Category fit

- ai-applications-rag: Visual application, agent-workflow and retrieval-augmented generation platform. The application platform is deployable; selected models and plugins are separate dependencies.

- ai-tools: Visual AI application and RAG workflow platform available as a self-hosted container stack.

### Deployment boundaries


- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.alibabacloud.com/help/en/openapi/integrating-openapi-mcp-server-in-dify (checked 2026-11-12). Source: https://help.aliyun.com/en/compute-nest/use-cases/dify-community-edition-service-instance-deployment-document (checked 2026-11-12). 


### Cloud deployment evidence

- Dify Docker deployment on Alibaba Cloud ECS (alibaba): https://www.alibabacloud.com/help/en/openapi/integrating-openapi-mcp-server-in-dify
  Alibaba Cloud documents cloning upstream Dify and running its Docker deployment on a customer ECS instance. The example then integrates an MCP server; model providers and other outbound integrations must be reviewed separately.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.

- Dify Community Edition full application on Alibaba Compute Nest (alibaba): https://help.aliyun.com/en/compute-nest/use-cases/dify-community-edition-service-instance-deployment-document
  Alibaba documents a Dify Community Edition service instance that creates ECS compute in the customer-selected VPC, zone and region, then exposes the installed Dify application for administrator registration. This is application hosting rather than an MCP/model connector, and is separate from the licensed Dify AWS Premium offering. Review model endpoints and release compatibility.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Docker Compose deployment: https://docs.dify.ai/en/self-host/deploy/quick-start/docker-compose

- Application capabilities and integrations: https://github.com/langgenius/dify

- Current license and additional conditions: https://github.com/langgenius/dify/blob/main/LICENSE

- Dify Community Edition full application on Alibaba Compute Nest: https://help.aliyun.com/en/compute-nest/use-cases/dify-community-edition-service-instance-deployment-document

- Dify 1.20.0 release: https://github.com/langgenius/dify/releases/tag/1.20.0

### Licensing sources

- https://github.com/langgenius/dify/blob/main/LICENSE

### Infrastructure sources

- https://docs.dify.ai/en/self-host/deploy/quick-start/docker-compose


### Buyer diligence


Research coverage: 6/12 fields (50%); 6 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. SAML, OIDC and OAuth2 SSO appear in the self-hosted Enterprise feature comparison and are enabled by an Enterprise licence. This does not establish those features for an unlicensed Community installation; confirm identity-provider and end-user/admin coverage. Scope: Self-hosted Enterprise licence; Community differs. Source: https://dify.ai/pricing/dify-enterprise (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Current advisory review: Dify 1.20.0 fixes OAuth callback reuse, member-role enforcement, vector deletion scope, public stream detail exposure, CVE-2026-116591, and security dependencies. Apply the 1.20.0 migrations and configuration changes, or a later supported release, and retest authentication and public endpoints. Scope: Upstream Dify 1.20.0 release; consult its linked advisories for component-specific ranges.. Source: https://github.com/langgenius/dify/releases/tag/1.20.0 (reviewed 2026-11-18).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream Compose file is generated from its template and environment configuration. Use a consistent release checkout rather than mixing generated files or dependency settings across releases. Scope: Upstream multi-service deployment; models and integrations need separate configuration. Source: https://github.com/langgenius/dify/blob/main/docker/docker-compose.yaml (reviewed 2026-11-14). Deployment artifact: https://github.com/langgenius/dify/blob/main/docker/docker-compose.yaml. Artifact reference: main (moving branch).

- Minimum footprint / sizing: Documented. The Compose quickstart specifies at least 2 CPU cores and 4 GiB RAM. The selected database, vector store, models and workload may require more resources. Scope: Quickstart application stack; not model-serving or production HA sizing. Source: https://docs.dify.ai/en/self-host/deploy/quick-start/docker-compose (reviewed 2026-11-14).

- License pricing: Documented. Dify uses modified Apache-2.0 terms, with additional conditions for multi-tenant workspaces and frontend branding. Certain uses require a commercial licence. Do not treat it as unmodified Apache-2.0; Enterprise, support and model-provider charges are separate. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/langgenius/dify/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Dify 1.20.0 was published November 18, 2026. It includes six migrations from 1.19, retires shared.env, changes OPENAPI_ENABLED and HITL behavior, and requires review of plugin-daemon, OpenShell, and file-scanning configuration. Scope: Upstream Dify self-hosted 1.20 release. Source: https://github.com/langgenius/dify/releases/tag/1.20.0 (reviewed 2026-11-18).




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- Dify 1.20.0 security update (security-advisory): Dify 1.20.0 fixes OAuth callback reuse, member-role enforcement, vector deletion scope, public stream detail exposure, CVE-2026-116591, and security dependencies. Scope: Upstream Dify 1.20.0 release; consult its linked advisories for component-specific ranges. Conditions: Exposure depends on enabled OAuth, public application streams, role configuration, vector stores, and affected dependencies. Action: Apply the 1.20.0 migrations and configuration changes, or a later supported release, and retest authentication and public endpoints. Source: https://github.com/langgenius/dify/releases/tag/1.20.0; reviewed 2026-11-18.



