Dify is a self-hosted platform for building and operating applications that use language models. Its Docker Compose quick start documents minimum host sizing of 2 CPU cores and 4 GiB RAM, with Docker and Compose prerequisites on Linux. The standard Compose setup starts a multi-container stack, including PostgreSQL, Redis, Weaviate, and sandbox services; model inference capacity depends on the separately selected model provider or inference runtime.
The official Linux Docker Compose path lists a minimum of 2 CPU cores and 4 GiB RAM for the host. This is a documented minimum, not a production sizing guarantee.
Linux deployment requires Docker 19.03+ and Docker Compose 2.24.0+. The macOS Docker Desktop instructions call for a Docker VM with at least 2 vCPUs and 8 GiB memory.
Recommended
Documented guidance
No further general recommendations are published for this version.
Published starting requirements
The minimum comes from the official quick start. The Compose stack runs multiple application and supporting containers; production capacity depends on usage, enabled components, retained files and whether inference is local or remote. Dify itself does not establish that a host can run a chosen model.
We only compare what providers publish. A RAM figure alone can't confirm compatibility or production capacity.
Deploy with
Supported paths
Docker Compose on Linux
Docker Compose through Docker Desktop on macOS or Windows with WSL 2
The host must provide
Runtime
Container runtime
Docker 19.03+ for Linux, with Docker Compose 2.24.0+
Supporting services
The official Compose stack includes PostgreSQL, Redis, Weaviate, sandbox, proxy, worker and Dify application containers
Model endpoint
Choose a model provider or separately operated inference backend; sizing for that backend is outside the Dify host minimum
Storage
Persistent data
The Compose deployment uses persistent volumes for databases and application data. The official quick start does not state a universal disk minimum. Plan storage from retained uploads, knowledge-base documents, database growth, logs and backups; do not treat the 4 GiB RAM minimum as a disk recommendation.
Step by step
Plan a Dify self-hosted deployment
Check the baseline host
For the documented Linux Compose path, confirm at least 2 CPU cores and 4 GiB RAM, then install Docker and Compose at the documented versions. Treat this as a minimum starting point only.
The quick start starts multiple core and supporting containers. Review the supplied environment configuration and decide which storage, database, and service settings your deployment needs.
Connect Dify to a model endpoint and size that endpoint independently. The minimum Dify host requirements do not prove that local inference will fit or perform well.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
The official Linux Docker Compose path lists a minimum of 2 CPU cores and 4 GiB RAM for the host. This is a documented minimum, not a production sizing guarantee.This prerequisite has no comparable published plan field.
Linux deployment requires Docker 19.03+ and Docker Compose 2.24.0+. The macOS Docker Desktop instructions call for a Docker VM with at least 2 vCPUs and 8 GiB memory.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
The official Linux Docker Compose path lists a minimum of 2 CPU cores and 4 GiB RAM for the host. This is a documented minimum, not a production sizing guarantee.This prerequisite has no comparable published plan field.
Linux deployment requires Docker 19.03+ and Docker Compose 2.24.0+. The macOS Docker Desktop instructions call for a Docker VM with at least 2 vCPUs and 8 GiB memory.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
The official Linux Docker Compose path lists a minimum of 2 CPU cores and 4 GiB RAM for the host. This is a documented minimum, not a production sizing guarantee.This prerequisite has no comparable published plan field.
Linux deployment requires Docker 19.03+ and Docker Compose 2.24.0+. The macOS Docker Desktop instructions call for a Docker VM with at least 2 vCPUs and 8 GiB memory.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
The official Linux Docker Compose path lists a minimum of 2 CPU cores and 4 GiB RAM for the host. This is a documented minimum, not a production sizing guarantee.This prerequisite has no comparable published plan field.
Linux deployment requires Docker 19.03+ and Docker Compose 2.24.0+. The macOS Docker Desktop instructions call for a Docker VM with at least 2 vCPUs and 8 GiB memory.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
The official Linux Docker Compose path lists a minimum of 2 CPU cores and 4 GiB RAM for the host. This is a documented minimum, not a production sizing guarantee.This prerequisite has no comparable published plan field.
Linux deployment requires Docker 19.03+ and Docker Compose 2.24.0+. The macOS Docker Desktop instructions call for a Docker VM with at least 2 vCPUs and 8 GiB memory.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
The official Linux Docker Compose path lists a minimum of 2 CPU cores and 4 GiB RAM for the host. This is a documented minimum, not a production sizing guarantee.This prerequisite has no comparable published plan field.
Linux deployment requires Docker 19.03+ and Docker Compose 2.24.0+. The macOS Docker Desktop instructions call for a Docker VM with at least 2 vCPUs and 8 GiB memory.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
The official Linux Docker Compose path lists a minimum of 2 CPU cores and 4 GiB RAM for the host. This is a documented minimum, not a production sizing guarantee.This prerequisite has no comparable published plan field.
Linux deployment requires Docker 19.03+ and Docker Compose 2.24.0+. The macOS Docker Desktop instructions call for a Docker VM with at least 2 vCPUs and 8 GiB memory.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
The official Linux Docker Compose path lists a minimum of 2 CPU cores and 4 GiB RAM for the host. This is a documented minimum, not a production sizing guarantee.This prerequisite has no comparable published plan field.
Linux deployment requires Docker 19.03+ and Docker Compose 2.24.0+. The macOS Docker Desktop instructions call for a Docker VM with at least 2 vCPUs and 8 GiB memory.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
The official Linux Docker Compose path lists a minimum of 2 CPU cores and 4 GiB RAM for the host. This is a documented minimum, not a production sizing guarantee.This prerequisite has no comparable published plan field.
Linux deployment requires Docker 19.03+ and Docker Compose 2.24.0+. The macOS Docker Desktop instructions call for a Docker VM with at least 2 vCPUs and 8 GiB memory.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
The official Linux Docker Compose path lists a minimum of 2 CPU cores and 4 GiB RAM for the host. This is a documented minimum, not a production sizing guarantee.This prerequisite has no comparable published plan field.
Linux deployment requires Docker 19.03+ and Docker Compose 2.24.0+. The macOS Docker Desktop instructions call for a Docker VM with at least 2 vCPUs and 8 GiB memory.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
The official Linux Docker Compose path lists a minimum of 2 CPU cores and 4 GiB RAM for the host. This is a documented minimum, not a production sizing guarantee.This prerequisite has no comparable published plan field.
Linux deployment requires Docker 19.03+ and Docker Compose 2.24.0+. The macOS Docker Desktop instructions call for a Docker VM with at least 2 vCPUs and 8 GiB memory.This prerequisite has no comparable published plan field.
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
The official Linux Docker Compose path lists a minimum of 2 CPU cores and 4 GiB RAM for the host. This is a documented minimum, not a production sizing guarantee.This prerequisite has no comparable published plan field.
Linux deployment requires Docker 19.03+ and Docker Compose 2.24.0+. The macOS Docker Desktop instructions call for a Docker VM with at least 2 vCPUs and 8 GiB memory.This prerequisite has no comparable published plan field.
