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. 01reconDocker present?
2. 02reconalready deployed?
3. 03actStart the serververify
4. 04actThe UDP port is listeningverify

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. 01verifyStart the serverVerified bydocker ps --filter name=factorio --format "{{.Status}}" | grep -c Up
2. 02verifyThe UDP port is listeningVerified byss -ulnH "sport = :34197" | grep -c 34197

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 game servers recipes

1. 01Minecraft Server (Java)Configurable Java Minecraft server (version, type, players, RAM), as a systemd service.
2. 02Valheim ServerDedicated Valheim game server via Docker.
3. 03Mumble ServerMumble (murmur) voice server, started and verified.
4. 04Minecraft Bedrock ServerDedicated Minecraft Bedrock server via Docker.
5. 05Terraria ServerDedicated Terraria (TShock) game server via Docker.