Expired80% confidenceFactTime unknown
Dify is deployed using Docker Compose, encapsulating multiple services — including the web frontend, API backend, PostgreSQL, Redis, Weaviate, and others — as separate containers.
7
Sources
80%
Confidence
Medium-term (~90 days)
Relevance
7/2/2026
First Seen
This claim has expired. It is kept for the record and no longer describes the current state.
Valid until: 9/30/2026(expired)
Sources
Related Claims
UnverifiedDify supports deploying the application stack locally via Docker Compose, with built-in PostgreSQL vector database (pgvector extension), Redis cache, and Nginx reverse proxy.82% similarUnverifiedA full Dify deployment typically involves 7–10 independent containers, including Nginx, a Next.js frontend, a Flask API service, Celery, PostgreSQL, Redis, and a vector database.78% similarUnverifiedThe full operation of Dify depends on at least six independent services working together, including the API service, web frontend, database, vector store, Redis, and others.77% similarUnverifiedA locally deployed Dify container can directly access services such as MySQL and Redis on the host machine without requiring additional intranet tunneling.76% similarVerifiedThe full service stack for a Dify private deployment includes the API service, Worker, Web frontend, PostgreSQL database, Redis cache, and a vector database.74% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/54186API
curl https://kongchang.com/api/v1/knowledge/claims/54186MCP
get_claim(id=54186)