Published specs, corrected for reality
Nameplate numbers are optimistic. A rack is rated for 600 kW, a drive is rated for five years, an interconnection queue is rated in gigawatts. None of those survive contact with a real site. These are free tools that do the correction, on public data, with every constant shown.
The bench
Rack Budget
Power, cooling and floor area for an AI hall. Start from a megawatt budget or from a fleet size and get the other side, plus the heat you have to reject and the room it lands in.
Open Rack Budget →Crash Cart
Drive failure triage on thirteen years of public fleet telemetry. Not a dashboard, a work queue: which drives to pull this week, ranked by risk times blast radius, with the evidence that flagged each one.
Where the power is
Siting under a power constraint. Interconnection queue, existing and proposed sites, and grid carbon in one view, answering where you can actually energize a few hundred megawatts before the end of the decade.
Outage replay
Public cloud incidents reconstructed as an operator timeline. What the console showed, when it showed it, and how long the truth took to surface. A study in why incidents run long.
How these are built
Public data only
Every input is something you could go and download yourself. Nothing proprietary, nothing behind an NDA, nothing you have to take on trust.
Constants in the open
Each tool states its assumptions and shows the arithmetic that produced every number. If you disagree with a constant, you know exactly which one to argue with.
One decision out
Numbers on a screen are data. Each tool ends by naming the thing that will actually stop you, because that is the part someone has to act on.
Built by a person Adrian Mucha
I design the console and ship it to production myself
I am a product designer working on the software most designers avoid: data centers, AI tooling, operator consoles where a wrong click costs real money. A repair console saving around $10M a month, a data-access portal cut from 10 days to 48 hours, production code that ships as a pull request rather than a handoff document.
Infrabench is that same work, done in the open on public data. If your engineers are drawing your operator UI because you have not hired a designer yet, that is the gap I fill.