Expired70% confidenceFactExact time
Dify's full service stack includes a frontend Web service, a backend API service, a Celery-based Worker asynchronous task queue, PostgreSQL, Redis, a Weaviate vector database, and an Nginx reverse proxy.
4
Sources
70%
Confidence
Medium-term (~90 days)
Relevance
7/9/2026
First Seen
Valid until: 10/7/2026(expired)
Sources
Related Claims
VerifiedThe full service stack for a Dify private deployment includes the API service, Worker, Web frontend, PostgreSQL database, Redis cache, and a vector database.83% similarUnverifiedRunning Dify depends on multiple microservices: Nginx reverse proxy, API service, Worker service, PostgreSQL, Redis, and a Weaviate or Qdrant vector database.80% 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.79% 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.79% similarVerifiedDify is deployed using Docker Compose, encapsulating multiple services — including the web frontend, API backend, PostgreSQL, Redis, Weaviate, and others — as separate containers.71% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/395407API
curl https://kongchang.com/api/v1/knowledge/claims/395407MCP
get_claim(id=395407)