Production Deployment - Dify Enterprise Docs

Requirements

This requirements can support up to 3000 active users daily. If you have more users, you can scale the resources as needed, or refer to our Performance Tuning Documentation.

Kubernetes Cluster
- 6 Worker Nodes: Each one 8 CPU, 32 GB RAM
Container Registry (Plugins)
- AWS ECR（with AK/SK or IRSA）/ Azure ACR / Aliyun ACR (with AK/SK) / Tencent TCR (with AK/SK) / Dockerhub / Google Artifact Registry
Persistence Storage
- S3 / AWS S3 (with AK/SK or IRSA) / Azure Blob / Aliyun OSS (with AK/SK) / Tencent COS (with AK/SK) / Google GCS
- 512 GB Storage
Postgres Database
- Version 14+
- 8 CPU, 16 GB RAM
- At least 512G SSD
Redis Database
- Version 6+
- 2 GB RAM
Vector DB Virtual Machine - Qdrant Cluster
- 3 Virtual Machines
- 8 CPU, 64 GB RAM
- 100 GB Storage

The `limits` of Dify Services Resources

workerBeat always runs as a single replica. Don’t scale it.

Services	Replicas	CPU	RAM - GB	Total CPU	Total RAM - GB
api	3	3	1	9	3
worker	3	2	1	6	3
triggerWorker	3	2	1	6	3
workerBeat	1	1	1	1	1
web	3	1	1	3	3
sandbox	3	1	2	3	6
enterprise	3	1	2	3	6
enterpriseAudit	3	1	2	3	6
enterpriseFrontend	3	1	1	3	3
ssrfProxy	3	1	1	3	3
unstructured	3	1	2	3	6
plugin_daemon	3	1	3	3	9
plugin_controller	3	1	2	3	6
plugin_connector	3	1	2	3	6
plugin_manager	3	1	2	3	6
gateway	3	1	2	3	6
minio	1	1	2	1	2
			Total	59	78

Deployment

1. Get Helm Repository Info

helm repo add dify https://langgenius.github.io/dify-helm
helm repo update

For more information, please refer to the Dify Helm Chart.

2. Save Helm Chart Values

Save Helm chart values to a file named values.yaml.
Update the values.yaml file with your configuration.

Please replace the #REPLACE_ME# placeholders with your actual values.
Please replace “dify123456” with your own value.
The global.appSecretKey and enterprise.appSecretKey must be different.

###################################
# Please replace "dify123456" with your own value
###################################
global:
  appSecretKey: 'dify123456'
  innerApiKey: 'dify123456'
  consoleApiDomain: "console.dify.local"
  consoleWebDomain: "console.dify.local"
  serviceApiDomain: "api.dify.local"
  appApiDomain: "app.dify.local"
  appWebDomain: "app.dify.local"
  filesDomain: "upload.dify.local"
  enterpriseDomain: "enterprise.dify.local"
  triggerDomain: "trigger.dify.local"

ingress:
  enabled: true
  className: "nginx"
  annotations: {
    # set file upload size limit
    nginx.ingress.kubernetes.io/proxy-body-size: "15m"
  }

api:
  replicas: 3
  serverWorkerAmount: 1
  resources:
    limits:
      cpu: 3000m
      memory: 1024Mi
    requests:
      cpu: 1500m
      memory: 512Mi
worker:
  replicas: 3
  celeryWorkerAmount: 1
  resources:
    limits:
      cpu: 2000m
      memory: 1024Mi
    requests:
      cpu: 1000m
      memory: 512Mi
triggerWorker:
  replicas: 3
  celeryWorkerAmount: 1
  resources:
    limits:
      cpu: 2000m
      memory: 1024Mi
    requests:
      cpu: 1000m
      memory: 512Mi
workerBeat:
  resources:
    limits:
      cpu: 1000m
      memory: 1024Mi
    requests:
      cpu: 500m
      memory: 512Mi
web:
  replicas: 3
  resources:
    limits:
      cpu: 1000m
      memory: 1024Mi
    requests:
      cpu: 500m
      memory: 512Mi
sandbox:
  replicas: 3
  resources:
    limits:
      cpu: 1000m
      memory: 2048Mi
    requests:
      cpu: 500m
      memory: 1024Mi
enterprise:
  replicas: 3
  appSecretKey: "dify123456"
  adminAPIsSecretKeySalt: "dify123456"
  passwordEncryptionKey: "dify123456"
  resources:
    limits:
      cpu: 1000m
      memory: 2048Mi
    requests:
      cpu: 500m
      memory: 1024Mi
enterpriseAudit:
  replicas: 3
  resources:
    limits:
      cpu: 1000m
      memory: 2048Mi
    requests:
      cpu: 500m
      memory: 1024Mi
enterpriseFrontend:
  replicas: 3
  resources:
    limits:
      cpu: 1000m
      memory: 1024Mi
    requests:
      cpu: 500m
      memory: 512Mi
ssrfProxy:
  replicas: 3
  resources:
    limits:
      cpu: 1000m
      memory: 1024Mi
    requests:
      cpu: 500m
      memory: 512Mi
unstructured:
  replicas: 3
  resources:
    limits:
      cpu: 1000m
      memory: 2048Mi
    requests:
      cpu: 500m
      memory: 1024Mi
plugin_daemon:
  replicas: 3
  resources:
    limits:
      cpu: 1000m
      memory: 3072Mi
    requests:
      cpu: 500m
      memory: 1536Mi
plugin_controller:
  replicas: 3
  resources:
    limits:
      cpu: 1000m
      memory: 2048Mi
    requests:
      cpu: 500m
      memory: 1024Mi
plugin_connector:
  replicas: 3
  resources:
    limits:
      cpu: 1000m
      memory: 2048Mi
    requests:
      cpu: 500m
      memory: 1024Mi
plugin_manager:
  replicas: 3
  resources:
    limits:
      cpu: 1000m
      memory: 2048Mi
    requests:
      cpu: 500m
      memory: 1024Mi
gateway:
  replicas: 3
  resources:
    limits:
      cpu: 1000m
      memory: 2048Mi
    requests:
      cpu: 500m
      memory: 1024Mi
minio:
  replicas: 1
  resources:
    limits:
      cpu: 1000m
      memory: 2048Mi
    requests:
      cpu: 500m
      memory: 1024Mi

###################################
# Persistence Configration
###################################
persistence:
  type: "s3"
  s3:
    endpoint: "https://xxx.r2.cloudflarestorage.com"
    accessKey: "#REPLACE_ME#"
    secretKey: "#REPLACE_ME#"
    region: "us-east-1"
    bucketName: "your-bucket-name"
    addressType: ""
    useAwsManagedIam: false
    useAwsS3: true

###################################
# External postgres
###################################
externalPostgres:
  enabled: true
  address: "#REPLACE_ME#"
  port: 5432
  credentials:
    dify:
      database: "dify"
      username: "postgres"
      password: "#REPLACE_ME#"
      sslmode: "require"
    plugin_daemon:
      database: "dify_plugin_daemon"
      username: "postgres"
      password: "#REPLACE_ME#"
      sslmode: "require"
    enterprise:
      database: "enterprise"
      username: "postgres"
      password: "#REPLACE_ME#"
      sslmode: "require"
    audit:
      database: "audit"
      username: "postgres"
      password: "#REPLACE_ME#"
      sslmode: "require"

###################################
# External Redis
###################################
externalRedis:
  enabled: true
  host: "#REPLACE_ME#"
  port: 6379
  username: ""
  password: "#REPLACE_ME#"
  useSSL: false

###################################
# External Qdrant
###################################
vectorDB:
  useExternal: true
  externalType: "qdrant"
  externalQdrant:
    endpoint: "http://your-qdrant-cluster-url.qdrant.tech/"
    apiKey: "#REPLACE_ME#"

imagePullSecrets: []

3. Configure `Container Registry`

3.1 Container Registry for Plugins
- For more information, please refer to the Container Registry for Plugins.
3.2 Container Registry for Services
- For more information, please refer to the Container Registry.

4. Configure `Persistence Storage`

For more information, please refer to the Persistence Storage.

5. Configure `External postgres`

For more information, please refer to the External Postgres.

6. Configure `External Redis`

For more information, please refer to the External Redis.

7. Configure `External Qdrant`

For more information, please refer to the External Qdrant Cluster.

8. Configure `Ingress Controller`

For more information, please refer to the Ingress Controller.

9. Install Dify Helm Chart

helm upgrade -i dify -f values.yaml dify/dify

10. Verify Installation

For more information, please refer to the Verify Services Status.

Advanced Configuration

1. Domain and SSL Certificate

For more information, please refer to the Domain and SSL Certificate.

2. Email Provider

For more information, please refer to the Email Provider.

3. Performance Tuning

For more information, please refer to the Performance Tuning.

​Requirements

​The limits of Dify Services Resources

​Deployment

​1. Get Helm Repository Info

​2. Save Helm Chart Values

​3. Configure Container Registry

​4. Configure Persistence Storage

​5. Configure External postgres

​6. Configure External Redis

​7. Configure External Qdrant

​8. Configure Ingress Controller

​9. Install Dify Helm Chart

​10. Verify Installation

​Advanced Configuration

​1. Domain and SSL Certificate

​2. Email Provider

​3. Performance Tuning

Requirements

The `limits` of Dify Services Resources

Deployment

1. Get Helm Repository Info

2. Save Helm Chart Values

3. Configure `Container Registry`

4. Configure `Persistence Storage`

5. Configure `External postgres`

6. Configure `External Redis`

7. Configure `External Qdrant`

8. Configure `Ingress Controller`

9. Install Dify Helm Chart

10. Verify Installation

Advanced Configuration

1. Domain and SSL Certificate

2. Email Provider

3. Performance Tuning