Server Builds in BuildSmith: Planning in Configurations, Not Carts
Most BuildSmith plans are one machine. Server mode is for the other question: what does the rack version look like? The planner switches its parts universe to the 92 servers in the directory, drops the idea of a list price total entirely, and plans in configurations and quotes instead.
That last change is the honest one. Servers in this dataset carry no public list prices, from the 1U nodes to the 8 GPU systems, because that is how the market sells them. A consumer planner that printed a total would be inventing it. Server mode prints the configuration, the accelerator count, the host CPU family and the memory, then hands you the vendor and specialist store route to pricing.
Who makes the servers in the directory
| Maker | Server listings |
|---|---|
| Dell | 15 |
| HPE | 12 |
| Supermicro | 11 |
| Gigabyte | 10 |
| Lenovo | 9 |
| ASUS | 7 |
| TYAN | 4 |
| Inspur | 4 |
Listings by maker
The planning logic still starts with memory, now at fleet scale: total accelerator memory across the node, host cores per GPU, and the storage tier for checkpoints and datasets. EPYC and Xeon host options are presented side by side with their core counts from the data, the same comparison as our EPYC versus Xeon read.
The configuration language is deliberate. A server plan names the accelerator, the count, the interconnect and the host, because those four choices decide what the node can do, while the chassis brand mostly decides who services it. The directory's server list spans the big enterprise makers and the GPU dense specialists, and the planner presents both without a house favorite: what differs in the data is configuration coverage, not a score we assigned. Power gets planned at the node level too. An 8 GPU system is a room decision before it is a purchase decision, so server mode asks about rack power early and prints the draw of the planned configuration from published figures where they exist. Where a figure is not published, the plan says so, in the same spirit as the missing prices: a labeled gap beats a confident guess, especially in a six figure conversation.
Support is the final planning field, and it is a data field, not a vibe. The plan records which makers in the configuration offer local service through the retailer directory's specialists, because a node that earns money cannot wait on a shipping label. It is the least technical line in server mode and, in operations, usually the one that matters first.
Server mode ships after the desktop planner. The server category and the rack build are live today; BuildSmith is in development, waitlist on the homepage.