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. 01reconTailscale already installed?
2. 02reconalready connected to a tailnet?
3. 03actInstall Tailscaleverify
4. 04actConnectverify

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 TailscaleVerified bytailscale version
2. 02verifyConnectVerified bytailscale status >/dev/null 2>&1 && echo ok || echo pending

SEC.03

Variables

What you choose before launching — the recipe fills in the rest.

SEC.04

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.05

More networking recipes

1. 01WireGuardWireGuard VPN: generates keys, configures an interface. Destructive: touches the network.
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.