Repository brief

fatedier/frp

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:39:28.532Z

fatedier/frp

frp is a large, actively maintained Go project for exposing local services behind NAT or firewalls to the internet. It is mature and widely used, with very high adoption signals: 105,680 stars and 14,969 forks, and it was updated on 2026-03-30. Forks are most interesting if you want a production-grade reverse proxy with ongoing upstream activity and a broad feature set rather than a small niche utility.

GitHub

Stars105,680

Forks14,969

Default branchdev

Last pushed2026-03-29T19:22:35Z

Best maintainedHaidyCao/frp

Closest to upstreamHaidyCao/frp

Most feature-richZeroDream-CN/SakuraFrp

Most opinionatedZeroDream-CN/SakuraFrp

Forks

Choose a fork to inspect

4 cached fork briefs

Fork comparison

ZeroDream-CN/SakuraFrp

stale

significant_divergence

Choose this fork if you need a productized FRP deployment with multi-user and quota controls. Avoid it if you want upstream freshness, broad community support, or minimal maintenance burden.

Likely purpose

Provide a hosted or commercial FRP variant with multi-user management, bandwidth/traffic limits, and operational controls that make it easier to run as a service.

Best for

Operators running FRP as a paid or managed service; Teams that need per-user quotas or bandwidth control; Users who want FRP but need a custom API/control layer; Adopters willing to trade upstream freshness for service-specific features

Additional features

Multi-user management workflows
Traffic and bandwidth limiting via `extend/limit`
Cumulative usage/accounting via `extend/cumu`
Custom API surface in `extend/api`
Customized HTTPS/vhost handling and server control behavior
Commercial hosting-oriented packaging and documentation

Missing features

It is 705 commits behind upstream, so it likely lacks many recent upstream fixes and improvements
Recent upstream work such as dashboard redesign, dependency/security updates, and test/CI maintenance are not reflected here
Upstream parity is weaker, so adopters may need to maintain their own compatibility and update work
It trails upstream by 705 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Clear fit for hosted FRP services
Adds operational controls that upstream does not emphasize
Smaller fork footprint than a full rewrite, so core FRP behavior is still recognizable

Risks

Large upstream lag increases security and compatibility risk
Custom extension surface may diverge from upstream config and APIs
Stale activity suggests uncertain long-term maintenance