wubbery://data-centres — colocation, wholesale and enterprise halls
The constraint was never compute. It is the substation, the water permit and the busbar.
You are turning customers away while half the hall sits idle, because the thing that binds is not the thing anyone reports. WUBBERY names which of power, cooling, space, weight and network runs out first — and refuses the placements that look fine on a nameplate and fail on a Tuesday.
What actually binds
The number everyone quotes is the one least likely to bind
An operator with space to sell describes rack space, and the substation decided the answer two years ago. Capacity is the minimum across power, cooling, space, floor loading and network — and the surplus on every other dimension is bought, financed and returning nothing. Quantifying that is what turns a capacity conversation into an investment one.
Redundancy claims are inherited, not re-checked
N+1 means one more unit than needed only when every unit is identical, and plants stop being identical after a decade of replacements. A hall with four 100 kW units and a 250 kW expansion unit has plenty of surplus and is not N+1, because losing the large one takes more than the surplus. The claim was true when it was made and nobody recomputed it.
The failure modes are invisible until they are total
A dual-corded rack sized against the sum of both feeds reads as comfortable on every meter in the hall and trips the survivor during A-side maintenance. An AI rack inside its kilograms-per-square-metre rating exceeds the panel's point load and breaks the floor during installation, on castors. Neither degrades. They are fine, and then they are an outage.
Measured, on a named alternative
Guards are reported blocked-of-attempted, never as a percentage — “zero violations” without the attempt count is a claim about nothing. Each is posed against a case that passes the check the industry already runs, because a guard that only catches obvious mistakes measures nothing.
8 kW across an A+B pair reads as 4 kW per feed on every meter you have. The rack runs for a year and trips the survivor the first time you do planned maintenance.
Refuses the rack before it is energised, and states the load it will carry safely on the pair you have installed.
You have rack space to sell and cannot sell it. Nobody can say which resource is the wall, so the next purchase is a guess.
Names the one resource that is holding the hall back, and prices the capital sitting idle behind it.
The plant is documented N+1. It has 200 kW of surplus. It is not N+1, and nobody has re-run the arithmetic since the expansion unit went in.
Re-tests the redundancy claim against the plant as it stands today, and refuses it when it no longer holds.
A megawatt rack at 415 V needs 2,410 A. No busbar you can buy carries it, and the loss goes as the square of current.
Refuses the design, then returns the specification that makes the same power deliverable through your existing distribution.
Sustainability owns the water number, engineering owns the power number, and the pair is what decides whether the site is permitted.
Clears a cooling design only when it satisfies the water permit and the power cap at once, and refuses the site when nothing does.
The schedule is built around equipment lead times, then handed a queue position that is four to seven years out.
Tests the grid date against your online date, sizes a bridge when one exists, and says plainly when none does.
An AI rack weighs three times a conventional one through four small contact patches. The distributed figure passes; the point load breaks the panel during install.
Refuses the rack that passes the rating everyone quotes and fails the one that actually breaks the floor.
The single-line diagram shows two independent feeds. One transfer switch is common to both, and the site is not Tier III.
Proves or disproves concurrent maintainability against the real single-line diagram, and names the component that breaks it.
Reproduce every number above
One command, one seed, the same answer — on your hardware, in front of you. Almost no infrastructure vendor can do that, and it is the only reason to believe any of the figures on this page.
POST https://api.wubbery.com/v1/bench/all-modules
{ "seed": 1 }What we will not claim: these are steady-state models over the state you supply. No phase imbalance, no inrush, no humidity or rate-of-change limits, and no seasonal water restriction — an annual permit can be satisfied by a design that fails in August, and the month is what gets a site refused. Every module states its own boundary in its output, and we would rather you read them than trust the summary.
Figures measured at seed 1 on the WUBBERY substrate engine and reproducible with the command above. WUBBERY is independent; company and product names are used for identification only and imply no endorsement.