Dify
Dify is an open-source large language model (LLM) application development platform.
Platform availability
Available on 3 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS
- Proxmox (not listed)
- Helm
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server
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.
80/100 Excellent
- Maintained
- 100last commit 13 days ago
- Popular
- 100160,677 GitHub stars
- Easy to install
- 553 install platforms, install notes, Docker image
- Light to run
- 304 GB minimum RAM
Availability: platform listings confirmed today
- GitHub stars
- 160,677
- Open issues
- 1209
- Last commit
- 2026-11-08
- Latest release
- 1.19.0
- Activity
- steady
Checked 13 days ago - source: GitHub (langgenius/dify)
Resources & Compatibility
Minimum requirements: 4 GB RAM, 2 CPU core(s), 50 GB disk. ARM (e.g. Raspberry Pi) is not supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Add the agent backend secret key Generate a random secret with the Python command and put it into DIFY_AGENT_SERVER_SECRET_KEY, the secret key the agent backend needs. If the value is malformed, the agent service will refuse to start. source
- Point the web UI at the API In the web app folder, copy the sample env file to .env.local and set NEXT_PUBLIC_API_PREFIX and NEXT_PUBLIC_PUBLIC_API_PREFIX to the base addresses for your Dify console and public web app. If they point to the wrong host or port, the browser cannot reach Dify's backend, so login and app pages will fail. source
- Keep port 3000 free for the web UI Dify's web UI is expected to start at http://localhost:3000, so make sure port 3000 is free and reachable from where you will open the browser. If it is blocked or already used, you will not be able to load the UI. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives (10)
- Claude Code - Claude Code is a self-hosted Docker container that keeps an always-on Claude Code session on your homelab, so the agent stays reachable fro…
- Codex - Codex is a web-based comic archive browser and reader for organizing, importing, and reading personal CBZ, CBR, CB7, CBT, and PDF comic lib…
- Cursor - The AI-first Code Editor.
- Emdash - EmDash is a full-stack TypeScript CMS based on Astro; the spiritual successor to WordPress
- GitHub Copilot - GitHub Copilot leverages the power of OpenAI Codex to provide real-time suggestions for code and complete functions, all within your editor.
- Google Opal - Build, edit and share mini-AI apps using natural language.
- Jules - Jules is an asynchronous agent that gets out of your way.
- Pi Agent
- Xiaomi MiMo Code
- opencode - OpenCode is an open-source AI (artificial intelligence) coding agent for terminal, editor, and desktop environments that helps developers w…
Checked 39 days ago - source: AlternativeTo
Common questions
Why does the Docker Compose deploy script fail with “Remote branch null not found in upstream origin”?
The script resolves the latest Dify version through the GitHub API before cloning. If that request fails, often because of GitHub’s rate limit on unauthenticated requests, jq outputs null and git reports the missing null branch.
What Dify environment variable must be valid for the agent service to start?
DIFY_AGENT_SERVER_SECRET_KEY must contain a randomly generated secret. If the value is malformed, the agent service refuses to start.
Which web UI environment variables need to match the backend address in a source-code deployment?
Set NEXT_PUBLIC_API_PREFIX and NEXT_PUBLIC_PUBLIC_API_PREFIX to the base addresses for the Dify console and public web app. If they point to the wrong host or port, the browser cannot reach Dify’s backend, so login and app pages will fail.
How should I reset a Dify account password when running from source code?
For source-code deployments, run the same command from the api directory. Enter the account email and new password when prompted.
Answers sourced from docs.dify.ai, docs.dify.ai, docs.dify.ai, docs.dify.ai
Community
Collected 48 days ago - public community threads