Colocation is one of those old-school IT terms that still matters.
Cloud changed how businesses buy technology, but it did not eliminate the need for physical infrastructure. Servers still run somewhere. Data still lives somewhere. Networks still connect somewhere. Power, cooling, security, and uptime still matter.
Colocation, often shortened to colo, is a data center service where a business rents space for its own IT equipment inside a third-party facility.
In plain English:
Colocation lets a business put its servers, storage, and networking equipment inside a professional data center without owning the entire building.
The business usually owns or controls the hardware. The colocation provider supplies the facility, power, cooling, physical security, network access, and operational environment.
What Is Colocation?
Colocation is when a company places its own IT equipment in a third-party data center instead of keeping that equipment in an office, closet, basement, or private server room.
The company may bring:
- Servers
- Storage systems
- Firewalls
- Network switches
- Backup appliances
- Tape libraries
- Private cloud hardware
- Disaster recovery equipment
The colocation provider supplies the building and infrastructure around that equipment.
That usually includes:
- Rack space
- Power
- Cooling
- Internet and carrier access
- Physical security
- Fire suppression
- Redundant systems
- Remote hands support
- Monitoring
- Facility access controls
Colocation is not the same as public cloud. With cloud, a provider usually owns the underlying hardware and sells computing resources as a service. With colocation, the customer often owns or controls the hardware and rents the professional data center environment.
Colocation in Plain English
Think of colocation as renting a secure, professionally managed home for your IT equipment.
You bring the equipment.
The data center provides the space, power, cooling, connectivity, and security needed to keep it running.
It is like the difference between parking a valuable car in your driveway and parking it in a secure, climate-controlled garage with cameras, controlled access, backup power, and mechanics nearby.
For IT equipment, that environment matters.
Servers are sensitive. They need steady power, proper cooling, controlled access, network connectivity, and protection from physical risks.
That is what colocation provides.
Why Businesses Use Colocation
Businesses use colocation for several reasons.
Some want more control than public cloud gives them. Others have legacy systems that are difficult to move. Some need predictable infrastructure costs. Others want a secondary location for disaster recovery or backup.
Colocation can be useful when a business needs:
- More physical security than an office server room
- Better uptime than a local office environment
- Control over hardware
- Predictable infrastructure
- Access to multiple network carriers
- A place for backup or disaster recovery systems
- A private cloud environment
- Hybrid cloud connectivity
- Compliance-friendly infrastructure
- Geographic separation from the main office
Colocation is not just for huge enterprises. It can also make sense for mid-sized businesses, SaaS companies, law firms, healthcare organizations, financial firms, manufacturers, schools, local governments, and companies with specialized infrastructure needs.
What Is a Data Center Rack?
A rack is a standardized metal frame used to hold IT equipment.
Servers, storage arrays, switches, firewalls, patch panels, and other devices are mounted into racks so they can be organized, powered, cooled, and connected properly.
Most data center racks are based on a standard equipment width of 19 inches.
When a business buys colocation, it may rent:
- A full rack
- A half rack
- A quarter rack
- A single cabinet
- A private cage
- A custom footprint
A full rack gives more space, but it also requires more planning around power, cooling, cabling, and equipment layout.
What Is a U?
A U, or rack unit, is a standard measurement of vertical space inside a data center rack.
One U equals 1.75 inches of height.
So when equipment is described as 1U, 2U, or 4U, that tells you how much vertical rack space it takes.
Examples:
| Equipment Type | Common Rack Size |
|---|---|
| Network switch | 1U |
| Firewall | 1U |
| Thin server | 1U |
| Larger server | 2U |
| Storage array | 2U to 4U or more |
| Tape library | Varies widely |
A standard full-height rack is often 42U, although some data centers use taller racks.
That does not mean a business can automatically install 42 separate pieces of equipment. Some equipment takes more than 1U. Some space may be needed for cabling, airflow, patch panels, or future expansion.
Simple Rack Space Example
Imagine a business rents part of a rack and wants to install:
| Equipment | Rack Space |
|---|---|
| Firewall | 1U |
| Network switch | 1U |
| Server 1 | 2U |
| Server 2 | 2U |
| Backup appliance | 2U |
| Storage array | 4U |
| Patch panel | 1U |
That setup already uses 13U before accounting for cable management, airflow needs, or future growth.
This is why rack planning matters.
A business should not only ask, “How many servers do we have?”
It should also ask:
How much physical space, power, cooling, cabling, and growth capacity will this environment require?
Colocation Is Not Just About Space
One of the biggest mistakes beginners make is thinking colocation is only about renting rack space.
Rack space matters, but it is only one part of the decision.
A business also needs to understand:
- Power
- Cooling
- Connectivity
- Redundancy
- Security
- Access
- Support
- Contract terms
- Compliance needs
- Expansion options
The rack is the visible part.
The real value is the facility around it.
Power: The Most Important Thing Beginners Miss
In colocation, power can matter as much as space.
A business might physically fit equipment into a rack, but that does not mean the rack has enough power to run everything safely.
Colocation power may be priced or described by:
- Amps
- Kilowatts
- Circuits
- A-side and B-side power
- Metered power
- Committed power
- Redundant power feeds
For example, a customer may rent a rack with a specific power allocation. If the equipment needs more power than the rack provides, the business may need a different design, a different contract, or more expensive infrastructure.
In plain English:
You do not just rent space in a data center. You rent power.
That matters because modern equipment can be power-hungry. Storage systems, dense virtualization environments, and GPU servers can consume significant power and create significant heat.
A-Side and B-Side Power
Many data center environments use redundant power paths.
You may hear people talk about A-side power and B-side power.
This usually means equipment can be connected to two separate power feeds. If one side has a problem, the other side may continue supplying power.
This requires compatible equipment, proper cabling, and thoughtful design.
Not every device has dual power supplies. Not every customer needs the same level of redundancy. But for mission-critical systems, redundant power can be an important part of the colocation decision.
Cooling: Why Heat Matters
Servers generate heat. Storage generates heat. Network equipment generates heat.
If that heat is not managed properly, equipment can fail.
Data centers are designed to remove heat using cooling systems, airflow management, hot aisle and cold aisle layouts, containment, and other facility design practices.
Power and cooling are connected.
The more power equipment uses, the more heat it typically produces.
This is especially important for:
- Dense server environments
- Virtualization clusters
- Storage-heavy workloads
- Private cloud environments
- AI and GPU infrastructure
- Backup and archive systems
A business should not only ask whether equipment fits in the rack.
It should ask whether the data center can power and cool that equipment reliably.
Connectivity: How Your Equipment Connects to the World
Colocation also provides access to network connectivity.
This may include:
- Internet access
- Private network circuits
- Cloud connectivity
- Telecom carriers
- Fiber connections
- Cross-connects
- Interconnection with partners or vendors
Some colocation facilities are carrier-neutral, which means multiple network providers operate in the building. That gives customers more choice and flexibility.
Carrier-neutral facilities can be valuable because the business is not locked into only one connectivity provider.
What Is a Cross-Connect?
A cross-connect is a physical connection between your equipment and another network, carrier, cloud provider, or customer inside the data center.
In plain English:
A cross-connect is how your rack connects to something else inside the facility.
Cross-connects can be used for:
- Internet service
- Private circuits
- Cloud on-ramps
- Low-latency connectivity
- Disaster recovery replication
- Hybrid cloud networking
- Connecting to partners or service providers
Cross-connect costs matter. Some facilities charge setup fees and monthly recurring fees for cross-connects.
A low-cost rack can become more expensive if connectivity fees are high.
Colocation vs. Cloud
Colocation and cloud are related, but they are not the same.
With cloud, a business rents computing resources from a cloud provider. The provider owns and manages the underlying infrastructure.
With colocation, a business usually owns or controls its own hardware and rents the data center environment where that hardware lives.
| Category | Colocation | Cloud |
|---|---|---|
| Hardware ownership | Customer often owns hardware | Provider owns hardware |
| Control | More hardware-level control | Less physical control |
| Scaling | Requires hardware planning | Easier to scale quickly |
| Pricing | Space, power, bandwidth, services | Usage-based or subscription |
| Best for | Stable, controlled, specialized workloads | Flexible and elastic workloads |
| Responsibility | More customer responsibility | More provider abstraction |
The right answer is not always colocation or cloud.
For many businesses, the answer is both.
That is called a hybrid infrastructure strategy.
Colocation and Hybrid Cloud
Colocation can play an important role in hybrid cloud.
A business might use:
- Public cloud for applications
- Colocation for core infrastructure
- SaaS for business tools
- Cloud backup for fast recovery
- Tape or offline storage for long-term resilience
- Colocation for disaster recovery systems
This is why colocation is still relevant.
The cloud did not eliminate the data center. It changed how businesses think about where systems should live.
Some workloads belong in cloud.
Some belong in colocation.
Some belong in SaaS.
Some may still run on-premises.
The real question is not “cloud or colo?”
The better question is:
Where should each system live based on cost, control, performance, risk, and recovery needs?
Colocation and Disaster Recovery
Colocation can be useful for disaster recovery because it creates geographic and operational separation.
If a company keeps all systems in one office, it has a concentration risk. A fire, flood, power event, theft, ransomware attack, or local outage could create serious disruption.
A colocation facility can serve as:
- A secondary data center
- A disaster recovery site
- A backup replication target
- A private recovery environment
- A location for redundant infrastructure
- A place to host critical systems away from headquarters
This connects directly to business continuity.
If the main office is unavailable, the business may still have infrastructure running elsewhere.
Colocation and Backup Strategy
Colocation can also support backup and recovery planning.
A business may use colocation for:
- Backup servers
- Storage arrays
- Replication targets
- Tape libraries
- Immutable backup appliances
- Disaster recovery infrastructure
- Archive systems
This matters because backup is not the goal.
Recovery is the goal.
A business needs to know not only whether data is backed up, but also where it is stored, how it is protected, how quickly it can be restored, and whether the recovery environment is ready.
Colocation can be one piece of that strategy.
Colocation and Offsite Infrastructure
Colocation is also part of a broader offsite infrastructure conversation.
Businesses often need to separate critical systems and recovery copies from the main operating location.
That can include:
- Offsite tape vaulting
- Cloud backup
- Disaster recovery as a service
- Colocation
- Secondary data centers
- Immutable storage
- Air-gapped backup copies
The goal is not to chase technology for its own sake.
The goal is survivability.
If something bad happens, can the business keep operating or recover quickly enough?
Who Should Consider Colocation?
Colocation may make sense for businesses that need more control than cloud but more resilience than an office server room.
Examples include:
- Law firms with sensitive client data
- Healthcare organizations with compliance requirements
- Financial services firms
- SaaS companies
- Manufacturers
- Local governments
- School systems
- Media companies
- Insurance companies
- Companies with legacy applications
- Businesses with private cloud environments
- Organizations with predictable infrastructure needs
- Companies that need a disaster recovery site
Colocation is especially relevant when a business has equipment it wants to control but does not want to house in a weak physical environment.
When Colocation May Not Make Sense
Colocation is not right for every business.
It may not make sense if:
- The business has no need to own hardware
- Cloud services already meet the business need
- The company lacks IT staff or vendor support
- The workload changes constantly
- The business cannot manage hardware lifecycle planning
- The equipment footprint is too small to justify complexity
- The company needs simple SaaS tools, not infrastructure
Colocation gives control, but control comes with responsibility.
The business still needs to manage or support the hardware, operating systems, applications, backup design, patching, monitoring, and vendor relationships.
Questions to Ask Before Buying Colocation
Before signing a colocation agreement, a business should ask:
- How much rack space do we need?
- How much power do we need?
- Is power redundant?
- How is cooling handled?
- What network carriers are available?
- Is the facility carrier-neutral?
- What are the cross-connect fees?
- What remote hands services are available?
- What physical security controls are in place?
- What compliance certifications does the facility have?
- Can we visit the facility?
- What happens if we need more power later?
- What happens if we need more space later?
- What is included in the monthly cost?
- What costs extra?
- What is the contract term?
- What service levels are offered?
- How are outages communicated?
- Who can access our equipment?
- How are visitors authenticated?
- What happens when we need to remove equipment?
These questions matter because colocation is not just a technical decision.
It is a business risk decision.
Beginner Colocation Terms to Know
| Term | Meaning |
|---|---|
| Colocation | Renting data center space for your own IT equipment |
| Rack | A frame or cabinet that holds IT equipment |
| U / Rack Unit | A standard unit of vertical rack space equal to 1.75 inches |
| Full Rack | A full cabinet, often around 42U |
| Half Rack | A smaller portion of rack space |
| Cage | A physically separated private area inside a data center |
| Cross-Connect | A connection between your equipment and another carrier or network |
| Carrier-Neutral | A facility with access to multiple network providers |
| Remote Hands | Data center staff performing basic tasks on your equipment |
| A/B Power | Redundant power feeds for critical equipment |
| SLA | Service Level Agreement describing performance or uptime commitments |
The Business Case for Colocation
The business case for colocation usually comes down to five things:
1. Control
The business can own and configure its own hardware.
2. Resilience
The equipment sits in a professional data center instead of a vulnerable office environment.
3. Connectivity
The business can access carriers, private circuits, and cloud connections.
4. Security
The facility provides controlled physical access, cameras, monitoring, and professional security procedures.
5. Recovery
Colocation can support backup, disaster recovery, and business continuity planning.
That does not mean every business needs colocation.
But for the right use case, it can be a powerful infrastructure option.
Bottom Line
Colocation is not just renting space for servers.
It is renting access to a professional data center environment.
Racks and U’s are the starting point, but the real decision involves power, cooling, connectivity, security, redundancy, cost, and recovery planning.
For businesses that need control over infrastructure, colocation remains relevant.
The cloud changed IT, but it did not eliminate physical infrastructure.
Sometimes the smartest move is not putting everything in the cloud.
Sometimes the smartest move is putting the right systems in the right facility, with the right power, cooling, connectivity, security, and recovery plan.