Your own public IPv4. Everything over SSH.

That is the whole purchase. No account to create, no form, no dashboard to be shown around. The address is allocated and already answering before you pay for it, and the key you connected with is the account from then on.

Nobody ever sees a half-uploaded site. Each upload lands as a complete release and swaps in at once, so a connection that drops halfway changes nothing. The way back is one word.

The reverse DNS is yours to set. Forward-confirmed — what mail servers check, and what most hosts will not hand over. Certificates renew themselves.

1. 185.104.32.xyour address, on our network
2. one tunneloutbound, so no port to forward
3. your machineat home, behind CGNAT

The machine under your desk gets a public address. Every port of it, reachable from anywhere, straight through carrier NAT that no port forward can cross. That ip rule line is why it is an address and not a VPN: only traffic you bind to it leaves that way, so everything else on the machine carries on as before. That is also why the curl has an --interface. The address follows the tunnel: wg-quick down and we serve your files again, wg-quick up and it is yours, as often as you like.

Your agent gets a key of its own, never your password — there is none. help over the same connection is the whole API: no SDK, no token to rotate, nothing to scrape. keys rm and the agent is out. You are not.