SEC.01

The playbook

The run starts read-only: the recon probes decide what happens next. The steps that follow are adapted to the distribution and state found — a real machine is rarely clean.

1. 01reconWireGuard already installed?
2. 02recondoes a WireGuard interface already exist? do not overwrite it
3. 03reconcurrent network interfaces (so as not to break access)
4. 04actInstall WireGuardverify
5. 05actGenerate the keysverify
6. 06actConfigure and enable wg0destructiveverify

SEC.02

What it verifies

Each step ships its own check. The run only moves on when the check passes, so what the recipe reports as done is what is actually on the server.

1. 01verifyInstall WireGuardVerified bywg --version
2. 02verifyGenerate the keysVerified bytest -s /etc/wireguard/privatekey && echo ok
3. 03verifyConfigure and enable wg0Verified bywg show wg0 >/dev/null 2>&1 && echo up

SEC.03

How a recipe runs in Servor

Servor is zero-knowledge: the platform cannot execute anything on its own. When you launch this recipe, a run reads the reconnaissance, plans the steps and asks for your approval. Each approved command is signed by your browser — with a key the server never sees — then relayed verbatim to the agent, which verifies the signature locally before executing.

SEC.04

More networking recipes

1. 01TailscaleTailscale mesh VPN (requires an auth key to connect).
2. 02Pi-holePi-hole (DNS + ad blocking). Destructive: changes the DNS resolver.
3. 03AdGuard HomeAdGuard Home filtering DNS. Destructive: may take over port 53.
4. 04OpenVPNOpenVPN server via the road-warrior script. Destructive: network.
5. 05DNS resolver (Unbound)Unbound recursive DNS resolver, on localhost.