FRP cloud relay
Where FRPS runs and how PocketWorkers stores public endpoint leases.
FRPS is planned to run on an independent cloud server, separate from the Vercel web deployment.
Responsibilities
The FRP side owns long-running relay behavior:
- public port availability
- relay process lifecycle
- route allocation
- stale route cleanup
- network-level access diagnostics
Worker implementation
The PocketWorkers FRP worker is planned in C++ using Sogou Workflow. It lives close to the FRP server and communicates with Supabase to persist lease metadata.
Web app boundary
The web app does not run FRPS. It shows gateway records, creates pairing flows, and gives authenticated clients the endpoint data they are allowed to use.