1. Hardware Requirements
1.1 Testing Phase
During the testing phase, you need at least the following environment to launch the most basic Dify Enterprise system:- Kubernetes 1.24+ environment
- 4 CPU cores, 16 GB memory
- Helm 3.14+
- Kubectl
- S3 storage or S3-compatible persistent storage
- Minimum capacity of 50 GB (100 GB recommended)
- Contains all software functions of Dify Enterprise
- Low availability
- Low data reliability
- Not suitable for any production or production-like environment
1.2 Production Environment
In a production environment, you need the following hardware requirements to test Dify Enterprise capabilities in a cluster deployment environment:- Kubernetes cluster
- 1 Worker Node: 4 CPU cores, 16 GB memory
- Persistent storage
- S3, Azure Blob, Alibaba Cloud OSS, Google Cloud Storage, etc.
- 100 GB storage space
- PostgreSQL database
- Version 14+
- 2 CPU cores, 4 GB memory
- 256 GB storage space
- Redis database
- Version 6+
- 1 GB memory
- Vector database VM - Qdrant single node
- 1 virtual machine
- 4 CPU cores, 8 GB memory
- 100 GB storage space
- Kubernetes cluster
- 3 Master Nodes: 4 CPU cores, 16 GB memory each
- 6 Worker Nodes: 8 CPU cores, 32 GB memory each
- Persistent storage
- S3, Azure Blob, Alibaba Cloud OSS, Google Cloud Storage, etc.
- 512 GB storage space
- PostgreSQL database
- Version 14+
- 4 CPU cores, 8 GB memory
- 512 GB SSD storage space
- Redis database
- Version 6+
- 2 GB memory
- Vector database VMs - Qdrant cluster
- 3 virtual machines
- 8 CPU cores, 64 GB memory each
- 100 GB storage space each
1.3 Exceptions
Unless otherwise agreed in writing, the Dify team will not be able to provide standard deployment services in the following situations:- You are using local hardware (such as physical servers) rather than standard cloud service hardware.
- Your hardware is shared with other software.
- You wish to deploy using non-Kubernetes solutions.
- You wish to modify existing software structure, code, etc.
- You wish to use certain vector databases that the Dify team cannot support.
- You wish to use unsupported hardware protocols.
- Other situations explicitly refused support by the Dify team.
2. Software Requirements
You need to be aware that Dify Enterprise has opened up a powerful third-party software integration ecosystem. Once the transaction is completed, you will receive a Dify Enterprise user manual that will indicate methods for integrating third-party software, please refer to it. However, this does not mean that Dify will help you deploy third-party software, nor does it mean that Dify will be responsible for the consequences of your use of such software. Please evaluate the usage methods, risks, and personnel configuration of third-party software on your own before use.2.1 Software Configuration
Typically, you need to install and initialize the following environments:- Docker
- Kubernetes (K8S)
- Minikube
2.2 Personnel Configuration
Please ensure your company always has its own operations engineers, or obtains assistance through Dify Deep Technical Support Services to help advance the entire Dify deployment process. If you lack such support, or if you have a development team but lack operations experience, it may lead to difficulties in deploying Dify Enterprise. You need to clearly state your technical capacity reserves or deployment plan during business communications so that we can match the best technical solution for you. Dify Enterprise is software aimed at large-scale applications, and technical capacity is particularly important during the deployment process.2.3 Updates and Maintenance
After contract signing, you will obtain the update method in the enterprise version deployment manual. You can choose not to update Dify Enterprise, but your access key will only be effective during the contract-specified time. If software issues arise, please contact our delivery team for assistance. For software issues, we will provide maintenance services. The regular issue response cycle is 24 hours; for fatal issues affecting software production capability, we will assist you in resolving them as soon as possible. The above assistance refers to non-intrusive technical support, meaning only maintaining the normal operation of the software itself, not including software usage training, nor providing customized development or deployment services.3. Deployment
3.1 Deployment Notes
Dify Enterprise is a software system. When purchasing the software alone, we will provide you with 24 hours total over one year of standard technical support services. Purchasing this software does not mean you have purchased Dify’s deployment services. Therefore, after reading this document, please appropriately evaluate your existing technical capacity and contact sales personnel to evaluate the technical difficulty and your actual needs, so we can provide you with the most suitable deployment solution.3.2 Standard Deployment Service Scope
Generally, you will receive the following after contract signing and payment settlement:- Dify Enterprise account and password—Used to generate tokens for accessing Dify Enterprise images.
- Dify Enterprise deployment manual—Please deploy according to the manual requirements.
- Helping you confirm whether hardware meets standard deployment service requirements.
- Interpretation and guidance of the deployment manual.
- Assisting you in contacting reliable cloud service providers.
- Providing limited technical consultation related to the deployment manual.
3.3 Deep Technical Support Services
If your needs fall into one of the categories in 1.3 Exceptions, or you believe your team cannot mobilize sufficient operations capacity for deployment, or need more information to train your team, please contact sales personnel to evaluate your needs. Dify provides corresponding Deep Technical Support Services to ensure you can deploy and use the purchased software economically, efficiently, and easily. These services typically include:- Deep software integration customization services.
- Deep deployment process intervention services.
- Deep information consulting services.