Physical Infrastructure
Some workloads earn their own hardware. We advise on when that is true and how to do it without recreating 2009.
We compare the cost of running your workloads in the cloud with the cost of buying, housing and operating your own hardware.
- datacentre selection
- colocation
- hardware sizing
- network design
for workloads that earn their own hardware.
When physical wins
- Steady, predictable compute at scale
- latency that must be engineered, not hoped for
- data that regulation or contract nails to a geography
These cases are real and increasingly common: the industry just spent a decade pretending they weren't.
What advised means
You own and run it; we make sure you decide and build it correctly.
- Sizing grounded in measured load rather than vendor sheets
- colocation and site selection with jurisdiction in mind
- network design that doesn't make the datacentre an island
- the honest run-cost model, including the ops capability you will need: the cost most proposals omit.

The deliverable
A prioritized action plan:
- the sizing
- the site or colocation choice
- the network design
- the run-cost model against the cloud alternative
argued rather than assumed.

Considering your own iron?
A 30-minute call on the workload and the numbers driving the thought. Sometimes the answer is yes, and here is the design
; sometimes it is no, and here is why
.
