Skip to main content
For the beginning of the deployment, you need to prepare the following resources.

​
Requirements

  • Helm 3.14+
  • Kubernetes 1.24+
    1. Important For the License Activation, contact your IT team to provide the necessary permissions.
      • ServiceAccount (Required)
      • Role / RoleBinding (Required)
    2. Warning If you are using a restricted environment, please make sure to allow the pods to run as root (like OpenShift).
  • Cloud Provider (Supported)
    • AWS, Azure, Aliyun, Tencent Cloud, GCP

​
Domains

Dify Enterprise requires 6 domains to be set up. The domains are:
  • Console: console.dify.local
  • Services API: api.dify.local
  • APP: app.dify.local
  • Files: upload.dify.local
  • Enterprise Dashboard: enterprise.dify.local
  • Trigger: trigger.dify.local

​
Testing Deployment Resources

  • Kubernetes Cluster
    • 1 Worker Node: 4 CPU, 16 GB RAM
  • Persistence Storage
    • s3, amazon-s3, azure-blob, aliyun-oss, google-storage, tencent-cos
    • 100 GB Storage
  • Postgres Database
    • Version 14+
    • 2 CPU, 4 GB RAM
    • 256 GB Storage
  • Redis Database
    • Version 6+
    • 1 GB RAM
  • Vector DB Virtual Machine - Qdrant Single Node
    • 1 Virtual Machines
    • 4 CPU, 8 GB RAM
    • 100 GB Storage

​
Production Deployment Resources

  • Kubernetes Cluster
    • 6 Worker Nodes: Each one 8 CPU, 32 GB RAM
  • Persistence Storage
    • s3, amazon-s3, azure-blob, aliyun-oss, google-storage, tencent-cos
    • 512 GB Storage
  • Postgres Database
    • Version 14+
    • 4 CPU, 8 GB RAM
    • 512 GB SSD Storage
  • Redis Database
    • Version 6+
    • 2 GB RAM
  • Vector DB Virtual Machine - Qdrant Cluster
    • 3 Virtual Machines
    • 8 CPU, 64 GB RAM
    • 100 GB Storage