FRP Manager (frpmgr) is a user-friendly desktop GUI client for FRP on Windows that lets users configure, launch, and monitor reverse proxies without ever writing a configuration file.

What it is

FRP Manager is a multi-node, graphical reverse proxy tool built on top of FRP, written in Go and licensed under Apache-2.0. It is aimed squarely at Windows users — the latest release requires at least Windows 10 or Server 2016 — and it covers a complete workflow: a configuration editor, a launcher, status tracking, and hot reload. Documentation lives in the project Wiki, which carries installation instructions, a Quick Start guide, a Configuration reference covering proxy, visitor, and log settings, and a set of worked examples.

The concrete problem it solves is a common one described by the authors: exposing a local server that sits behind a NAT or firewall to the Internet normally means juggling several separate pieces at once — the FRP client binary, a hand-written configuration file, and some kind of launcher — in order to keep a stable service running. FRP Manager collapses that into an all-in-one application and eliminates the tedious manual operations that come with deploying a reverse proxy that way.

Key capabilities

• Configurations launched from the application run independently as background services, so the GUI can be closed after setup while the proxies keep working.
• A launched configuration is registered as an auto-start service by default and comes up during system boot, without requiring anyone to log in.
• Hot reload applies proxy changes to a running configuration without restarting the service and without losing proxy state.
• Multiple configurations make it possible to connect to several nodes at once, with each node kept as its own configuration.
• Configurations can be imported from a local file, from the clipboard, or over HTTP, and exported again for reuse.
• A self-destructing configuration disappears and becomes unreachable after a set amount of time.
• Proxy status is shown directly in a table view, so there is no need to read logs to see what is running.

Who uses it and how

• Windows users who need to expose a local server behind NAT or a firewall to the Internet, replacing the usual client-plus-config-plus-launcher arrangement with a single application.
• Operators managing connections to multiple nodes, who keep one configuration per node and track each proxy's state from the status table rather than from log output.
• People who want a proxy service that survives reboots unattended, since launched configurations register as auto-start services that start at boot without a login.
• Users working with short-lived or shareable access, who rely on the self-destructing configuration type to make a configuration unreachable after a given period.
• Contributors building the project from source, who need Go, Node v22, the Windows SDK, MinGW, and the WiX Toolset v3.14, set WindowsSdkVerBinPath, and run build.bat to produce installation files in the bin directory.

Getting started

Install the application from the releases page following the Wiki's Installation Instructions, or build it from source with git clone, cd frpmgr, and build.bat — passing build.bat -p skips the installer and produces a portable application instead.

How it compares

FRP Manager sits on top of FRP itself rather than next to an alternative: it is the graphical front end for the same frpc client, so it competes with nothing so much as the manual workflow of editing a config file and launching the FRP binary by hand. In this registry it stands alongside the underlying FRP project as the tool you reach for when that command-line workflow is the part you would rather not maintain.

When to use it — and when not

The trade-off is platform and scope: you are accepting a Windows-only GUI (Windows 10 or Server 2016 and above) that manages FRP clients, and you still need a reachable FRP node for the proxy to connect to. It is a poor fit for Linux servers, headless deployments with no desktop, or anyone who already drives frpc comfortably from configuration files and a shell. Building it yourself also carries a fairly heavy toolchain — Go, Node v22, the Windows SDK, MinGW, and WiX — and the README itself is thin, deferring most guidance to the Wiki, while the project carries 21 open issues.

git clone https://github.com/koho/frpmgr
cd frpmgr
build.bat

build.bat -p

go generate

go run ./cmd/frpmgr