Powered-site + GPU deployment matching
Start with the asset you can document. See what physically fits, then calculate the return for the party supplying the site or the GPUs.
Who brings what
A GPU deployment needs power, a facility and GPUs. Those are almost never owned by the same party — and with a containerized deployment the facility is delivered, not built. Here is who supplies what, and how each one gets paid.
Two more parties sit outside the deal: the electricity supplier sells power to the deployment, and the compute buyer pays for the output. Neither is included in the returns below unless you enter their terms.
Choose one starting point. You can compare the full project later.
Use power that can run continuously after the site’s required reserve—not the number printed on a breaker. The estimate fits complete GPU systems and leaves unused power visible.
A Kimi unit is one published 16-GPU logical pod. Two pods can share one physical 48U rack. Other systems use their sourced complete-rack packing.
This private helper recognizes power, price, location, GPU system, PUE and GPU/rack quantity in your browser. It does not verify capacity, qualify a site, find a counterparty or upload your text. Review every value it fills.
ROI calculator
The deployment above already supplies GPU count, IT load, site draw and rack count. Add verified capital and contract terms below; every return updates immediately.
Linked automatically
Power, GPU system, rack or pod quantity, PUE and fabric entered above flow into every return below. Only the missing commercial terms need entry.
You provide the powered facility—not the GPUs. Test hosting revenue against the GPU-ready build or retrofit cost and site O&M.
You provide the GPUs—not the site. Test net compute revenue after hosting and electricity against hardware cost.
Test combined capital against compute revenue, electricity and site O&M. Internal hosting payments cancel here.
Enter the GPU-ready build or retrofit cost, hosting fee and site O&M.
Start here · real inputs
Type contracted figures. Grey example values are not included until you enter or load them.
Implied net compute revenue—
Work backwards from the goal
Choose a goal—not a market forecast. The selected owner view determines whether this solves for a hosting fee or a net GPU-hour payout.
Equivalent simple annual cash yield: 33.3%
The physical deployment above is already linked.
This is the minimum arithmetic threshold under the costs and target entered here—not evidence that the market will offer the rate, a quote, or a guaranteed return.
Token or workflow revenue needs an exact-stack throughput benchmark and proven demand. Public API prices are buyer retail references and do not establish GPU-owner payout.
Operating cash excludes any costs not entered here, including software, staffing, insurance, spares, maintenance, taxes and platform fees outside the net payout.
The calculator opens with this editable illustration so the live formulas are visible immediately. Clear it to enter your own figures, or reload it here at any time.
Mechanics-only sample:
Editable arithmetic inputs only. They are not one sourced project, a quote, forecast, market benchmark, offer, or guaranteed return.
How the cash flow connects
The hosting fee is revenue to the site and a cost to the GPU owner. Electricity is a deployment cost. Compute payout is revenue to the GPU owner.
Returns appear only from entered figures. Annual yields are unlevered; payback is simple payback before financing, tax, depreciation and residual value.
Inputs are visible because site power is not a GPU specification.
These definitions describe how this calculator uses each term. Project contracts and final engineering documents control.
System architecture
Power, IT and heat rejection are separate functional blocks because each scales to a different engineering limit. They work as one system; they do not mean three IT containers.
Receives the site utility service and safely conditions, protects and distributes electricity.
Houses the GPU racks, fabric, controls and the equipment-side cooling connections. Fiber enters here.
Collects heat from the racks through a CDU liquid loop or an air-cooling loop, then rejects it outdoors.
Reference functional starting basis: one power block + one IT block + one heat-rejection block, subject to the selected rack density, site conditions and final vendor design. These are functions, not guaranteed shipping-container counts. Counts above scale independently; 10 MW+ requires a campus electrical and thermal design rather than simple container multiplication.
Partial source reference only—not delivered facility CAPEX. Power capacity, rack fit, and cooling topology remain provisional pending a signed one-line and platform-specific GA. Chiller, pump, tank, redundancy, and balance of plant remain open.
Energy balance says almost all electrical input ultimately becomes heat; the whole-site heat line therefore equals total site draw. The server source separately publishes a slightly higher thermal maximum, so early cooling selection uses that higher value and flags the conflict. These are alternate design bases, not additive operating loads.
Enter downside and upside inputs to show the table.
| Platform | — | Region | — |
|---|---|---|---|
| Pods / physical racks | — | Nodes | — |
| Customer GPUs | — | Cooling | — |
| Critical IT | — | Site PUE | — |
| Total site power | — | PUE overhead incl. cooling | — |
| Modules | — | Measured output | — |
| GPU hardware in facility budget | — | Facility budget | — |
|---|---|---|---|
| GPU hardware (separate) | — | Hosting fee | — |
| Operator EBITDA | — | Operator ROI / payback | — · — |
|---|---|---|---|
| Power pass-through | — | Customer invoice | — |
| Provider payout | — | Financing service | — |
| Owner operating cash | — | Owner cash after debt | — |
| Owner unlevered yield / payback | — · — | Combined project CAPEX | — |
| Project operating cash | — | Project cash after debt | — |
| Project unlevered yield / payback | — · — | Stress summary | — |
Indicative planning scope only. Not a vendor quote, financing offer, offtake commitment, or return guarantee.
