Colocation Power Requirements: How to Size kW Without Guessing

Colocation power requirements: the short answer

Colocation power is usually sold as a committed kilowatt (kW) allocation to a cabinet, cage, or suite—not as unlimited outlet capacity. Size the requirement from equipment draw, redundancy design, growth planning, and the cooling approach at the target density. Undersizing can create change orders and schedule risk; oversizing can leave you paying for an allocation you cannot use. The best quote starts with a documented load model rather than a cabinet count alone.

Why power is often the gating resource

A facility may have physical rack space while lacking the electrical or cooling capacity needed for your deployment. Power availability can vary by room, phase, circuit design, and expansion plan. That is why a provider will usually want your market, required kW, redundancy expectations, density, and move-in window before confirming a product.

Treat power as a design input and a commercial term. Ask whether the quoted number is allocated, metered, committed, or subject to a true-up. Confirm the usable load, circuit voltage and amperage, PDU responsibilities, and the consequences of exceeding the committed amount. Also ask what happens if you need more power later: an upgrade may depend on stranded capacity, electrical work, cooling, and an available construction slot.

A practical method to estimate kW

1. Inventory the equipment

List servers, storage, switches, firewalls, appliances, and any special devices. Record rack units, quantity, power supplies, nameplate information, and the expected operating profile. Include equipment that will arrive during the initial phase, not only what is already installed.

2. Prefer measured draw when possible

Nameplate ratings help with a safe design envelope, but measured draw from a comparable workload can produce a better planning estimate. Capture normal and peak behavior if your systems vary materially. If the equipment is new, document the vendor’s expected draw and the assumptions behind it.

3. Add network and storage overhead

Network, storage, management, and security equipment can be easy to omit when a team estimates by server count. Include the complete IT load that will be connected to the cabinet or suite. Keep the equipment estimate separate from facility overhead so the provider can explain how its allocation and efficiency model work.

4. Decide on redundancy

Determine whether production equipment uses one cord, dual cords, or A/B feeds. Dual-cord equipment can draw from separate paths, but the design still needs to account for circuit capacity, balancing, maintenance, and failure scenarios. A redundant architecture does not mean you can ignore the load on either path.

5. Plan for growth without inventing precision

State the equipment you expect to add, the likely timing, and whether growth is a firm requirement or a scenario. A qualitative buffer is more useful than a made-up percentage. Ask the provider how additional kW is reserved, priced, delivered, and tested.

6. Validate cooling and density

Electrical capacity alone does not make a rack deployable. Confirm that the room, containment, airflow, floor loading, and cooling method support the expected density. GPU and other high-density environments may need a purpose-ready design or liquid-cooling support. See High-Density and AI Colocation for a validation worksheet.

To turn that estimate into space and growth headroom, see our guide to colocation capacity planning.

To turn kW into a rack count, see how many colocation racks you need.

Density bands as planning language

Buyers often describe loads as lower-density traditional racks, mid-density enterprise racks, or high-density/GPU racks. These labels are useful for opening a conversation, but they are not guarantees. The same kW figure can have different implications depending on rack layout, airflow, redundancy, equipment generation, and cooling method.

Give the provider kW per rack, total rack count, peak and expected operating draw, and the cooling preference. Ask which parts of the proposed design are available now versus on a future roadmap. For a high-density request, validate branch circuits, busway, containment, liquid distribution, CDU ownership, and thermal service commitments.

What providers need to quote power

A complete request should include:

• Target market or markets, such as Ashburn, Hillsboro, or Phoenix.
• Immediate kW per cabinet or suite and total initial kW.
• Planned expansion, with timing and whether it must be reserved.
• Single-feed or A/B redundancy expectations.
• Equipment type, rack density, floor-loading concerns, and cooling method.
• Carrier, cloud, and cross-connect needs.
• Physical access, remote-hands, security, and compliance requirements.
• Required delivery and go-live window.

This information lets providers distinguish a standard product from a custom design and identify schedule dependencies early.

Costs and terms beyond the kW number

A quote can include cross-connects, remote hands, installation, PDUs, circuit changes, metering, and other one-time or recurring services. The power term should explain allocation versus measurement, billing intervals, overage, true-up, maintenance treatment, and upgrade rights. Do not compare two kW figures without comparing what each provider includes and what the buyer must supply.

For a broader commercial framework, review the colocation pricing guide. Do not rely on generic price tables: current terms depend on market, site, density, redundancy, and contract structure. Request a quote that reflects your actual load and timeline.

Mistakes that delay deployments

Common avoidable problems include asking for “a few cabinets” without stating kW, ignoring dual-cord ampacity, treating nameplate maximum as operating draw without explaining the assumption, and assuming every site can cool GPU racks. Other risks include omitting network and storage load, failing to reserve expansion, and leaving the power demarcation unclear in the order form.

Use the colocation RFP checklist to turn these questions into a comparable request. Then verify the accepted load, circuit design, testing, and upgrade path before shipping equipment.

Frequently Asked Questions