Loading…
Loading documentation...
Inspect your environment fabric in the 3D Network Builder, save network checkpoints and connect private subnets over WireGuard VPN.
Commands checked on 2026-11-12 with WireGuard 1.0, Ubuntu 24.04, sau CLI 0.2.0.
Your Servers Are Up virtual machines, workstation devices, and remote office or cloud sites will communicate over an authenticated, modern ChaCha20-Poly1305 WireGuard mesh and private VPC subnet fabric—visualized across four layers (L1 WAN/VPN peers, L2 Gateway/Firewall, L3 Subnets/VLANs, and L4 Compute Nodes) on /dashboard/network—with saved rollback checkpoints before every topology change.
/dashboard/instances) or an active environment on Billing & account > Plan & capacity (/dashboard/environment).macOS, Windows, or Linux) or wireguard-tools (wg, wg-quick) on a remote Linux gateway if you are establishing a site-to-site tunnel.sau CLI v0.2.0 (sau network ...) for scripting checkpoints and tunnel audits.Open Network > Map (/dashboard/network?tab=map). The four-plane fabric view shows only your own tenant's WAN edge, perimeter rules, private RFC1918/RFC6598 subnets, and compute nodes.
Before adding subnets, VPN peers, or east-west ACL changes, save a named configuration checkpoint so you can roll back with one click or command:
sau network checkpoint-create pre-vpn-rollout --description "Baseline fabric before adding workstation and branch VPN peers"
sau network checkpoints-list -o table
To reach PostgreSQL, Redis, SSH, or internal admin dashboards without opening any public ports:
/dashboard/network?tab=vpn) (or open a single server's VPN panel if you only need point-to-point access to one VM).ops-macbook), and download or scan the generated .conf profile. Keys are generated for your device alone; only the public key is registered on the gateway./etc/wireguard/sau-dev.conf with 0600 permissions:[Interface]
PrivateKey = YOUR_LOCAL_DEVICE_PRIVATE_KEY
Address = 172.30.1.50/32, fd10:1::50/128
DNS = 172.30.1.1
[Peer]
PublicKey = SAU_ENVIRONMENT_VPN_PUBLIC_KEY
AllowedIPs = 172.30.1.0/24, fd10:1::/64
Endpoint = 203.0.113.10:51820
PersistentKeepalive = 25
Notice AllowedIPs = 172.30.1.0/24, fd10:1::/64 (split-tunnel mode): only traffic bound for your private cloud subnet enters the encrypted tunnel, while normal internet browsing stays on your local connection.
To bridge an entire remote subnet (for example an OpenStack or branch subnet 172.24.10.0/24) with your Servers Are Up environment subnet (172.30.1.0/24):
/dashboard/network?tab=vpn), choose Site-to-site tunnel, enter the remote gateway's public IPv4 (198.51.100.88:51820), paste its WireGuard public key, and declare the routed remote CIDR (172.24.10.0/24).198.51.100.88), enable kernel IPv4/IPv6 forwarding and bring up the matching WireGuard interface:sudo tee /etc/sysctl.d/99-sau-vpn-forward.conf > /dev/null <<'EOF'
net.ipv4.ip_forward = 1
net.ipv6.conf.all.forwarding = 1
EOF
sudo sysctl --system
sudo tee /etc/wireguard/wg-s2s0.conf > /dev/null <<'EOF'
[Interface]
PrivateKey = REMOTE_SITE_GATEWAY_PRIVATE_KEY
Address = 172.30.255.2/30
ListenPort = 51820
[Peer]
PublicKey = SAU_ENVIRONMENT_GATEWAY_PUBLIC_KEY
Endpoint = 203.0.113.10:51820
AllowedIPs = 172.30.1.0/24, 172.30.255.1/32
PersistentKeepalive = 25
EOF
sudo chmod 0600 /etc/wireguard/wg-s2s0.conf
sudo systemctl enable --now wg-quick@wg-s2s0
172.24.10.0/24 (or on your branch router's DHCP gateway) pointing 172.30.1.0/24 to the Linux WireGuard gateway.On Network > Map (/dashboard/network?tab=map), Layer 3 lets you separate public-facing ingress nodes from isolated database and storage VLANs so a compromised web container cannot scan unrelated internal workloads. Bind internal services (such as PostgreSQL listen_addresses = '172.30.1.27') strictly to the server's private interface.
Bring up your tunnel, inspect the cryptographic handshake and transfer counters, and verify private reachability:
sudo wg show
sau network tunnels-list -o table
ping -c 3 172.30.1.27
sudo wg show prints a latest handshake timestamp within the last two minutes and non-zero transfer: ... received, ... sent counters. On Network > Map (/dashboard/network?tab=map), your peer badge updates from never connected to active.
wg-quick up succeeds) but latest handshake never appears. WireGuard is connectionless UDP (51820/udp by default) and wg-quick up succeeds even if packets drop upstream. Confirm UDP 51820 is not blocked by guest/corporate Wi-Fi and verify both sides switched PublicKey values accurately (a common mistake is pasting a peer's own public key into [Peer]).ping packets succeed. Classic Path MTU blackhole! Add MTU = 1380 under [Interface] on both peers (especially over PPPoE fiber or cloud VXLAN underlays) and restart wg-quick.sau network checkpoint-restore pre-vpn-rollout or click Restore on Network > History (/dashboard/network?tab=history)..conf across teammates, because revoking one lost laptop should take one click without disrupting anyone else.sau network checkpoint-create ...) before every firewall or subnet refactor./dashboard/entra-suite) and Access > Cloud bastion (/dashboard/bastion) when contractors need application-specific access rather than L3 subnet routing.Every Servers Are Up virtual machine and container includes an integrated HTML5 browser-based SSH, RDP, and VNC console in your dashboard, default-off inbound firewall rules with per-IP allow-lists, and full programmatic control via REST API v1 and Model Context Protocol (MCP). Explore our Virtual Datacenter Plans or reach out to Servers Are Up Support.