Choosing a colocation data center starts with the workload you need to run and the team that will operate it. A building can have available cabinets yet lack the power configuration, network access, or support arrangements your deployment needs.
The goal is a shortlist you can defend: each facility meets the same requirements, exceptions are documented, and its quote covers a comparable service. Work through these questions before committing to a location.
Define the workload and the market
Write a brief covering equipment count, rack dimensions, expected electrical load, network destinations, deployment date, and growth. Identify which systems need low latency to customers, another data center, or a particular cloud region. Specify how you will measure acceptable performance.
Select candidate markets using those dependencies alongside staff travel, shipping, and recovery requirements. Geographic distance alone is insufficient evidence of network performance. Request test endpoints or proposed routes, and measure from the networks your applications actually use.
For a second site, assess shared dependencies with the first, including carriers and regional hazards. Record data location and audit requirements early so unsuitable facilities leave the shortlist before detailed quoting.
Verify usable power and cooling
Ask for the electrical capacity available to your specific cabinets, expressed as usable kilowatts under the proposed configuration. Confirm voltage, circuit configuration, connectors, rack power distribution, and contractual load limits. Have the facility explain normal operation and what capacity remains when a feed is unavailable.
For redundant A/B power, validate that the surviving path can support the intended load. Include single-cord equipment in the design discussion. Two feeds on a quote do not explain the full redundancy arrangement.
Cooling needs the same specificity. Confirm the supported load per cabinet and any airflow, containment, or liquid-cooling requirements. For air-cooled equipment, ask where temperatures are measured: Lawrence Berkeley National Laboratory's thermal guidance identifies equipment intake conditions as the relevant measurement point. Match the proposed environment to your hardware requirements.
Confirm connectivity at the exact facility
List the carriers, internet exchanges, cloud connections, and private network destinations you require. Verify availability at the specific building and proposed service handoff. A provider's presence elsewhere in a metro area does not establish delivery to your cabinet.
Distinguish the physical connection from the network service using it. A cross-connect provides a point-to-point connection, as illustrated in Flexential's cross-connect documentation; internet transit or transport still needs an agreed service scope.
Request handoff details, media type, port speeds, ordering responsibilities, and installation dependencies. If you need diverse paths, ask providers to describe the physical routes and shared segments. Two carrier names alone are insufficient evidence of physical diversity.
Test the operating model and expansion path
Walk through a realistic incident: a server fails overnight, a replacement arrives, and someone must install it. Who can enter the facility, authorize work, receive shipments, locate spares, and confirm completion?
Remote hands can cover physical installation and troubleshooting; Equinix's Smart Hands service description illustrates that scope. For each candidate, establish available tasks, staffing hours, response commitments, billing increments, and exclusions. Separate physical assistance from responsibility for operating systems and applications.
Then describe the next expansion: additional cabinets, higher rack density, or more connections. Ask what is available now, what requires construction, and what can be reserved contractually. Confirm whether growth would require moving existing equipment. Spare floor space alone does not answer those questions.
Compare the complete commercial scope
Send every candidate the same requirements and request itemized quotes. Keep monthly recurring charges separate from nonrecurring charges, then compare the full initial term using consistent assumptions.
- Recurring items: space, committed power or metered consumption, network services, cross-connects, and support plans.
- Nonrecurring items: installation, circuit delivery, cabling, equipment handling, and deployment work.
- Variable items: power adjustments, bandwidth overages, remote hands, storage, and after-hours work.
For each line, record quantity, unit, billing basis, included allowance, and exclusions. Identify which vendor bills each service. Review commencement dates, term lengths, renewal provisions, escalation clauses, service credits, and exit obligations. Ask what happens commercially if one component is ready before the rest of the deployment.
Turn the shortlist into a deployment decision
Keep only facilities with written answers to the requirements that determine whether your deployment will work. Before selection, confirm:
- The location and proposed network paths meet workload needs.
- Cabinet power and cooling support initial load and the expansion plan.
- Required connectivity is deliverable, with dependencies and responsibilities assigned.
- Access, remote hands, shipping, and spares procedures fit your operating team.
- Quotes cover equivalent scope, with unresolved assumptions clearly marked.
Amherst Systems supports independent colocation selection and deployment engineering, connecting clients directly with vendors. Its partner relationships support that process; the facility decision should follow your requirements. Bring your equipment inventory, target markets, and timing to a colocation discussion to begin a focused comparison.