MHSanaei/3x-ui

Choose this fork if older-system support and Chinese-oriented customization matter more than staying close to upstream. Choose upstream if you want the latest fixes, smoother upgrades, and lower maintenance risk.

Prefer upstream unless you specifically need this fork’s older snapshot or branding; this fork shows no added capability and is materially behind on maintenance.

Choose this fork if you want extra automation and workflow-specific changes, especially Telegram-driven client delivery and custom install/update behavior. Choose upstream if you want broader protocol coverage, lower maintenance risk, and easier compatibility with future releases.

Choose this fork if you want the Telegram and subscription workflow changes and can accept being far behind upstream. Avoid it if you need current fixes, minimal drift, or a drop-in replacement for the latest 3x-ui behavior.

Choose this fork if your main need is easier domestic installation and localized guidance; stay with upstream if you want the broadest community support and the least-maintenance path.

Choose this fork only if you specifically need the Happ deep-link behavior fix; otherwise upstream is the safer choice because it is much more current.

Prefer this fork if you need the RoscomVPN-specific routing and deployment customization. Prefer upstream if you want fresher fixes, broader language support, and the default 3x-ui behavior with less maintenance risk.

Prefer this fork if you need its targeted protocol and LDAP-oriented customizations and you are comfortable managing divergence from upstream; prefer upstream if you want the broader feature set, fresher maintenance, and lower upgrade risk.

Choose this fork if Telegram-driven client management and setup conveniences matter more than keeping full upstream parity. If you want the widest protocol coverage and the latest fixes, upstream is the safer choice.