Select a region, choose a server size, and click Deploy. TunnelFleet creates the Droplet, runs cloud-init, and reports back when your VPN server is ready. No terminal, no config files, no SSH.
Server name, cloud region, and server size. That's it. TunnelFleet handles the rest from here.
Using your connected cloud provider credentials, TunnelFleet creates the VM with a cloud-init script as user-data. No SSH keys needed.
# TunnelFleet calls the DigitalOcean API:
POST https://api.digitalocean.com/v2/droplets
{
"name": "vpn-london-01",
"region": "lon1",
"size": "s-1vcpu-1gb",
"image": "ubuntu-22-04-x64",
"user_data": "#cloud-config (generated by TunnelFleet)"
}On first boot, the cloud-init script installs WireGuard, generates keys, configures the interface, and starts the service. Your server appears as online in the TunnelFleet dashboard.
The Droplet is created via the cloud provider API. You don't need to log in to DigitalOcean.
WireGuard packages are installed via apt during cloud-init. No manual package management.
Private/public keypairs are generated on the server. The private key stays on the VM.
sysctl settings for IPv4 and IPv6 forwarding are enabled automatically.
UFW rules allowing WireGuard UDP traffic are applied. Only the necessary port is opened.
wg-quick@wg0 is enabled and started. WireGuard persists across server reboots automatically.
In TunnelFleet, you fill in a server name, select a region and size, then click "Deploy". That's the only user action required. Everything else (Droplet creation, WireGuard setup, firewall configuration) happens automatically.
Typically 90–180 seconds. The majority of this time is DigitalOcean creating the Droplet. cloud-init runs in parallel and usually completes within 60 seconds of the VM becoming accessible.
The default configuration covers the most common use case. If you need advanced configuration (custom subnets, specific MTU values, etc.), consult the documentation for supported customisation options.
Yes. TunnelFleet supports deploying multiple servers. Each server goes through the same automated provisioning flow independently.
It takes about 2 minutes. No SSH, no Linux expertise required.