Turn Servers Into Working Capacity — Then Deploy Whatever Runs On It
The problem
- Getting a physical server ready to run real workloads is usually a manual, one-off project — different every time, with no consistent record of what was actually done to it.
- Hardware differences between machines are easy to miss until a workload fails to run correctly on the wrong box.
- Most bare-metal tooling assumes every server exists to run Kubernetes — a poor fit when what you actually need is a plain container or VM for something else.
The solution
- Gough inventories and health-checks a new server automatically as soon as it is connected, then rolls out the workload you choose as a versioned Biome — a Kubernetes node or storage agent from the built-in catalog, or a custom one you author, such as a Nextcloud server or a Windows AD domain controller — each an LXC container or a KVM VM.
Outcomes
- A newly connected server typically finishes discovery, network setup, and its first workload in about 8–12 minutes — no manual configuration.
- Kubernetes is one workload you deploy this way, not a prerequisite — the same catalog and process cover any container or VM you need to run.
- Every step is recorded automatically, so there is always a record of what was deployed, when, and to which machine.