AlphaVPN per AlphaXP 404

AlphaVPN routes your browser traffic through your AlphaVPN account — nothing else on the machine is touched. There is no system service to install, no driver, and no configuration file: sign in, choose a location, and flip the switch in the toolbar.

How it works

Firefox lets an extension make a routing decision per request. AlphaVPN uses that directly rather than a PAC script, so the extension can be precise about what it does and does not proxy. Requests to the AlphaVPN API itself always go direct — otherwise the call that disconnects you would need the connection it is tearing down.

When you connect, the server issues a short-lived proxy credential. It is handed straight to Firefox's proxy layer and is never shown, copied to the clipboard, or written anywhere a page can reach. When you disconnect, it is returned to the server and deleted, so a credential that leaked cannot outlive the session.

What it shows

• Live throughput, sampled from the server's own byte counters
• Your plan, the data you have used against it, and how long you have been connected
• The exit location, chosen from the servers your account can reach

What you need

An AlphaVPN account. The free plan covers one device and 5 GB a month, which is enough to try it properly; paid plans add devices and data. You can create an account from inside the extension.

Permissions, and why

• proxy — the whole point: route requests through the exit server
• webRequest, webRequestBlocking — supply the proxy credential when Firefox asks for it
• storage — keep your session token and the current proxy credential locally
• <all_urls> — a proxy decision has to be made for every request; the extension inspects only the hostname, and only to decide direct-or-proxy

AlphaVPN contains no analytics, no third-party scripts, and no remote code. It talks to one host: the AlphaVPN API.