What Is Colocation? A Plain-English Guide for Buyers

What is colocation?

Colocation (colo) means placing your own servers and network gear in a third-party data center that supplies power, cooling, physical security, and connectivity. You keep control of the hardware and operating systems; the facility operator runs the building systems. Buyers use colocation to obtain enterprise infrastructure without building and staffing a private data center.

For a commercial buyer, the practical question is not only “what does colo mean?” It is whether a facility can provide the right footprint, power allocation, connectivity, access model, and contract terms for the workload you need to place. A good evaluation turns your equipment list, target market, redundancy requirements, and move-in date into comparable quotes.

Colocation in one paragraph

A colo provider rents space in a facility that is designed for IT equipment. Your deployment may occupy a few rack units, a full cabinet, a private cage, or a dedicated suite. The provider operates the critical environment around that space: electrical distribution, UPS and generator systems, cooling, fire and life-safety systems, building security, and facility operations. Connectivity may be available through carriers, internet exchanges, cloud on-ramps, or other tenants using cross-connects.

You still own or lease the servers, storage, switches, firewalls, and software running inside your footprint. You are responsible for configuring and maintaining that equipment, protecting your applications, and defining your own network and backup architecture. This shared-responsibility model is important: colocation is not automatically managed hosting or a turnkey IT service.

What the facility provides—and what you manage

A facility commonly provides the following building and site services:

• A cabinet, cage, suite, or other contracted footprint.
• A defined power allocation and the electrical path serving it.
• Cooling and environmental monitoring appropriate to the product and site design.
• Physical security, access controls, visitor procedures, and escort rules.
• Connectivity options, carrier access, and cross-connect ordering processes.
• Remote-hands or on-site technician services, if selected and within scope.
• Facility certifications or compliance attestations, where offered.

You generally manage the equipment and workload inside the footprint. That includes servers, storage, operating systems, applications, network configuration, data protection, patching, and the parts of compliance that apply to your organization and system. A provider’s facility certification does not automatically certify your application or operating practices.

Before comparing proposals, ask exactly where the demarcation sits. Confirm who installs power whips, who supplies PDUs, who orders a cross-connect, who responds to an alarm, and who is authorized to touch equipment. These details can affect schedule and total cost even when two quotes appear to offer the same number of cabinets.

Common colo footprints

Partial cabinet or rack units. A small deployment may need only a few rack units. Confirm available power, physical separation, cable management, and whether the product supports your security and access requirements.

Full cabinet. A full cabinet provides a defined vertical footprint and a power allocation. Do not size it by rack space alone: equipment draw, dual-cord requirements, circuit design, and cooling capability determine whether the cabinet is a workable home for the load.

Cage or private suite. A cage adds a controlled area around cabinets, while a private suite can provide more dedicated space and design control. These footprints may fit organizations that need restricted access, phased growth, custom layout, or higher-density infrastructure.

For power planning, see Colocation Power Requirements. For larger footprints and fit-out responsibility, compare Wholesale vs. Retail Colocation.

Before you pick a footprint, plan capacity and growth.

For a side-by-side view of the options, see cabinet vs cage vs private suite.

Who colocation is for—and who it is not

Colocation can fit a buyer with predictable hardware requirements, control or regulatory needs, a hybrid architecture, a disaster-recovery site, or a desire to select carriers and cloud connections. It can also fit a team that wants to keep physical hardware while avoiding ownership of the building, generators, cooling plant, and security operation.

Colocation may be a poor fit for a workload that is entirely ephemeral and has no hardware requirement, or for a small team that does not want to own physical lifecycle work. Cloud, managed hosting, or another service may be better for those needs. Many organizations use a combination: physical infrastructure in colo for control and steady workloads, with cloud services for elasticity or specialized services. See Colocation vs. Cloud when comparing operating models.

If you are planning a secondary site, see how to choose a disaster-recovery colocation site.

First-time buyers should also read about common first-time colocation buyer mistakes.

How colo pricing usually works

Most proposals separate space and power from optional services. Common line items include the footprint, committed or metered power, cross-connects, bandwidth or carrier services, remote hands, installation, and access-related services. The order form should explain what is included, how power is measured, how overage or true-up works, and which services have recurring or one-time charges.

There is no universal price that applies to every market or deployment. Capacity, density, redundancy, term, fit-out, and connectivity all change the commercial picture. Compare the complete quote and the service obligations rather than relying on a single line item. Use the colocation pricing guide as a framework, then request current quotes.

How to start evaluating colo

Prepare a short requirements brief before contacting providers:

1. Identify the market and the latency or geographic requirements.
2. List equipment, rack units, current draw, and expected growth.
3. State whether production needs single or dual power feeds and what failure domains matter.
4. List carriers, cloud on-ramps, internet exchanges, and cross-connect destinations.
5. Identify physical access, compliance, security, and remote-hands requirements.
6. Give a target move-in window and any phased deployment dates.

Use those requirements to compare facilities in Phoenix, Dallas, and Chicago, then extend the search to other markets when latency or capacity requires it. The colocation RFP checklist can help structure the questions. When you are ready to compare options, get started and share your market, power, and timeline.

Frequently Asked Questions