It works on the day it arrives.
Custom Linux and Windows, pinned to a known-good stack.
The gap between hardware arriving and hardware being useful is usually a driver, a kernel version and an accelerator runtime that disagree with each other. We resolve that once, build the image, pin every version in it, and ship the machine with it installed.
Linux and Windows are both first-class. Windows matters more in this segment than infrastructure vendors like to admit — engineering, media and instrumentation workloads live there, and a machine that only boots Linux is a machine half those teams cannot buy.
Every image carries a software bill of materials. That is a Cyber Resilience Act obligation for products with digital elements[src], and it is what a procurement security review asks for first.
| Operating system | Linux and WindowsImage built to the workload; kernel, driver and runtime versions pinned |
|---|---|
| Software bill of materials | Per imageSPDX or CycloneDX |
| Provisioning | Installed and configured before shipment |
| Commissioning | Acceptance under load on site |
| Monitoring | Energy, thermal and utilisation, wired on first boot |
| Vulnerability handling | Coordinated disclosure policy and security contact |
| Support | Named engineering contactNot a ticket queue and not a commissioned salesperson |
| Spare parts | Held and shipped from stock |
Every deployment ships with the documentation a procurement team actually asks for: declaration of conformity with the standards and versions listed, accredited test reports, physical and thermal envelopes, warranty terms and claim procedure, support response commitments, spare-parts availability, and the software bill of materials.
Assembled once, issued with the system. Nothing in that list sits behind a form.