1Add one
A gateway belongs to one private network, so make the network first. In the console, open Gateways from the Overview (or from Private networks), choose Add a gateway and pick the network. It's ready in a few minutes.
A gateway belongs to one private network, so make the network first. In the console, open Gateways from the Overview (or from Private networks), choose Add a gateway and pick the network. It's ready in a few minutes.
Install the free WireGuard app on the laptop or phone. On the gateway, choose Add a device and give it a name. You get a config file: download it and import it in the app.
The file holds the device's private key. We show it once and don't keep a copy, so save it. If it's lost, remove the device and add it again. If you'd rather make the key on the device, open I have my own WireGuard key and paste its public key.
Any router that runs WireGuard can connect a whole office. Choose Add an office, give it a name and the address range the router hands out, for example 192.168.1.0/24. Put the config file on the router and send your private network's range through the tunnel. Everyone in the office then reaches your servers.
Each office needs its own range, and none of them can overlap the private network.
Your servers on that private network, at their private addresses, and nothing else: not the internet, and not your other devices or offices. Your servers see the traffic coming from the gateway's own private address, so nothing needs to change on them.
The gateway's page shows which devices and offices are connected right now.
By default your servers only answer. To let them start connections to your offices and connected devices too, for example a backup job that copies to an office NAS, choose Let them next to Your servers on the gateway.
Each server needs routes for that. We add them on the servers we set up for you. For a server you set up by hand, run the steps on its Networking tab again. After you add or change an office, choose Update my servers.
A server that only talks to your other servers, such as a database, doesn't need its own public IPv4 address. When you order it, tick No public IPv4: online through a gateway and pick a private network that has a gateway. The price is the same.
The server gets an IPv6 address and an address on the private network. It reaches the IPv4 internet, for updates and the like, through the gateway's address. Nobody on the internet can reach it over IPv4, and you reach it from your devices and offices through the gateway.
One-click apps, free HTTPS certificates, extra IPv4 addresses and load balancers need a public IPv4, so they aren't available on these servers. Outgoing mail on port 25 is blocked, as on every server.
A gateway can connect up to four more of your private networks at the same location to its own, free. Choose Connect a network on the gateway: servers on its network and on the one you pick can then reach each other. The ranges can't overlap, and the other network can't have a gateway of its own.
We add the routes on the servers we set up for you. For a server you set up by hand, run the steps on its Networking tab again.
Turn off stops a device or office from connecting until you turn it on again. Remove deletes it for good. File shows its config again, without the private key.
Everything here is also in the API (/gateways), the eh gateways command and the AI assistant tools.