Sizing a colocation cabinet is a decision most businesses end up making more than once. The first time arrives with the move itself, and there's no single path to it: some businesses are coming off cloud or VPS hosting, some are pulling equipment out of an office server room that was never really built to hold it, some are graduating from rented dedicated servers to machines they own outright, and plenty start at a rack directly because the workload needs specific hardware or a compliance requirement rules out shared infrastructure.

After that it keeps returning. It comes up again at contract renewal, when a hardware refresh changes what the same rack units draw, and when growth forces a choice between adding a second cabinet and consolidating into a bigger one. The question is the same every time, and so are the two ways of getting it wrong.

The first is renting more rack than you need because it feels safer, then paying monthly for years of capacity that never gets used. The second is squeezing into a quarter rack that runs out of power six months in, forcing an unplanned move or a second cabinet in a different part of the facility.

Both come from the same gap: not knowing which of the two constraints that actually govern a cabinet will bind first, so you either over-buy to hedge the uncertainty or size on server count and get caught by power. This guide covers both of them, how they interact, and what to confirm with a provider before signing anything.

Rack space basics

Rack space is measured in rack units, written as U, where one U is 1.75 inches of vertical space. A standard full cabinet is typically 42U, though 45U and 47U cabinets exist and some facilities use taller ones.

Colocation is usually sold in fractions of that: a full rack, a half rack (around 20U), a quarter rack (around 10U), or individual U slots for very small deployments. The fractions aren't always exactly half or a quarter of the total, since shared cabinets need space for cable management and per-customer power distribution, so confirm the actual usable U count rather than assuming the arithmetic.

Sizing starts with an honest inventory. Count the U height of every device going in, including the things people forget: switches, firewalls, a patch panel, a KVM or console server, anything terminating your own address space, and the power distribution units themselves if they're rack-mounted rather than vertically mounted in the cabinet's rear channel. If you're speccing hardware rather than relocating equipment you already own, run the same count from the bill of materials you intend to buy, since U height and rated power are on every vendor's spec sheet. Then add a growth buffer for 12 to 24 months, which is a more useful horizon than five years, because hardware density and business requirements both change faster than that.

Power is usually the real constraint, not space

Here's the part that surprises people sizing their first cabinet, and still catches out plenty who have done it before: most contracts are priced and capped by power, and you can exhaust your power allocation with half the cabinet still empty.

A quarter rack might come with a 5 amp or 10 amp allocation at 208V or 230V, which works out to roughly 1 kW at the low end and a little over 2 kW at the high end, before any derating is applied. Five or six modern dual-socket 1U servers can reach that under load, which leaves you holding half an empty quarter rack you aren't allowed to fill. This is why "how many servers fit" is the wrong opening question and "how many watts am I allowed" is the right one.

Estimating draw starts with nameplate wattage, the rated maximum on each device's power supply label. Summing nameplates gives you a conservative ceiling, and actual draw is typically well below it, often in the range of 40 to 70 percent for general-purpose servers at normal utilization. The useful discipline is to size against realistic sustained draw while leaving headroom, rather than either summing nameplates (which overbuys) or assuming idle figures (which underbuys and trips breakers).

Circuit derating matters too, and it catches people out. Electrical code practice generally limits continuous load to 80 percent of a circuit's rated capacity, so a 20 amp circuit gives you about 16 amps of usable continuous draw. If a provider quotes you a 20 amp feed, plan around 16, and confirm whether their quoted figure is the breaker rating or the usable allocation.

How redundant power changes the math

Most colocation cabinets offer A and B power feeds from separate upstream paths, and devices with dual power supplies connect to both. Under normal operation each supply draws roughly half the device's load, and if one feed fails the other carries the whole thing.

This creates a billing question worth asking explicitly, because practices differ. Many providers bill on the higher of the two feeds rather than the sum, on the reasoning that you're paying for the capacity you can actually use continuously. Others bill total provisioned capacity across both. The difference can be substantial on your monthly invoice, so get the answer in writing rather than inferring it.

The operational point matters just as much. Each feed needs to be able to carry your entire load alone, because that's the scenario redundancy exists for. If you're drawing 8 amps split across two 10 amp feeds you're fine, but if you're drawing 16 amps split across two 10 amp feeds you have no redundancy at all, just two feeds running at 80 percent, where losing one pushes the entire 16 amps onto the survivor and trips it too.

Cooling and airflow considerations

Power and cooling are related but not interchangeable. A facility can have power available for your cabinet and still not have the airflow to keep dense equipment in a safe temperature range.

Modern facilities use hot aisle and cold aisle arrangements, often with containment, and that design assumes equipment pulls cool air from the front and exhausts hot air to the rear. The temperature and humidity envelopes most facilities design against come from ASHRAE's datacom guidelines, which is useful context if a provider quotes you a supply air range. Getting the benefit requires your side of it: equipment oriented consistently, blanking panels in empty U slots so hot exhaust doesn't recirculate to the front intake, and cabling that doesn't obstruct rear airflow. Blanking panels in particular cost very little and materially improve intake temperatures.

It's also worth separating facility resilience from cooling capacity, since they're quoted together and mean different things. A facility's Uptime Institute Tier rating describes redundancy in power and cooling distribution, not how many kilowatts a single cabinet can shed.

Density is where this becomes a real conversation. A cabinet averaging 3 to 5 kW is unremarkable for most facilities. GPU hosts, dense compute, or heavily populated blade chassis can push a single cabinet well past that, and above roughly 10 to 15 kW you're in territory where the facility's per-cabinet cooling capacity needs explicit confirmation rather than assumption. Ask what they support per cabinet at your intended density, and whether higher-density cabinets are placed differently on the floor.

A practical sizing framework

Start by inventorying every device with both its U height and its nameplate wattage, including network gear and anything rack-mounted that isn't a server. Estimate realistic sustained draw rather than the nameplate sum, then add your 12 to 24 month growth buffer to both the space and power figures.

Next, translate that into the provider's units. Ask whether billing is driven by U space, power allocation, or both, and which one your configuration will hit first, because that's the number that determines what you're actually buying. Confirm whether a quoted amperage is breaker rating or usable continuous capacity, and how A and B feeds are billed.

Finally, confirm the fit on the physical details: usable U count in the specific cabinet fraction you're renting, cabinet depth against your deepest server, per-cabinet cooling capacity at your density, and what the upgrade path looks like if you outgrow the allocation. Those sit alongside the broader question of where the facility should be in the first place. A provider who can answer the upgrade question concretely, whether that's adding an amp allocation in place or moving to a larger footprint, is worth more than one who quotes a slightly lower price and leaves that open.

Re-sizing a cabinet you already have

The same two constraints govern every later decision, but the inputs shift in ways that catch people out. A hardware refresh is the clearest case: replacing older 2U servers with current 1U models can halve your rack space while raising draw per U, so you free up space you can't actually use and reach the power ceiling sooner than the U count suggests.

Renewal is the other moment that deserves a real recalculation rather than a rollover. Measure actual draw at the PDU across a normal week instead of reusing the estimate you built from spec sheets, because the gap between the two is usually wide. Running consistently well under your allocation is a negotiating position; sitting near the derated ceiling is a warning worth acting on before it becomes an incident.

Growth eventually forces a choice between adding a second cabinet and consolidating into a larger one. Two quarter racks in different parts of a facility cost more in cross-connects and cabling complexity than a single half rack, so if the provider can move you into contiguous space it's worth asking about that before defaulting to a second cabinet somewhere else on the floor.

Common mistakes to avoid

Renting a full rack "just in case" is the most common and the most expensive, because power allocation is billed whether or not you draw it. Starting smaller with a documented upgrade path almost always costs less over two years.

Underestimating power is the mirror error, and it's worse operationally than financially: hitting a hard cap mid-deployment means either an unplanned upgrade on the provider's timeline or splitting equipment across non-adjacent cabinets, which complicates cabling and cooling both.

Two smaller ones are worth naming. Forgetting derating means planning around a breaker number you can't continuously use. And treating a facility's headline power density as guaranteed availability for your specific cabinet, rather than a facility-wide capability that varies by location on the floor, leads to an unpleasant surprise at install time. Both are avoided by asking directly rather than reading the marketing page.

Wrapping up

Sizing a cabinet comes down to two numbers checked against each other: the U space your equipment occupies, and the sustained power it actually draws with derating and redundancy accounted for. Whichever one you hit first is your real constraint, and it's frequently power.

Get those two figures right, add a realistic 12 to 24 month buffer rather than a five-year guess, and confirm the billing model and cooling capacity before signing. That's most of the difference between a cabinet that serves you for years and one you're renegotiating in six months.

Thanks for reading! Whether you're sizing a first cabinet or resizing one you've had for years, xTom offers colocation alongside enterprise-grade dedicated servers, NVMe-powered KVM VPS through V.PS, IP transit, shared hosting, and general IT services for whatever else your infrastructure needs.

Ready to discuss your infrastructure needs? Contact our team to explore the right solution for your projects.

Frequently asked questions about colocation sizing

How do I know if I need a quarter rack or a half rack?

Work out both your U requirement and your sustained power draw, add a 12 to 24 month buffer, and see which constraint you hit first. If your equipment fits comfortably in 10U but draws more than a quarter rack's power allocation, the power figure is what decides it.

Is power capacity usually the limiting factor before rack space runs out?

Frequently, yes, particularly with modern dual-socket servers. It's common to exhaust a power allocation with half the cabinet still physically empty, which is why sizing on server count alone tends to mislead.

What's the difference between nameplate power draw and real-world draw?

Nameplate is the maximum the power supply is rated for, while actual sustained draw for a general-purpose server often lands somewhere around 40 to 70 percent of that under normal load. Size against realistic sustained draw with headroom rather than either extreme.

Does redundant A+B power double my available capacity?

No, and treating it that way removes the redundancy you're paying for. Each feed needs to be able to carry your full load alone, so your usable capacity is effectively one feed's worth. Billing practice varies between the higher feed and the combined total, so confirm it with the provider.

What is circuit derating and why does it matter?

Continuous load is generally limited to 80 percent of a circuit's rating, so a 20 amp circuit supports about 16 amps sustained. Planning against the breaker number rather than the derated number is a common way to end up tripping circuits under normal operation.

Should I recalculate when renewing an existing colocation contract?

Yes, rather than rolling over the same allocation by default. Measure actual draw at the PDU over a normal week, since a hardware refresh can change your power profile substantially even when the U count stays the same, and the measured figure is usually well below the estimate you originally sized against.

How much growth buffer should I plan for?

Twelve to 24 months is the practical range. Beyond that you're usually paying for capacity that will be filled by hardware you haven't specified yet, and hardware density changes enough that a five-year projection rarely holds.