What is FRP Auto Deploy?
FRP Auto Deploy is a lightweight deployment and operations layer for official FRP. It is built for small remote-access environments where a few systems to a few dozen systems need to be reached safely from outside private networks.FRP is the tunnel engine. FRP Auto Deploy is the installation, enrollment, identity, service, port, lifecycle, backup, diagnostics, and operator experience around it.
The problem it solves
Without a reverse-tunnel approach, remote support often becomes a chain of infrastructure requests: For temporary support, labs, partners, branches, and small infrastructure, that process can be much heavier than the actual technical task.The operating model
Install the public server once. Remote clients enroll and initiate outbound tunnels toward it. A client can publish its own services or act as a small gateway for services on other LAN hosts that it can reach.Who is it for?
System administrators
Reach remote Linux systems without building a full VPN or RMM stack.
Technical support engineers
Give customers or partners a controlled one-command onboarding path.
Lab / partner operators
Publish a few services from private networks through one controlled public entry point.
Small infrastructure teams
Manage a few to a few dozen systems with stable identities, ports, and a CLI.
What the product manages
What it intentionally does not manage
- cloud security groups
- external firewalls or NAT/DNAT rules
- UFW, firewalld, or iptables policy
- DNS provider records
- operating-system accounts, passwords, or SSH keys
- application authentication
- application TLS certificates
Supported service model
The stable core publishes TCP services:- SSH
- HTTP
- HTTPS passthrough
- Custom TCP
Recommended reading order
- Concepts & Mental Model — terminology and diagrams
- Quick Start — first working connection
- Publishing Services — SSH/web/custom/LAN examples
- frpctl Guide — everyday operation
- Architecture — expert internals