Take a Private Route Online.Connect Your Devices Through One VPN.

Our WireGuard hosting gives your devices a VPN endpoint to connect to. Once a device is configured, traffic sent through its tunnel is encrypted between that device and the endpoint.

You choose which destinations use that route. It can serve a remote-work setup or provide a consistent path for everyday traffic, depending on the network configuration. Compare the current features and billing terms in our hosting plans.

Start with simultaneous use, rather than the total number of devices you own. A few people opening an internal dashboard have different needs from a team transferring large files all day.

• Estimate how many devices will be connected at busy times.
• Compare the published traffic allowances and plan features.
• Test the tasks you expect to run through the tunnel.

Use our current plan listing for any device limits or included management options.

This environment is prepared for WireGuard VPN connections. If you need to install and manage a separate mix of websites, databases or other server software, choose our VPS hosting.

1. Install the appropriate client from the official downloads.
2. Import the configuration prepared for that device.
3. Activate the tunnel and test a destination that should use it.

Keep the configuration private: it contains the device’s private key. Your client setup should match the endpoint, routes and DNS settings for your intended connection.

Give each device its own peer configuration. That lets you remove one lost phone or retired laptop without replacing the whole team’s access.

Name peers so you can identify their owner and device. Keep private keys out of shared documents, and remove configurations when the associated device no longer needs access.

• Split tunnel: only selected destinations use the VPN. Other traffic follows the device’s usual connection.
• Full tunnel: general traffic uses the VPN endpoint as its exit route.

For example, split tunnelling can send work-app traffic through the VPN while leaving ordinary browsing on your local connection. The client routes and endpoint forwarding must match your choice. See the setup guide for configuration basics.

Yes, when the VPN endpoint has a working route to that application and the network permits access. Creating a VPN account alone does not connect an office network.

Before rollout, check three things:

• The destination address is included in the intended VPN route.
• The office network can return traffic to the VPN device.
• Firewalls allow the specific application connection.

Then test with one device before adding the rest of the team.

WireGuard supports IP address roaming, so a peer can retain its identity when its external address changes. The client and operating system still affect how the switch feels in practice.

Try the Wi-Fi-to-mobile handover with an application you use regularly. Also check what happens when the phone sleeps and wakes, particularly if you need to receive traffic after an idle period.

No. It protects the device-to-endpoint link for traffic routed through the tunnel. Websites can still recognise signed-in accounts, cookies and other identifiers.

Continue using HTTPS and normal account protections. A no-logs commitment is a provider policy, not a feature guaranteed by the WireGuard protocol; refer to the applicable service privacy terms.

Match name resolution to the route you want. A private work-app name may require your organisation’s resolver, while general browsing may use a different DNS setup.

• Make sure the chosen resolver is reachable.
• Check which resolver the client actually uses when connected.
• Test both private names and ordinary websites.

Verify this on each type of device. Turning on the tunnel alone does not confirm that every DNS query follows the intended path.

1. Remove the old device’s peer from the endpoint configuration.
2. Confirm that the change is applied and its access is revoked.
3. Create a new key pair and configuration for the replacement.

If the device was lost, also secure the accounts and data it could access. Revoking a VPN peer closes that route; it does not sign the device out of other services.

A recent handshake confirms that the peers can communicate securely. It does not prove that the application route is working.

1. Check the destination address and the routes assigned to the peer.
2. Compare access by IP address and hostname, where the application supports both, to help isolate a DNS issue.
3. Check forwarding, the return route and firewall rules.
4. Confirm that the application itself is listening and available.

When requesting help, include the failing destination and any error message. Remove private keys before sharing configuration details.