Hardware Plan
What are you deploying?
We’ll review your GPU or server platform, rack count, equipment specifications, procurement status, and workload requirements.
COLOCATION DELIVERY MODELS
Choose How Much We Build.
Deploy on the same RWS infrastructure with the level of facility support that fits your team. Start with powered land, add critical facility systems, or choose a fully integrated environment ready for your GPU hardware.
Every responsibility is defined before deployment, giving both teams a clear scope from site preparation through production handoff.
Four Ways to Deploy
One Platform. Four Levels of Delivery.
Choose the model that matches your engineering resources, infrastructure ownership strategy, deployment schedule, and operating requirements.
01/ Powered Land
Bare
Shell
RWS provides the site, building shell, utility power, and fiber. You supply distribution, cooling, racks, networking, and IT.
More tenant scope02/ Ready for Fit-Out
Powered
Shell
RWS adds conditioned white space. You supply backup systems, cooling infrastructure, racks, networking, and IT.
Compare scope03/ Cooling and Resiliency
Powered
Shell+
RWS adds the cooling plant, backup generation, fuel systems, and meet-me-room infrastructure. You supply racks, networking, and IT.
Compare scope Most popular04/ Ready for First Token
Turnkey
Modular
RWS delivers a racked, cooled, connected, tested, and commissioned environment. You bring the GPU systems and workloads.
More RWS scopeMore customer-managed infrastructure More RWS-managed infrastructure
Scope and Demarcation
Know Who Provides Every System.
Infrastructure projects slow down when responsibilities are unclear. RWS defines the delivery boundary before work begins, including who provides, installs, tests, commissions, and operates each system.
| System | Bare Shell | Powered Shell | Powered Shell+ | Turnkey Modular |
|---|---|---|---|---|
| Building shell and structure | RWS | RWS | RWS | RWS |
| Utility power and site distribution | RWS | RWS | RWS | RWS |
| Fiber and meet-me-room access | RWS | RWS | RWS | RWS |
| Conditioned white space | Customer | RWS | RWS | RWS |
| Backup generation and fuel systems | Customer | Customer | RWS | RWS |
| Central cooling plant and capacity | Customer | Customer | RWS | RWS |
| UPS, PDUs, and rack-level power | Customer | Customer | RWS | RWS |
| Racks, CDUs, network, and commissioning | Customer | Customer | Customer | RWS |
| GPUs, servers, and workloads | Customer | Customer | Customer | Customer |
Qualification noteThe table describes the standard delivery boundary. Final scope, system ownership, performance requirements, and acceptance criteria are established for each project during engineering and contracting.
Technical Qualification
What We’ll Validate Together
The delivery models define the standard responsibility boundaries. Your hardware, site, density, cooling, network, and schedule determine the final deployment scope.
Power and Cooling
What does the environment require?
We’ll validate total IT load, rack density, electrical interfaces, resiliency requirements, heat load, and cooling approach.
Site and Network
Where should it run?
We’ll match the deployment to available site capacity, fiber and carrier options, latency requirements, logistics, and regional expansion plans.
Schedule and Scope
When does it need to be operational?
We’ll establish the delivery model, responsibility boundaries, engineering requirements, commissioning plan, target schedule, and acceptance criteria.
Plan Your Deployment
Ready to Define the Deployment?
Bring us your infrastructure requirements. We’ll help identify the right site, delivery model, responsibilities, and path to production.