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. 01reconWindows edition and build (ProductType 1 = workstation, 2 = DC, 3 = server), RAM
2. 02reconHyper-V already enabled?
3. 03reconhardware virtualization available? VM without nested virtualization? (HypervisorPresent True makes VirtualizationFirmwareEnabled unreliable)
4. 04reconanother hypervisor active (VirtualBox/VMware)?
5. 05actEnable Hyper-Vdestructiveverify

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. 01verifyEnable Hyper-VVerified byif (Get-Command Get-WindowsFeature -ErrorAction SilentlyContinue) { (Get-WindowsFeature Hyper-V).InstallState } else { (Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All).State }

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 Hyper-V 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 containers recipes

1. 01Docker EngineDocker Engine + Compose from the official repository, service active, hello-world verified.
2. 02Docker ComposeDocker Compose plugin (docker compose), installed and verified.
3. 03PodmanPodman (daemonless containers, rootless capable), verified.
4. 04PortainerPortainer CE (LTS) Docker management web UI, admin preconfigured.
5. 05k3s (lightweight Kubernetes)Single-node k3s cluster. Destructive: configures networking and a container runtime.