Skip to main content
Support
0
Contact us
Nederlands
Deutsch
Español
Dedicated serversFlexible VPSCloud TechnologyColocationChallenges in ITSectorsCareers
Cloud Compute

With Cloud Compute, you have access anytime and anywhere to a portal through which you can configure your entire IT environment from wherever you are in the world.

Cloud Storage

Reliable access to your files, infrastructure, and applications at all times – with no interruptions or delays. At Worldstream, we offer a variety of storage solutions.

Flexible cloud icon
Flexible cloud
Private cloud icon
Private cloud
Bare metal icon
Bare Metal Compute
Hollow cube icon
Object storage
Hollow cube icon
File storage
Block storage icon
Block storage
Backup storage icon
Backup storage
Need support?

With experienced engineers and an average response time track record on 7 minutes, you can expect a solid technical support solution in next to no time.

All Servers

Choose your Dedicated Server now. Custom or Instant Delivery. Powerhouse servers built for your use case.

Use Cases

Whatever your use case, we’re here to help you find the ideal solution.

Deal servers icon
Deals
AMD servers icon
AMD Processors
AI servers icon
Intel Processors
Hollow cube icon
Virtualisation, Containerisation and Orchestration
Hollow cube icon
Websites and Applications
Hollow cube icon
Gaming and Streaming Infrastructure

24/7/365 support with an average response time of just 7 minutes. Thanks to our own data centers, our engineers can go directly to your server for fast, hands-on assistance. Email or call us anytime.

Smart outsourcing

Some IT creates added value, while other types are supportive. Use that as a starting point for outsourcing.

Cost Efficiency

Complete IT packages may seem like the safe option, but when you consider the costs, other choices often make more sense.

IT flexibility & control

Outsourcing doesn’t mean losing control; it actually provides more flexibility and control.

Cloud repatriation

The cloud is not a final destination: You should continuously evaluate and adjust your cloud environment as needs evolve.

Financial services
Logistics & Transportation
Retail & E-commerce
Media & Entertainment
Tech & Software Development
Security
Managed Service Providers
Need support?

With experienced engineers and an average response time track record on 7 minutes, you can expect a solid technical support solution in next to no time.

Chat with usContact us
About WorldstreamAbout the technologyCasesKnowledge base
About usMeet the teamJobsBecome a resellerCertificationsOur data centersOur networkDDoS ProtectionAMD EPYC serversTechnology PartnersOperating SystemsAll casesEasyTerraDutch Drone CompanyPerfGridArticlesFAQNews and BlogsProducts and Services
Contact us

Call +31 (0) 174 – 712 117

Industriestraat 53, Naaldwijk

Nederlands
Deutsch
Español
0
Dedicated serversFlexible VPSCloud TechnologyColocationChallenges in ITSectorsCareersAbout WorldstreamAbout the technologyCasesKnowledge baseMy Worldstream
Contact
Support
NederlandsDeutschEspañol
  1. HomeHome
  2. Knowledge Base
  3. Colocation
  4. Budgeting rack power for colocation

Budgeting rack power for colocation

Applies to ColocationAudience Server administrators, buyersLast reviewed September 2026

Quick answer

Add up the rated power draw of every device you plan to rack, then plan for meaningfully less than that total on each power feed, both because equipment rarely runs at its rated maximum and because a redundant A/B feed setup is only truly redundant if either feed alone can carry the full load if the other fails.

On this page
  • Step 1: sum the nameplate power of every device
  • Step 2: apply headroom, don't plan to the theoretical maximum
  • Step 3: understand what redundant feeds actually protect against
  • How this maps to what Worldstream publishes
  • A worked approach, in outline

Getting rack power right before you order colocation space avoids two expensive surprises: ordering more capacity than you need, or discovering mid-deployment that your equipment doesn't fit within what a rack, or a single power feed, can actually deliver. The methodology below is standard datacentre practice, not specific to any one provider, and it's worth working through before committing to a rack size or power allocation.

Step 1: sum the nameplate power of every device

Every piece of rack equipment, a server, a switch, a storage array, carries a nameplate or rated power figure, usually printed on the chassis or listed in its datasheet, expressed in watts or as a maximum amperage at a given voltage. Start by listing every device you plan to install and its rated draw, then sum them. This total is your starting point, not your final budget, it represents the theoretical ceiling, not what the equipment will actually draw under normal operation.

Step 2: apply headroom, don't plan to the theoretical maximum

Real-world power draw is almost always lower than the nameplate figure, nameplate ratings are typically set conservatively, well above what a device draws under normal, even heavy, load. But planning exactly to nameplate sum leaves no room for peak load, added equipment later, or measurement error, and running infrastructure consistently near its rated maximum leaves no margin for the unexpected. A common approach is to budget with meaningful headroom below the summed nameplate total, rather than treating that sum as the target to fill. Exactly how much headroom to build in depends on how variable your workload's power draw is and how much future growth you want to leave room for, so treat this as a planning principle to apply deliberately, not a fixed formula.

Step 3: understand what redundant feeds actually protect against

A rack fed by two independent power paths, commonly labelled A and B, is only meaningfully redundant if either feed alone can carry the full load on its own. If your actual draw is split evenly across both feeds but adds up to more than either feed can handle by itself, a failure on one feed doesn't gracefully halve your capacity, it overloads the surviving feed and risks taking the whole rack down at the worst possible moment, exactly when you needed the redundancy to work. The budgeting rule that follows from this: keep your total draw within what a single feed can carry alone, even though you're drawing from both. Dual power supplies on your own equipment, plugged one into each feed, are what let this actually work in practice, without dual supplies on the equipment itself, a feed failure means an outage regardless of how the rack is wired.

How this maps to what Worldstream publishes

Worldstream's colocation facilities run on N+1 redundancy with dual power feeds and support up to 10kW of power per rack as an available density option, details already covered in Power, cooling and rack density at Worldstream's data centres. The 10kW figure describes what a rack can be provisioned for, it isn't a target to fill, the same headroom-and-single-feed-capacity reasoning above applies to it directly. Facility-level efficiency, expressed as a PUE of around 1.15, is a useful conceptual reference too: it's a reminder that the power a facility draws to run your rack is somewhat higher than what your equipment itself consumes, cooling and distribution overhead account for the difference, though PUE describes the facility as a whole rather than any single rack.

A worked approach, in outline

  1. List every device going in the rack with its rated power draw, and sum them.
  2. Apply headroom below that sum to arrive at a realistic planning figure, rather than budgeting to the theoretical maximum.
  3. Check that planning figure against what a single feed can carry alone, not the combined capacity of both feeds, since that's what stays available if one feed fails.
  4. Confirm your equipment actually has dual power supplies wired one to each feed, otherwise the redundancy the facility provides doesn't reach your hardware.
  5. Leave room in the plan for equipment you'll add later, rather than sizing exactly to what you're racking on day one.

Related articles

  • Power, cooling and rack density at Worldstream's data centres
  • Colocation vs. dedicated servers vs. cloud: which fits your workload
  • Connecting your colocated hardware to AWS, Azure or GCP
  • Colocation overview
Was this article helpful?

Solid IT. No Surprises

Sparring partner for IT maturity
Eliminating barriers so you can run
Predictable and transparant costs

Contact

  • Industriestraat 53, Naaldwijk
  • Payment Methods
  • Abuse
  • Developers Resources
  • Network Operations Center
  • About us
  • Meet the team
  • Jobs
  • Become a reseller
  • Certifications
  • Our data centers
  • Our network
  • DDoS Protection
  • AMD EPYC servers
  • Technology Partners
  • Operating Systems
  • Overview
  • FAQ
  • Cases
  • News & Blogs
  • Use Cases
Nederlands
Deutsch
Español
Nederlands
Deutsch
Español
  • Legal
  • Disclosure