← Directory

Dify AIO

Dify is a self-hosted AI application platform for agentic workflows, RAG pipelines, tool integrations, and model-provider management.

  • AI
  • Development
  • Productivity
  • Tools & Utilities
Dify is a self-hosted AI application platform for agentic workflows, RAG pipelines, tool integrations, and model-provider management. The All-In-One Unraid Edition bundles the Dify API, workers, web UI, plugin daemon, code sandbox, SSRF proxy, Nginx, PostgreSQL with pgvector, and Redis into a single container for Unraid users who want the full Dify stack without managing separate services.

Platform availability

Available on 1 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

48/100 Fair

Maintained
77last commit 119 days ago
Popular
187 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
404 GB minimum RAM, runs on ARM

Availability: platform listings confirmed today, links checked 17 days ago

GitHub stars
7
Open issues
2
Last commit
2026-06-18
Latest release
1.14.2-aio.4
Activity
stale

Checked 8 days ago - source: GitHub (JSONbored/dify-aio)

Resources & Compatibility

Minimum requirements: 4 GB RAM, 2 CPU core(s). ARM (e.g. Raspberry Pi) is supported.

Checked 17 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Make a secret key before starting Use the Python command to create a random value for DIFY_AGENT_SERVER_SECRET_KEY, then save it in your environment settings. If it is missing or in the wrong format, the Dify agent part won't start. source
  • Set up the web app settings file Copy the sample .env file (a text file holding settings) to .env.local and set the API base URLs to where your Dify services run. This tells the Dify web UI where to find the backend, so pages, apps, and logins can load. source
  • Use these local ports After starting, expect the web UI on http://localhost:3000 and API prefixes pointing to http://localhost:5001. If those ports are blocked, you won't be able to open the app or reach its API from your machine. source
  • First-boot setup After installing the template, leave Web UI Port and AppData at their defaults unless you have a port conflict. Start the container and allow a few minutes for first boot — the wrapper initializes PostgreSQL, pgvector, Redis, generated secrets, local storage, the sandbox, plugin daemon, and Dify services. Then open the Web UI and create your first admin account. You can optionally set the Initial source

Fetched 13 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What should I do after installing the Dify AIO Unraid template?

Start the container and wait for first boot to finish initializing PostgreSQL, pgvector, Redis, generated secrets, storage, sandbox, and plugin services. Then open the Web UI on port 8080, go to install, create the admin account, and add model-provider keys and integrations.

How do I set the initial admin password for Dify AIO?

Set INIT_PASSWORD in the Unraid template, and Dify will use it as the initial admin password. That value is limited to 30 characters.

Can I use an external PostgreSQL or Redis with Dify AIO?

Yes. In Advanced View set DIFY_USE_INTERNAL_POSTGRES=false with external DB_* settings, or DIFY_USE_INTERNAL_REDIS=false with external REDIS_* settings, to move those services out of the container.

Can I use a vector store other than the bundled pgvector?

Yes. The template supports selecting external vector stores such as Qdrant, Weaviate, Milvus, Chroma, OpenSearch, Elasticsearch, and Upstash in Advanced View.

Where does Dify AIO store generated config and app data?

It uses a persistent /appdata volume, with first-boot secret generation under /appdata/config/generated.env. Unraid template values take precedence, and /appdata/config/extra.env is an escape hatch for rare upstream variables.

Answers sourced from github.com

Community

Collected 11 days ago - public community threads