# Install frps with Homebrew Server app of fast reverse proxy to expose a local server to the internet. Version 0.70.1 via Homebrew; verified 2026-07-26. ## Install ```sh sudo av install brew:frps ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install frps ``` Evidence: local Homebrew formula metadata ## Package facts - **Package key:** brew:frps - **Package manager:** Homebrew - **Version:** 0.70.1 - **Source summary:** Server app of fast reverse proxy to expose a local server to the internet - **Homepage:** - **Repository:** - **Last updated:** 2026-07-26T11:37:58+02:00 - **Generated:** 2026-08-03T19:37:03+00:00 ## Executables - frps (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 0.70.1 ## Project history and usage frps is the server-side command in frp, the fast reverse proxy project. It runs on a host with a reachable address and accepts frpc client connections so private services can be exposed through TCP, UDP, HTTP, HTTPS, and related proxy modes. ### Project history frp was created on GitHub in 2015 and developed as a paired client/server tunneling system. The upstream README describes the architecture in terms of frps on a public server and frpc on a LAN host that cannot be directly reached from the Internet. The project has continued through frequent 0.x releases while the maintainers discuss a future v2 design. In the v0.69 line, the release notes formalized a compatibility policy and introduced a versioned wire protocol between frpc and frps. ### Adoption history frps is packaged separately because server operators often need only the public relay component. That packaging mirrors real deployments where frps may live on a VPS while many clients connect from private networks. frp's large GitHub audience and broad binary release matrix helped make frps a common choice in self-hosting, homelab, NAT traversal, and remote-access workflows. ### How it is used A common frps setup is to place the binary and server TOML configuration on a public host, configure a bind port, and then allow frpc clients to register proxies through it. Server-side features include dashboards, authentication, port controls, TCP multiplexing, protocol support, and management plugins. The server is the upgrade anchor in mixed-version deployments: the v0.69.0 release notes tell users to upgrade frps before frpc when moving through protocol changes. ### Why package nerds care frps matters to package history because it is a role-specific binary from a larger Go upstream. Separate packaging lets a server image or host install the relay daemon without implying that local client tunnel definitions should also be present. ### Timeline - 2015: The frp GitHub repository was created. - 2017: Public GitHub releases show established v0.x binary distribution. - 2026: v0.69.0 introduced the compatibility policy and versioned wire protocol. - 2026: v0.69.1 refined protocol behavior for UDP-family proxy payloads. ### Related projects - frpc is the client counterpart shipped by the same upstream frp project. - The upstream README relates future v2 work to cloud-native proxy and service-mesh ideas, including Envoy-like extensibility. ### Sources - - - - ## Security Notes broad file, network, media, or database tool signal. formula declares a Homebrew service. - **Geiger risk:** orange / medium - broad file, network, media, or database tool signal - formula declares a Homebrew service ## Combined YAML source View the package source record on GitHub. [combined/frps.yml](https://github.com/mxcl/pkgdb/blob/main/combined/frps.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated package history - pkgdb category and tag curation - cross-ecosystem install command graph