Discofork
Repository brief

NginxProxyManager/nginx-proxy-manager

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-30T19:49:26.779Z
1mo ago

NginxProxyManager/nginx-proxy-manager

Nginx Proxy Manager is a Docker-based reverse-proxy management project with a simple web UI for forwarding hosts, redirections, streams, SSL termination, and basic access controls. It is actively maintained, widely used, and has a large fork/stargazer base, which makes it a credible upstream if you care about an opinionated, self-hosted proxy manager with ongoing changes.

GitHub
Loading tags...
Stars32,306
Forks3,682
Default branchdevelop
Last pushed2026-03-29T19:51:46Z
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

10 of 10 fork briefs
Selected

Choose this fork if you want a more feature-rich and security-oriented Nginx Proxy Manager with active fork-specific development. Stick with upstream if you value maximum compatibility, simpler migrations, and fewer surprises in env vars and UI workflows.

Choose this fork if Chinese-language usability is the main blocker. Choose upstream if you want the latest features, fixes, and fastest maintenance cadence.

Choose this fork if integrated open-appsec management is the goal; choose upstream if you want the broadest compatibility, latest Nginx Proxy Manager fixes, and the simplest path to ongoing updates.

Adopt this fork only if you specifically need its historical state. For most users, upstream is the better choice because this fork is far behind and does not show added capabilities.

Choose upstream unless you specifically want a frozen copy from January 2026; this fork adds nothing new and is materially behind.

Choose upstream unless you specifically need this fork’s build/CI snapshot. This fork does not look like a feature-rich alternative; it is a stale maintenance fork with limited divergence and significant upstream lag.

Choose this fork only if you specifically need its old Docker experimentation or existing behavior. For most adopters, upstream is the safer default because this fork is stale and substantially behind.

Prefer upstream unless you specifically need this exact historical snapshot. For adopters, this fork offers no added capability and substantial maintenance risk.

Prefer upstream unless you have a hard requirement to stay on this exact old snapshot. This fork offers no added functionality and is materially stale, so it is a poor default choice for new adopters.

Choose this fork only if you want a very close upstream mirror; otherwise, upstream itself is the better default because this fork adds nothing and is already slightly behind.