A colocation data center is a facility where you rent space, power, cooling, and physical security for your own servers and networking hardware, rather than running them in your office or a cloud provider’s infrastructure. You bring the equipment (or lease it from the provider), and the colocation operator supplies the building, redundant power and cooling, high-speed internet connectivity, and 24/7 monitoring. In short, you own the hardware but rent the environment that keeps it running.
Background: Why Colocation Exists
Running servers in a typical office is inefficient. Standard office buildings lack the redundant power feeds, industrial cooling, and fire suppression that enterprise equipment needs. Power outages, overheating, and physical access by unauthorized people are constant risks. Colocation emerged in the 1990s as internet service providers and telecom companies began building specialized facilities to house their own equipment, then realized they could sell excess space to other businesses. Today, colocation is a middle ground between on-premises hosting and public cloud: you get the control of owning hardware without the burden of building and maintaining a data center yourself.
How Colocation Works
You typically rent space in one of three forms:
- Cage – a locked, wire-mesh enclosure that can hold several racks of equipment.
- Cabinet (rack) – a standard 19-inch server rack, usually 42U tall, shared with no one else.
- Suite – a private room with its own cooling and security, for large deployments.
You sign a contract that specifies the power allocation (measured in kilowatts per rack), bandwidth (in megabits or gigabits per second), and any cross-connect services to link your equipment to other carriers. You then ship or physically bring your servers, install them in the rack, and connect power and network cables. The colocation provider handles the facility—generators, UPS systems, HVAC, fire suppression, and physical access control. You typically manage the servers remotely via a management network or out-of-band console, since you won’t visit often.
Key Components of a Colocation Facility
A serious colocation provider invests heavily in infrastructure that most offices lack:
- Redundant power: Multiple utility feeds, diesel generators, and battery-backed UPS units that keep servers running through outages.
- Cooling: Precision CRAC (computer room air conditioning) units that maintain a stable temperature and humidity, often with hot-aisle/cold-aisle containment to improve efficiency.
- Network: High-speed connections to multiple internet backbones, plus meet-me rooms where you can cross-connect to carriers and cloud providers.
- Physical security: Biometric scanners, 24/7 guards, CCTV, and mantraps to prevent unauthorized access.
- Fire suppression: Clean-agent systems (like FM-200 or Novec) that extinguish fires without damaging electronics.
How to Choose a Colocation Provider
Not all colocation is equal. Evaluate providers on these factors:
- Location: Proximity to your team for maintenance visits, but also consider natural disaster risk (flood zones, earthquake faults, hurricane coasts).
- Power density: Can the facility deliver enough kilowatts per rack for your current and future hardware? High-density GPU servers need more than standard 1U servers.
- Connectivity: Does the facility have multiple carriers? Is there a meet-me room with access to major cloud providers (AWS, Azure, Google) for hybrid setups?
- Service level agreement (SLA): What uptime guarantee is offered (typically 99.9% to 99.99%)? What is the credit policy if they fail?
- Remote hands: Will staff reboot a server, replace a failed drive, or trace a cable for you, and at what cost?
- Compliance: Does the facility meet standards like SOC 2, HIPAA, or PCI DSS if your industry requires them?
Colocation vs. Cloud vs. On-Premises
Colocation is often compared to the two main alternatives:
- On-premises: You own everything, including the building, power, cooling, and IT staff. Maximum control, but high capital cost and no redundancy unless you build it.
- Public cloud (AWS, Azure, Google): You rent compute and storage on demand, paying per hour or per month. No hardware to manage, but less control over performance, and costs can escalate with sustained heavy usage.
- Colocation: You own the hardware (or lease it from the provider), so you control the exact specifications and security. You avoid the capital expense of building a data center, but you still pay a monthly fee for space and power.
Many organizations use a hybrid approach: run predictable, sensitive workloads in colocation, and use cloud for bursty or experimental work.
Costs of Colocation
Pricing varies widely by region and provider, but the main components are:
- Recurring monthly fee: Based on rack space (e.g., full rack, half rack) and power draw (e.g., $500–$2,000+ per month per rack, plus per-kW charges).
- Setup/installation: One-time fee for cabling, rack installation, and configuration.
- Bandwidth: Either included in the monthly fee or billed per Mbps of committed data rate.
- Cross-connects: Fee for each physical cable linking your rack to a carrier or cloud provider (often $50–$200 per month per connection).
- Remote hands: Per-incident charges for staff assistance (e.g., $50–$150 per half hour).
It is essential to read the contract for hidden fees: power overage charges, cancellation penalties, and minimum term lengths. Always calculate the total cost of ownership (TCO) over 3–5 years, including hardware depreciation, to compare against cloud pricing.
Common Problems and Misconceptions
Misconception: “Colocation is always cheaper than cloud.” Not necessarily. If your workloads are variable or short-lived, cloud can be cheaper because you pay only for what you use. Colocation makes sense for steady, resource-intensive workloads where hardware costs are amortized over years.
Problem: Power density limits. Older colocation facilities may only offer 2–5 kW per rack, which is insufficient for modern GPU servers that can draw 10–20 kW. Check the power capacity before signing.
Problem: Network congestion. A facility with poor carrier diversity can experience latency or packet loss during peak hours. Ask for a network map and test throughput before committing.
Problem: Vendor lock-in. Moving equipment out of a colocation facility is physically possible but time-consuming and expensive, especially if you have many racks. Negotiate exit terms in advance.
Safety and Security Considerations
Physical security is the primary safety concern. Choose a facility with multi-factor authentication, biometric access, and 24/7 monitoring. Also verify that the building meets local fire and building codes, and that fire suppression is appropriate for electronic equipment (water-based systems can destroy servers). For your own equipment, ensure proper rack mounting to prevent tipping, and use cable management to avoid overheating and accidental disconnects. Finally, always have a disaster recovery plan—even the best data center can go down, so keep backups off-site.
Frequently Asked Questions
What is the difference between colocation and a data center?
A data center is the physical building or room that houses servers. Colocation is a service model where a provider operates the data center and rents space to multiple customers. You can have a private data center (on-premises) or use a colocation facility; the term “data center” refers to the infrastructure, while “colocation” refers to the business arrangement.
Do I need my own IT staff for colocation?
Yes, for the servers themselves. You are responsible for installing, configuring, and maintaining your hardware. The colocation provider only maintains the facility. Many providers offer remote hands services for basic tasks like reboots or cable changes, but you still need someone to manage the operating system and applications.
Can I connect my colocation servers to the cloud?
Yes, most colocation facilities have direct connections to major cloud providers via cross-connects or dedicated links. This allows you to create a hybrid architecture where some workloads run on your hardware and others in the cloud, with low latency between them.
How much power do I need per rack?
It depends on your equipment. A typical 1U server draws 100–300 watts, so a rack with 20 servers might need 2–6 kW. High-density GPU servers can draw 1–2 kW each, requiring 10–20 kW per rack. Check your equipment specifications and add a safety margin of 20–30% for future growth.
What happens if the colocation facility has a power outage?
Reputable facilities have UPS batteries that provide instant backup, followed by diesel generators that can run for days. If the outage exceeds generator fuel capacity, the facility may shut down, so always ask about fuel contracts and testing procedures. Your servers should be configured to shut down gracefully if power is lost for an extended period.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.
More cards in this drawer
- Samsung Unpacked August 5: 5 Devices Teased?
- Google Workspace Accounts Created Bypassing?
- Recover Deleted Screenshots on Mac: Full Guide
- Go vs Node.js: Cloudflare API Request Data
- ROG Phone 3 Certified Specs Leak: What’s Confirmed
- Wi-Fi QR Code: Make One Guests Can Scan