langgenius/dify

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.