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.
- 01reconIIS already installed?
- 02reconis port 80 already taken?
- 03actInstall IISverify
- 04actStart the serviceverify
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.
- 01verifyInstall IISVerified by
(Get-WindowsFeature Web-Server).InstallState - 02verifyStart the serviceVerified by
(Get-Service W3SVC).Status
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.
search by intent — type “firewall”, get ufw
- 01Read-only reconnaissance before any change
- 02Every command signed by your browser, approved by you
- 03Each step verified before the run moves on, every run kept in the history
SEC.04
More web server recipes
- 01nginxnginx web server, started, enabled at boot and verified.
- 02CaddyCaddy with automatic HTTPS for a domain.
- 03Apache httpdApache web server, started, enabled and verified.
- 04HAProxyHAProxy load balancer, started and verified.
- 05TraefikTraefik reverse proxy via Docker, with the dashboard and automatic TLS.
Verified recipe
Run this recipe on your server
Connect a server, launch the recipe, and approve each step as Servor executes and verifies it. Free plan, no card required.