WireGuard vs. Runetale

WireGuard is operated as open source software. However, when it comes to operating it for businesses, it comes with various management costs. In addition, the WireGuard itself is not peer-to-peer by default, so it is necessary to have a WireGuardHub (a server that manages and periodically exchanges information about peers' public keys) just like in the traditional way.

Initial setup

Open-sourced WireGuard

1

Install WireGuard clients on both the source (Peer) and destination (Peer) to establish P2P connections.

2

Exchange necessary information such as Port, Private IP, and Private Key to establish a connection between both parties.

3

Repeat this process for as many peers as you want to operate. If you want to achieve a mesh network where all peers on the network you build are connected, the workload will double every time you add a new peer.

Runetale

1

Install the WireGuard client (Dotshake Mobile or Desktop app) on both the source (Peer) and destination (Peer) to establish P2P connections.

2

Runetale automates connectivity setups including key exchange. Instantly creates point-to-point connection.

Connectivity

Open-sourced WireGuard

In WireGuard, encryption is always guaranteed for traffic. However, in complex environments such as NATs or other situations, it may not be able to maintain a connection. It is because WireGuard is not intended to establish connections, but rather specializes in securing connection states.

You can improve connectivity with the keepalive option, but depending on the peer's device or environment, complex firewall settings and port forwarding might be required.

Runetale

No manual configuration is required. NAT traversal is automatically performed if necessary, maintaining connection stability.

Access Control

Open-sourced WireGuard

Manually creates and manages the configuration file by users.

Runetale

Automatically generates and updates the settings by Runtale.