A GB300 liquid-cooled AI data center container combines IT racks, power distribution, coolant distribution, heat rejection, monitoring, and safety systems within a transportable enclosure. A 40-foot high-cube proposal can be a useful planning reference, but it should not be treated as a universal ready-to-run configuration. Rack count, power scope, cooling design, and site conditions must be confirmed for each project.
Start with the project boundary
For a full project brief, use the container planning guide.
Before comparing container layouts, document what the supplier is responsible for. List whether the scope includes GB300 servers, racks, network equipment, UPS or battery storage, power distribution, CDU equipment, outdoor dry coolers, fire protection, controls, installation, and commissioning. A title such as “without UPS” is not enough if the technical schedules describe a different electrical arrangement.
Build one approved IT load schedule
Record the number of racks, server configuration per rack, typical operating load, peak design load, and future expansion allowance. Keep the same rack count and load assumptions in the power, cooling, distribution, and PUE calculations. Do not compare a cooling rating per rack with an unrelated total-container estimate.
Trace the cooling path and its interfaces
A common liquid-cooling arrangement uses cold plates at high-heat components, a secondary server loop, a coolant distribution unit (CDU), and a primary loop that rejects heat outdoors through a dry cooler. The CDU transfers heat between the loops and manages flow and temperature. The facility design should also account for residual room heat, pump power, filtration, leak detection, and service isolation.
Match coolant and operating limits
Specify fluid chemistry, concentration, material compatibility, water quality, filtration, pressure, flow, supply and return temperatures, and freeze protection for each loop. A reference proposal may use a glycol mixture, but the selected fluid must be compatible with the server manufacturer’s requirements and the complete cooling circuit. Define the site’s ambient temperature, humidity, altitude, and cold-start conditions separately from the server coolant inlet temperature.
Define redundancy, controls, and acceptance tests
When the scope is approved, send your project inputs for a quotation.
If the project calls for N+1 redundancy, identify the exact pumps, CDU components, controls, and heat-rejection equipment covered. State the expected operation during maintenance or a component failure. Commissioning should include pressure and leak tests, flushing and fluid verification, flow balancing, alarm checks, control failover, and integrated testing under an agreed load.
GB300 container project questions
Is a GB300 liquid-cooled container a ready-to-run product?
Treat a proposal as a project reference until the final bill of materials, site conditions, interfaces, and acceptance criteria are approved. Confirm whether servers, UPS or battery storage, network equipment, and external heat-rejection equipment are included.
How does liquid cooling reject heat in a container?
A typical design transfers heat from server cold plates into a secondary coolant loop, across a CDU heat exchanger, then through a primary loop to an outdoor dry cooler. The exact topology and fluid are project-specific.
What should be confirmed before specifying cooling capacity?
Agree on the number and type of IT racks, maximum and typical rack loads, server inlet conditions, flow and pressure limits, ambient design conditions, and the operating margin. Use one approved load schedule across the cooling and power calculations.
Does a 40-foot container automatically include UPS?
No. Container size does not define electrical scope. State explicitly whether UPS, batteries, switchgear, distribution, generators, servers, and commissioning are included or excluded.
Continue with the cold plate, CDU, and dry cooler guide and the PUE measurement checklist. Browse liquid-cooling products or send a project inquiry with your load schedule and site details.