What Is Colocation?
Colocation ("colo") is renting space, power, cooling, and connectivity in a third-party data center to house your own servers and network equipment — you own the hardware, the provider runs the facility.
Who Owns What
The provider runs the facility
Building, power feeds, cooling, physical security, and connectivity.
You own the IT
Servers, storage, network gear, their configuration, and their operation.
Retail vs Wholesale Colocation
Retail colocation rents by the rack or cage and is billed on space and power draw — a fit for most enterprises. Wholesale colocation leases larger dedicated space or whole data halls with committed power, typically for hyperscalers and very large deployments.
What You Actually Rent — and What It Costs
A colocation contract bundles four things: space (a rack, part of a rack, or a locked cage), a committed power allowance delivered to that space over redundant feeds, the cooling to remove the heat that power becomes, and connectivity — carrier access plus cross-connects, the in-building fiber runs that link your equipment directly to ISPs, internet exchanges, cloud on-ramps, or other tenants. The provider backs the facility side with an SLA covering power availability, temperature and humidity ranges, and physical security.
Pricing follows the same structure. Retail deals are quoted per rack or per U with a power allowance included; larger footprints are quoted per kW of committed power, because power — not floor space — is what modern facilities actually run out of. Around the base rent sit one-time setup charges, a monthly fee per cross-connect, and hourly billing for remote hands: the provider's on-site technicians, who will power-cycle a machine or reseat a cable from your ticket but know nothing about what runs on it.
The part the contract does not cover is everything inside your rack. Server health, failing disks, firmware, temperatures at the component level, operating systems, and applications remain entirely your job — from a distance. That is why colo tenants lean on BMC-level monitoring and data center monitoring software that works agentlessly and out-of-band: if the OS hangs at 3 a.m., the management controller still answers, and your remote-hands ticket can say exactly which machine and which part.
Colocation vs Cloud vs On-Premises
| Dimension | On-Premises | Colocation | Cloud |
|---|---|---|---|
| Who owns the hardware | You | You | The provider |
| Who runs the facility | You | The provider | The provider |
| Upfront cost | Building, plant, and hardware | Hardware only | None |
| Scaling speed | Months — construction and fit-out | Weeks — order and rack hardware | Minutes |
| Cost profile | High fixed, low marginal | Predictable monthly rent plus hardware | Variable, usage-based |
| Hardware monitoring | Your job, on site | Your job, remotely | Provider's job, invisible to you |
These are not exclusive choices: a common pattern is steady workloads on owned hardware in colo, burst and experimental workloads in cloud, and a cross-connect between the two.
When Colocation Is the Right Call
Retiring the office server room
The building's power and cooling were never designed for IT. Moving racks into a colo buys real redundancy without a construction project.
Steady, predictable workloads
Workloads that run flat around the clock often cost less on owned hardware in colo than on equivalent cloud instances rented month after month.
Compliance and data control
When regulation or policy requires data on hardware you own and can physically account for, colo delivers that inside a professionally run facility.
Interconnection and latency
Carrier-dense facilities put you one cross-connect away from ISPs, exchanges, and cloud on-ramps — useful for hybrid architectures and latency-sensitive services.
Disaster recovery site
A few racks in a colo in another region gives you a DR footprint without building or staffing a second facility.
Cloud repatriation
Teams moving stable workloads back off the public cloud for cost reasons usually land in colo — ownership economics without facility ownership.
You Own the Hardware You Can't Walk Up To
In colo, your servers may be in another city or country. You still own their health, warranty, and configuration — but you can't see a blinking fault light or swap a part quickly. Remote hardware visibility and an out-of-band rescue path stop becoming nice-to-haves and become the way you operate.
Common Questions About Colocation
What is the difference between colocation and cloud?
In colocation you own the physical servers and rent the space, power, cooling, and connectivity around them. In cloud you rent virtual capacity on someone else's servers and never touch hardware at all. Colo gives you full control over the hardware stack and predictable costs for steady workloads; cloud gives you elasticity and zero hardware responsibility. Many organizations run both, connected by a cross-connect or private link.
What is a cross-connect in a colocation data center?
A cross-connect is a physical cable — usually fiber — run inside the facility between your equipment and another party's: a carrier, an internet exchange, a cloud on-ramp, or another tenant. Because the connection never leaves the building, it offers low latency and high reliability. Cross-connects are billed as a recurring monthly fee per connection, and access to a rich set of carriers and clouds is one of the main reasons to choose one facility over another.
What are remote hands?
Remote hands is the provider's on-site technician service, usually billed hourly. Technicians work from your ticket: power-cycle a server, reseat a cable, swap a labeled drive, read out what an indicator light shows. They do not know your operating systems or applications, so the quality of the outcome depends on the quality of your instructions — and on how precisely your own monitoring told you what is wrong before you opened the ticket.
How is colocation priced?
Retail colocation is typically priced per rack (or per U, half rack, or cage) with a committed power allowance, while larger deployments are increasingly priced per kW of committed power, because power — not floor space — is the binding constraint in modern facilities. On top of the base fee come one-time setup charges, monthly cross-connect fees, and hourly remote hands. Rates vary widely by market and facility tier, so comparisons only make sense on a total-cost basis.
Who monitors my equipment in a colocation facility?
You do. The provider monitors the building: power feeds, cooling plant, and physical security, backed by an SLA. Everything inside your rack — server health, disks, memory, temperatures, firmware, operating systems, applications — is your responsibility. That is why colo tenants rely on out-of-band monitoring through BMC interfaces such as IPMI, Redfish, iDRAC, and iLO: it keeps hardware visible and controllable even when the OS is down and nobody is on site.
Operate colo hardware as if you were on site
Sensaka gives remote hardware visibility and out-of-band control across colocation and edge sites, so distance stops being a blind spot.