Discofork
Repository brief

langgenius/dify

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T07:38:18.045Z
3mo ago

langgenius/dify

Dify is a very active, production-ready platform for building agentic workflows. The repo is large, well-documented, and heavily used, with 134,954 stars, 21,019 forks, and recent commits on March 30, 2026.

GitHub
Loading tags...
Stars134,954
Forks21,019
Default branchmain
Last pushed2026-03-30T07:32:39Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

5 of 5 fork briefs
Selected

Choose this fork only if you want its specific Dify/OpenWebUI packaging and are willing to own the maintenance burden. If you want current upstream Dify features and fixes, upstream is the safer default.

Prefer this fork if your main goal is understanding Dify's source code. Prefer upstream if you want current features, active maintenance, and lower integration risk.

Choose this fork if OceanBase integration and enterprise runtime properties matter more than staying close to upstream Dify; choose upstream if you want the freshest general-purpose platform and the lowest upgrade risk.

Prefer this fork only if its specific 2024-era customizations are exactly what you need and you are prepared to maintain a large divergence yourself. For most adopters, upstream is the safer base because this fork is materially stale and far off the current maintenance stream.

Choose this fork if you want a customized Dify derivative for agent/worker experimentation and can absorb ongoing merge debt. Choose upstream if you want the safest path for production stability, current fixes, and lower maintenance overhead.