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. 01recontools already present (install only the missing ones)
2. 02recondistro and package manager
3. 03actInstall the toolsverify

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 the toolsVerified byiperf3 --version | head -1 && mtr --version && traceroute --version | head -1 && dig -v && tcpdump --version | head -1

SEC.03

Guardrails

Non-negotiable instructions the run must respect, whatever it finds on the server.

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

Deploy on Servor button

Maintain Network tools or a project that needs it? Put this button in your README or on your site: one click and your users install it on their own server.

SEC.06

More networking recipes

1. 01TailscaleTailscale mesh VPN: auth key or login link, without touching the server DNS.
2. 02WireGuardWireGuard VPN server + a first client, without touching routing. Destructive: network interface.
3. 03Pi-holePi-hole v6 (DNS + ad blocking) in a container, on the chosen IP. Destructive when listening on 0.0.0.0 (port 53).
4. 04AdGuard HomeAdGuard Home filtering DNS, local UI. Destructive: may free port 53.
5. 05OpenVPNOpenVPN server via the road-warrior script (angristan), first client created. Destructive: network.