Network
Where the gateways are, and how one is chosen.
Five cities on three continents, described exactly. Not “thousands of servers in a hundred countries” — a list, and how the app picks between them.
Locations
| Location | Country | Plan |
|---|---|---|
| New Jersey | United States | Standard |
| Silicon Valley | United States | Standard |
| London | United Kingdom | Standard |
| Frankfurt | Germany | Standard |
| Singapore | Singapore | Standard |
The app shows the live list with a load meter beside each entry, fetched when you sign in. A location that is full, draining, or has not reported in 90 seconds is left out, so what you see is what will accept you.
How a gateway is chosen
The directory is the load balancer.
There is no box in front of the gateways. The app asks the directory, gets a list sorted by load, and connects to the gateway directly. Nothing in the middle can see or slow your packets.
Load is sessions over capacity.
Each gateway reports how many sessions it is carrying every 30 seconds. The app shows that as low, busy or heavy; “Fastest available” picks the lowest.
Draining is graceful.
A gateway being taken down stops accepting new sessions and keeps carrying the existing ones until they end. You do not get cut off for maintenance.
Every gateway is ours to run.
Each one runs our software and nothing else, generates its own keys on first start, and keeps the same no-field-for-it counters as every other. There is no third-party VPN backend behind the list.
A network that grows carefully
Because a location that is listed has to be real: a server we run, with the same isolation and the same no-field-for-it counters as every other. Adding a city well is a commitment to keep it patched, reachable and honest. The list grows when we can make that commitment, and not before.
If there is a place you need and do not see, say so. It is the most useful thing you can tell us.
About the table above