One 48U liquid-cooled NVIDIA rack-scale domain on the current configuration.
Aloom MW1 / Basis of design / Rev B
A ≤1 MW facility-input concept.
Four C250 allocations.
Aloom publishes a Rev B concept basis for modular inference infrastructure using commercially supplied rack-scale compute references. Site, utility, OEM configuration, project scope, delivery and operating responsibility remain open and project-specific.
Concept design—not for construction. No built or measured customer MW1 is represented, and Aloom has not delivered a customer MW1. Final facility input, critical IT, OEM configuration, performance, availability, delivery and operating responsibility require accepted project inputs and executed terms.
Smallest complete unit
C250 defines the proposed isolation boundary.
A rack is equipment. The C250 concept defines a proposed coordinated electrical, thermal and compute isolation and accounting boundary. A future project would select and commission the compute, fabric, local safety, conversion, liquid-cooling and telemetry interfaces together; durable data, ingress and quorum remain outside that proposed cell boundary.
One physical failure domain. One declared accounting envelope.
Current HPE upstream design allowance for GB300 NVL72; final value follows the selected OEM.
The MW1 concept uses one dedicated reference transformer per C250. Campus-scale systems may preserve the same protected feeder boundary through shared upstream transformation.
A declared cell fault may stop one rack domain. Containment and surviving useful output require accepted design and tests.
Metering rule Each C250 allocation equals its measured cell feeder plus one measured share of common mechanical and house load. The 192 kW rack provision is an upstream allowance—not predicted continuous draw. Simultaneous rack and sidecar peaks close through the accepted OEM profile and site demand controller.
Compute plane
Commercial hardware references. Integration scope remains project-specific.
The MW1 concept treats the rack as one component inside a proposed electrical, thermal, network and control boundary. A project-specific basis would select the compute platform and define Aloom’s integration responsibility in executed terms.
NVIDIA GB300 NVL72
- Rack
- 48U / 600 mm wide
- Compute
- 72 B300 GPUs / 36 Grace CPUs
- Power
- 142 kW NVIDIA maximum
- HPE EDPp / busway
- ~155 kW / provision to 192 kW
- Cooling
- Direct liquid + residual air
- Loaded mass
- ~1.5–1.58 t by OEM
*Configuration and availability require a current written OEM or reseller quote. Nothing is ordered or reserved; price and lead time remain open.
NVIDIA product sourceAMD Helios
- Frame
- Double-wide Open Rack Wide
- Compute
- 72 MI455X GPUs / 18 EPYC CPUs
- Power
- Public envelope not closed
- Cooling
- Direct liquid / OEM schedule required
- Status
- AMD reference design
- MW1 count
- Not claimed before OEM data
An AMD-based concept could be studied only after an applicable OEM site-planning package and current written quote are accepted; it is not in the base MW1 reference.
AMD product sourceEngineering basis
Grid to rack. Heat back out.
The published Rev B concept basis is represented by an electrical single-line and cooling functional schematic. These are not construction or commissioning documents. Any future project would define revision control and commissioning evidence only under an executed scope.
Electrical single-line / Concept
Cooling functional schematic / Concept
V̇ = Q/(ρcpΔT)At 0.6–0.7 MW, water-equivalent recirculating-flow scenarios for ΔT 10 / 15 / 20 K are ≈52–60 / 34–40 / 26–30 m³/h. Not OEM rack flow, selected FWS flow, pump duty, pipe size or water consumption.
Inference fault model
No resilience claim without a loss case.
For workloads designed and tested for retry, a declared cell fault may allow work to restart elsewhere with temporary capacity loss. Session state, model/data durability and shared safety systems require explicit design and evidence.
| Layer | Concept or study posture | Required closure and evidence | Status |
|---|---|---|---|
| Compute cell | Base concept: 4 C250 allocations; optional fifth-cell study | A declared cell fault may stop one rack domain. Drain, retry and any surviving-output target require accepted scheduler, workload, data and power/thermal tests. | Concept; not tested |
| Local NVMe | Proposed cache or scratch role; not the sole durable copy | Source of truth, rehydration, replacement and recovery testing remain open. | Target; not implemented |
| Model and project data, if deployed | Replication or erasure-coding design options | Copy count, placement, independence, consistency, backup and restore, and cell-loss evidence remain open. | Target; not tested |
| Ingress and control | A/B network and quorum design options | Failure domains, quorum membership, routing, state persistence, split-brain handling and failover testing remain open. | Target; not implemented |
| Cell power and thermal interface | Target 1+0 cell boundary; equipment count and CDU sharing open | Containment and shared-dependency consequences require accepted electrical, thermal and controls design and testing. | Reference; open |
| Shared heat rejection | Redundancy objective and one-out duty open | Accepted duty, ambient, modules, pumps, controls, ride-through, common modes and loss-case testing are required. | Open; no N+1 design |
| Fire and life safety | Applicable code and authority requirements; site-specific | Qualified fire strategy, cause and effect, interfaces, commissioning and applicable-authority acceptance remain open. | Open; no compliance claim |
Asset-efficiency reference for workloads that may support retry. Scheduler, data, network, power and thermal behaviour require accepted design and tests.
Requires accepted house power, protection, scheduler, data, network, thermal and recovery design plus commissioning tests.
Project-basis gates
Five project-basis inputs remain open.
These parallel closure families identify evidence that would be required before Aloom could consider a project-specific proposal. They are not a sequence and do not assure a quote, price, order, availability, programme or delivery.
| Gate | Required closure | Status | Does not establish |
|---|---|---|---|
| Workload and acceptance | Declared workload, precision, latency, availability and useful-output test. | Open; project-specific. | Performance or service-level agreement. |
| OEM and supply | OEM configuration, written quote, rack site-planning guide and delivery window. | Open; not reserved. | Bill of materials, quantity, price or lead-time commitment. |
| Utility and electrical | Utility capacity, fault level, protection study, earthing and connection agreement. | Open; network-service-provider and site input required. | Secured grid capacity. |
| Thermal and site limits | Coolant chemistry, temperatures, ΔT, flow, pressure, water and acoustic limits. | Open; project-specific. | Selected plant, flow or water duty. |
| Approvals and operability | Planning, fire engineering, structural loads, security and maintainability review. | Open; authority and project input required. | Permit, compliance or construction-readiness claim. |
Start / Project configuration
Bring the project inputs.
Start with a scoped discussion.
A future written study proposal could define the workload, utility position, rack reference, cell count, single-line, cooling schematic, programme assumptions and commercial boundaries. No study, build, delivery or operating commitment is made on this page.
Request an MW1 study scope discussion Inspect the 50 MW campus boundary