Edge · Xalant Edge · Capacity estimator
Edge · Tool
Capacity estimator
Three inputs in, four figures out, and every line of the arithmetic on the page. It sizes a site. It quotes nothing.
Design estimate — derived, never measuredThe estimate
Anything below one pod rounds up to one pod. A pod is a container, not a fraction of one.
Sets the rack density, which sets the cooling line, which sets the design PUE and the backhaul allowance.
The markets in the pipeline. Selecting one sets which of the two deployment clocks the estimate is on.
The estimate below updates as you change these. The address bar keeps up, so the link carries the estimate with it.
Design estimate · derived from published design constants, not measured
- 20
- Containerised pods
- 6.5
- MW electrical
- 10
- Gbps backhaul
- 1
- Gateway pads
Design estimate for South Oregon: 20 containerised pods, 6.5 megawatts electrical at a design PUE of 1.3, 10 gigabits per second of backhaul across 1 gateway pad. Time to power: first build.
Time to power · First build
The first build in South Oregon is planned to take up to nine months of controlled build. It is the one that proves the kit.
The working
- Containerised podspods = ceiling( 5 ÷ 0.25 )20
- Electrical load at the meterMW electrical = 5 × 1.36.5 MW
- Backhaul the workload asks forGbps = 5 × 210 Gbps
- Gateway padsgateways = ceiling( 10 ÷ 10 )1
Cooling line: N+1 precision air, which is what selects the design PUE above.
Every constant it used
- IT load per pod — 0.25 MW-IT
- Xalant Edge design basis (spec §5.2 unit ladder) · as of 2026-09-11 · A Xalant design figure, not a vendor rating. The estimator divides the requested IT load by this.
- Design PUE, containerised pod — 1.3 PUE
- Xalant Edge design basis (spec §5.2 pod spec table) · as of 2026-09-11 · Design target for N+1 precision air. Renders as a design target, never as a measured figure.
- Backhaul allowance, HPC — 2 Gbps per MW-IT
- Xalant Edge design basis (spec 5.2 workload profiles) · as of 2026-09-11 · Design allowance, not a measurement. Bulk job input and result sets move in scheduled windows rather than continuously.
- Design capacity per gateway — 10 Gbps
- Xalant Communications design basis (spec §5.3, §13) · as of 2026-09-11 · A Xalant design figure for a gateway pad. Never a third-party product rating, and always stated for the whole gateway.
Worked examples
Four estimates, computed the same way
Every row below comes out of the same function the tool uses, at build time. The second row is the first row with one input changed, which is the clearest way to see what the workload actually does to the answer.
| Input | Pods | MW electrical | Gbps | Gateways | Time to power |
|---|---|---|---|---|---|
| 5 MW-IT · HPC · Milwaukee | 20 | 6.5 | 10 | 1 | Repeat site |
| 5 MW-IT · AI training · Milwaukee | 20 | 5.75 | 5 | 1 | Repeat site |
| 0.25 MW-IT · AI inference · South Oregon | 1 | 0.33 | 1 | 1 | First build |
| 12 MW-IT · AI inference · North Georgia | 48 | 15.6 | 48 | 5 | Repeat site |
The formulae
- Containerised podspods = ceiling( 5 ÷ 0.25 )20
- Electrical load at the meterMW electrical = 5 × 1.36.5 MW
- Backhaul the workload asks forGbps = 5 × 210 Gbps
- Gateway padsgateways = ceiling( 10 ÷ 10 )1
Shown for the first row. The tool prints the same four lines for whatever is currently selected.
Exclusions
What this estimate leaves out
An estimate that hides what it left out is worse than no estimate.
- Bridge fuel. The tonnes-per-day line needs a sourced heat-content figure for LPG and there is not one in the constants file yet, so it is left out rather than guessed at.
- Local approval time. Zoning, environmental and building permits sit outside every duration here, and the jurisdiction sets them, not Xalant.
- Interconnection. Nothing on the pad is designed to depend on a public utility, so no queue position is modelled either way.
- Price. This tool sizes a site. It quotes nothing.
Reference render
Site & capacity · Request