systemd service

Reconnaissance — before touching anything

The run starts read-only. Before a single change, Servor checks the real state of your server — a real machine is rarely clean, and only what is actually there decides what happens next.

• 01does a service with the same name already exist?
• 02does the user exist?

The steps — each one proves itself

The playbook below guides the run; the model adapts each command to the distribution and state found during reconnaissance. A step only counts as done when its verification passes.

1. 01

   Write the unit

   Verified by

   test -f /etc/systemd/system/${name}.service && echo ok
2. 02

   Enable

   Verified by

   systemctl is-active ${name}

Variables

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

${name}

Service name

${exec}

Command

${user}

User

How Servor runs this recipe

Servor is zero-knowledge: the platform cannot execute anything on its own. When you launch this recipe, an AI 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 to the agent, which verifies the signature locally before executing.