GRUENCY  /  Workstation architecture

Workstation architecture
is a discipline.

Anyone can pick parts that fit. Architecture is the other thing: planning lanes, watts, decibels and bytes together so the machine performs on day one and still makes sense in year three. It is the discipline behind the 2017 world-first 11-GPU build — and every WS.COMPUTER machine since.

The reference build →
A · The budgets

Four budgets, one machine

Every workstation is a negotiation between four scarce resources. Architecture is deciding the trade-offs explicitly — before they decide themselves.

  • 01Lanes — PCIe topology planned per slot, no silent x4 surprises
  • 02Watts — sustained draw measured, power delivery with headroom
  • 03Decibels — an acoustic ceiling agreed like any other spec
  • 04Bytes — memory channels, VRAM and storage bandwidth matched to the workload
B · The method

From workload to drawing

  • 01Workload analysis — what runs, how long, at what precision
  • 02Topology plan and component list, every part with written reasoning
  • 03Thermal and acoustic design — loop or air, engineered not hoped
  • 04Chassis: CAD design, laser-cut alloy, transport and serviceability
  • 05Delivered as a GRUENCY build — or as a design you take elsewhere
The 2017 world-first 11-GPU prototype — eleven red PCIe latches in a row under the glass top, original build documentation

Fig. 01 · The 2017 world first — eleven slots under glass, original documentation

Proof

The reference
build.

World-first prototype

11 water-cooled GPUs. One chassis. 2017.

Dual-CPU server platform, single custom loop, CAD chassis — architecture at its ceiling.

OctaneRender community

Benchmark-leading configurations

Throughput that came from topology, not luck.

Since 2014

Every generation, one discipline

A decade of architectures that survived their third year.

FAQ

Asked about
architecture.

Is this consulting or building?

Both, in that order. Architecture precedes the build — and can be delivered alone, as a written design another party executes.

Can you architect a system someone else builds?

Yes. Topology, thermal design and component reasoning are delivered in writing; the build can happen anywhere. See Technical advisory for reviews of existing designs.

What makes this different from a configurator?

A configurator picks parts that fit. An architect plans budgets — lanes, watts, decibels, bytes — so the machine still makes sense in year three.

Contact

Plan it before
you buy it.

Describe the workload and the constraints. Sebastian answers every enquiry personally — within two working days.

Prefer email? [email protected]