Dify Self-Hosted

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

5 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

Dify 1.20.0 security update

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.

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.

Primary source · Reviewed 2026-11-18

What lands where

  1. Supplied by

    Vendor or project

    Official Docker Compose deployment; pin a release and configure its required services.

  2. Operated by

    Your team

    Customer operates the containers, persistent stores, secrets, backups and upgrades; commercial edition support varies.

Deployment boundaries by provider

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodOfficial Docker Compose deployment; pin a release and configure its required services.
InfrastructureServers / containers
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.
Licensing modelSource Available
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.
LicenseModified Apache 2.0 terms; multi-workspace service operation and frontend branding can require commercial authorization.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

6 of 12 fields researched (50%) · 6 documented · 0 unresolved. Evidence coverage is not a feature score.

Single sign-on
Edition-dependentEvidence and scope for Single sign-on

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.

Self-hosted Enterprise licence; Community differs · Source ↗ · Reviewed 2026-11-20

Edition-dependent · Editor reviewed.

Security controls
DocumentedEvidence and scope for Security controls

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.

Upstream Dify 1.20.0 release; consult its linked advisories for component-specific ranges. · Source ↗ · Reviewed 2026-11-18

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

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.

Upstream multi-service deployment; models and integrations need separate configuration · Deployment artifact ↗ (main (moving branch)) · Reviewed 2026-11-14

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

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.

Quickstart application stack; not model-serving or production HA sizing · Source ↗ · Reviewed 2026-11-14

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

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.

Upstream core licence; commercial features, support and hosting priced separately · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

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.

Upstream Dify self-hosted 1.20 release · Source ↗ · Reviewed 2026-11-18

Documented · Editor reviewed.

Show all fields (6 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.

Scope & considerations

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.

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 & infrastructure
Visual AI application and RAG workflow platform available as a self-hosted container stack.

Compare within AI applications & RAG

  • AnythingLLM DockerSelf-hosted application for document-grounded AI chat, retrieval and agents.
    • AWS
    • Google Cloud
    • Railway
    Customer-operated · Open Source / Open Core
  • Langflow Self-HostedVisual AI workflow and agent builder with Docker and persistent PostgreSQL deployment.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • LibreChat Self-HostedSelf-hosted multi-model AI chat, agent and retrieval platform with documented Railway and DigitalOcean deployments.
    • DigitalOcean
    • Railway
    Customer-operated · Open Source / Open Core
  • MaxKB Community EditionOpen-source knowledge-base, RAG and agent-workflow platform deployable into an Alibaba Cloud account.
    • Alibaba Cloud
    Customer-operated · Open Source / Open Core
  • Onyx Self-HostedSelf-hosted enterprise search and AI assistant platform with connectors and retrieval infrastructure.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    Customer-operated · Open Source / Open Core
  • Open WebUI Self-HostedSelf-hosted AI chat and knowledge interface for local model servers and cloud APIs.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Source Available
  • RAGFlowDocument processing and retrieval platform for building RAG and agentic knowledge applications.
    • AWS
    • Azure
    • Google Cloud
    • Alibaba Cloud
    • Railway
    Customer-operated · Open Source / Open Core

These products address related workflows; read their category-fit notes before comparing scope. See all of AI applications & RAG →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Dify Docker deployment on Alibaba Cloud ECS ↗ · Alibaba Cloud

      Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

      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.

    • Dify Community Edition full application on Alibaba Compute Nest ↗ · Alibaba Cloud

      Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

      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.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory