PocketWorkers separates the web deployment from the network relay.
The web app runs on Vercel. Supabase stores identity, accounts, gateway records, and lease metadata. FRPS runs on an independent cloud server. Beside it, a small FRP worker manages allocation and lifecycle.
Why not run FRP in Vercel?
FRP is long-running infrastructure. It needs stable ports, process supervision, and direct control over relay behavior. That does not belong in a serverless web deployment.
What the worker does
The worker is responsible for:
- Choosing an available public port.
- Writing the lease to Supabase.
- Coordinating with gateway registration.
- Making the endpoint discoverable to authorized clients.
- Releasing or rotating stale mappings.
The planned implementation uses Sogou Workflow in C++ so the relay-side worker can stay small, fast, and close to the FRP server.
What the web app does
The web app stays boring in the best way: sign in, choose a team, see gateways, create pairing tokens, and let clients discover the selected route.