1Panel-dev/1Panel

Choose this fork only if the Portuguese-facing packaging and custom install flow are the goal. If you want current 1Panel capabilities, active maintenance, or upstream security fixes, the upstream project is the better default.

Choose this fork if you want a Chinese-localized, heavily customized 1Panel variant and are comfortable carrying divergence. Choose upstream if you want the newest security fixes, active feature delivery, and lower maintenance risk.

Choose the fork only if its customizations are specifically useful to you and you are prepared to own maintenance. If you want the latest 1Panel features, fixes, and security updates, upstream is the safer choice.

Choose this fork only if you need its specific custom workflows and are prepared to own a stale, highly divergent codebase; otherwise upstream is the safer default.

Choose this fork only if its added provider support or local customizations are essential. If you want current 1Panel features, security fixes, and active maintenance, upstream is the safer choice.

Choose this fork only if you specifically need its localized, forked distribution and are willing to accept major upstream lag. For most adopters, upstream 1Panel is the safer default because this fork is stale and materially diverged.

Choose this fork only if its added ops shortcuts match your workflow and you accept being materially behind upstream. For most adopters who want current security fixes, new OpenClaw/agent features, and active maintenance, upstream 1Panel is the safer choice.

Choose this fork only if you specifically want its localized, customized snapshot. For most adopters, upstream 1Panel is the safer choice because it is much more active and likely has newer fixes and features.