Colocation

Colocation Contract Negotiation Checklist: 25 Terms Every Buyer Must Review

A colocation contract is a multi-year commitment that determines your infrastructure cost, reliability, and operational flexibility for the duration of the term. Most contracts run 3-5 years with annual spend in the six- to seven-figure range. Yet many buyers sign colocation agreements after reviewing only the headline price per kilowatt, the uptime SLA percentage, and the contract term length. The terms that actually determine whether the deal is good or bad -- power pricing structure, cooling responsibility, escalation clauses, exit provisions, liability caps -- are buried in the master services agreement and its schedules.

This checklist covers 25 contract terms that colocation buyers should review, understand, and negotiate before signing. Whether you are deploying a single rack or a multi-megawatt GPU colocation environment, these terms determine the true total cost and the quality of the service you receive.

Section 1: Power Terms (The Biggest Cost Driver)

Power is typically 40-70% of the total colocation bill. How power is priced, measured, and allocated determines whether you overpay or get competitive economics. Refer to our colocation pricing model comparison for detailed context on each structure.

1. Power Pricing Model

Colocation providers use three primary pricing models for power: per-kWh (metered consumption), per-kW (allocated capacity), and flat-rate (bundled into the rack or cage price). Each model shifts risk differently between buyer and provider.

2. Power Factor Requirements

Power factor measures how efficiently your equipment converts delivered power into useful work. A power factor below 0.9 means the provider must deliver more current (and therefore more infrastructure capacity) to support your load than the metered consumption reflects. Many contracts include minimum power factor requirements (typically 0.95+) with surcharges for non-compliance.

Modern server power supplies achieve 0.99+ power factor. However, if your deployment includes older equipment, large UPS systems, or non-standard loads (industrial cooling, Bitcoin mining ASICs with older PSUs), verify that your equipment meets the contractual minimum or negotiate the threshold down.

3. Power Density Per Rack

The contract should specify the maximum power available per rack. Standard colocation delivers 4-8 kW per rack. High-density GPU deployments require 20-100+ kW per rack. If your deployment requires high density, the contract must explicitly guarantee the power delivery capacity, the cooling capacity to match (a 40 kW rack generates 40 kW of heat that must be removed), and the PDU and circuit breaker configuration to deliver that power safely.

4. Power Escalation Clauses

Most multi-year contracts include annual price escalation for power. Common structures include fixed annual increases (2-5% per year), CPI-indexed increases (tied to the Consumer Price Index), utility pass-through (increases match the local utility tariff change), and uncapped "market rate" escalation (avoid this).

5. Power Redundancy Level

Verify the power redundancy configuration (N+1, 2N, or 2N+1) and whether the quoted price includes redundant power feeds. Some providers quote a low per-kW rate but charge separately for A+B redundant power feeds, effectively doubling the power cost. The contract should specify whether the quoted power capacity is per feed or total across all feeds.

Section 2: SLA and Uptime Guarantees

6. Uptime Percentage and Measurement

The headline uptime number (99.99%, 99.999%) is meaningless without understanding how it is measured. Key questions include whether uptime is measured per circuit, per rack, or per facility. A facility-level SLA means individual circuits can be down as long as the facility average remains above the threshold. Whether scheduled maintenance windows are excluded from the calculation is another critical question. If the provider schedules 8 hours of maintenance per quarter (excluded from SLA), your effective uptime guarantee is lower than the headline number.

7. SLA Credit Structure

What happens when the provider misses the SLA? The credit structure determines the financial consequence. Negotiate prorated credits based on actual downtime duration, not flat penalties. A strong SLA credit structure provides escalating credits: 5% of monthly recurring charge per hour of downtime in the first 4 hours, 10% per hour thereafter, up to 100% of the monthly bill. The contract should also specify whether credits are applied automatically or require a claim submission within a limited window.

8. Exclusions and Carve-Outs

Review the SLA exclusions carefully. Common carve-outs that weaken the SLA include customer-caused outages (reasonable), scheduled maintenance (reasonable if limited and disclosed in advance), force majeure (reasonable for genuinely unforeseeable events), upstream provider failures (problematic -- the provider chose the upstream providers), and "circumstances beyond the provider's control" (overly broad -- reject or narrow this language). Negotiate to remove vague exclusions and require the provider to define specific, named events that qualify as exclusions.

9. Incident Response and Communication SLAs

Beyond uptime, negotiate response-time SLAs for incident notification, on-site support, and resolution. The contract should specify the maximum time from incident detection to customer notification (target: 15 minutes), maximum time for remote-hands support response (target: 15-30 minutes), and escalation procedures with named contacts and escalation timelines for critical incidents.

Section 3: Cooling and Environmental Guarantees

10. Temperature and Humidity Specifications

The contract should specify the environmental conditions the provider guarantees at the rack inlet, referencing ASHRAE TC 9.9 standards. For UAE deployments, verify that the provider guarantees conditions within the ASHRAE A1 recommended envelope (18-27 degrees Celsius, 20-80% RH) year-round, including during peak summer when ambient temperatures exceed 45 degrees Celsius. Ask for historical temperature data from the provider's environmental monitoring system to validate their track record.

11. Cooling Capacity Commitment

For high-density deployments, the cooling commitment is as important as the power commitment. A provider may allocate 40 kW of power to your rack but only have 20 kW of cooling capacity in that area. The contract should explicitly state the cooling capacity per rack (matched to the power allocation) and the cooling technology used (air, liquid, or hybrid).

12. PUE Guarantee

Some forward-thinking providers include PUE guarantees in their contracts. If you are paying metered power, PUE directly affects your bill because you pay for the total power delivered to your rack, including cooling overhead. A provider with PUE of 1.5 versus 1.1 charges you 36% more per kWh for the same IT workload. Negotiate a maximum PUE commitment or, if possible, structure your power pricing to exclude cooling overhead (pay only for IT power at the rack, with cooling bundled into the space charge).

Section 4: Connectivity and Network

13. Cross-Connect Pricing

Cross-connects (physical cables connecting your equipment to other tenants, carriers, or cloud on-ramps within the facility) are a common source of hidden costs. Review the per-cross-connect monthly fee (ranges from $50-$500 for copper, $100-$1,000 for fiber), installation fees, minimum term per cross-connect, and whether the price includes the patch panel port or just the cable.

For deployments requiring many cross-connects (connecting to multiple carriers, cloud providers, and IX peering), these costs add up quickly. Negotiate volume discounts or a bundled cross-connect package.

14. Carrier and Cloud Access

Verify which carriers and cloud providers are present in the facility. The contract should list the available carriers, confirm that you can bring your own carrier (and what the meet-me room fees are), and specify whether network infrastructure for high-bandwidth applications is available.

15. Network Redundancy

The facility should offer diverse network paths. If all fiber enters through a single conduit or manhole, a single construction accident can sever all connectivity. The contract should warrant diverse fiber entry paths and, ideally, connectivity from multiple utility vaults or manholes.

Section 5: Physical Security and Access

16. Physical Security Standards

Physical security requirements should be explicit in the contract. Verify that the contract specifies multi-factor access control (biometric + badge + PIN minimum), 24/7 on-site security personnel, CCTV coverage of all common areas with minimum retention period (90 days is standard), visitor escort policies, and rack-level locking (provider-managed or customer-managed). For UAE deployments, verify compliance with TDRA (Telecommunications and Digital Government Regulatory Authority) data center security requirements.

17. Access Hours and Remote Hands

24/7 physical access to your equipment should be guaranteed without additional fees. Some providers charge after-hours escort fees for access outside business hours. The contract should guarantee unrestricted 24/7 access for authorized personnel and define the remote-hands service scope, pricing, and response time SLA.

Section 6: Contract Terms and Financial Provisions

18. Contract Term and Renewal

Typical colocation contracts run 1-5 years. Longer terms generally yield lower per-kW rates. Review the auto-renewal provisions carefully. Many contracts automatically renew for successive 1-year terms unless the customer provides written notice 90-180 days before expiration. Missing the notice window locks you in for another year at potentially higher rates.

19. Early Termination

Early termination fees (ETFs) are the most provider-favored term in most colocation contracts. Standard contracts charge the full remaining contract value as a termination fee, which means exiting a 5-year contract after 1 year costs 80% of the total deal value. Negotiate a declining ETF structure: 75% of remaining value in year 1, 50% in year 2, 25% in year 3, and so on. Also negotiate termination rights without penalty for material SLA breaches (two consecutive months of SLA non-compliance is a reasonable threshold).

20. Liability and Indemnification

The liability cap determines the maximum the provider will pay if something goes catastrophically wrong (facility fire, prolonged power loss, security breach). Standard contracts cap liability at 12 months of recurring charges. For deployments where the hardware value and business continuity impact far exceed the colocation fees (common for GPU deployments where hardware costs 10-50x the annual colocation fee), negotiate a higher liability cap or require the provider to carry insurance that names you as an additional insured.

21. Insurance Requirements

Both parties should carry appropriate insurance. The contract should specify the provider's minimum insurance coverage (property, general liability, professional liability, cyber liability) and require certificates of insurance. You may also need to provide proof of insurance for your equipment housed in the facility. For UAE deployments, verify that insurance policies comply with local regulatory requirements.

Section 7: Operational Terms

22. Change Management

The contract should define the provider's obligations regarding facility changes that affect your deployment. This includes advance notice requirements for maintenance windows (minimum 72 hours for planned maintenance, minimum 30 days for major infrastructure work), approval requirements for changes to shared infrastructure (cooling system modifications, electrical upgrades, network changes), and the right to review and approve any changes that directly affect your racks or power circuits.

23. Audit Rights

You should have the right to audit the provider's compliance with contractual obligations, including SLA performance, security measures, environmental controls, and financial records (if the contract includes cost-plus or pass-through pricing). The contract should specify audit frequency (annual at minimum), audit scope, provider cooperation requirements, and how audit costs are allocated.

24. Data Sovereignty and Regulatory Compliance

For UAE deployments, the contract must address TDRA compliance, data residency requirements under UAE law, PDPL (Personal Data Protection Law) obligations, and free zone regulations (if the facility is in a UAE free zone). The contract should specify which party is responsible for regulatory compliance, how regulatory changes during the contract term are handled, and whether the provider will cooperate with regulatory audits and information requests.

25. Expansion and Right of First Refusal

If you anticipate growth, negotiate expansion provisions now rather than later. Key terms include right of first refusal on adjacent racks or cage space, guaranteed pricing for expansion capacity (at contract rates, not then-current rates), maximum lead time for provisioning additional power and space, and the provider's obligation to maintain reserved expansion capacity for a defined period.

Negotiation Strategy: Leverage Points for Buyers

Colocation is a competitive market, especially in regions with multiple providers like the UAE (du, Equinix, Khazna, Gulf Data Hub, and independent operators). Buyers with meaningful power requirements (100+ kW) have significant negotiating leverage. Use these strategies to improve contract terms:

• Multi-provider RFP. Solicit proposals from 3-5 providers simultaneously. Let each provider know you are running a competitive process. Pricing drops 10-25% in competitive bid situations versus sole-source negotiations.
• Total cost modeling. Compare providers on total cost of ownership (power + space + cross-connects + remote hands + cooling surcharges + escalation over term), not just the per-kW headline rate. The cheapest per-kW rate often comes with the highest ancillary charges.
• Reference checks. Request references from existing customers with similar deployment profiles. Ask about actual SLA performance, responsiveness to incidents, and whether the provider honored contract terms during disputes.
• Legal review. Have technology-experienced legal counsel review the master services agreement. Colocation contracts are not standard -- each provider uses custom terms that may contain provisions unfavorable to the buyer. The cost of legal review ($5,000-$15,000) is negligible relative to a multi-year six-figure commitment.
• Benchmark against industry standards. Reference published SLA benchmarks and pricing data when negotiating. Providers respect informed buyers and are more willing to concede terms to customers who demonstrate market knowledge.

Post-Signature: Ongoing Contract Management

Signing the contract is the beginning, not the end. Effective contract management ensures you receive the service you negotiated:

• Track SLA performance monthly. Request formal SLA reports and compare against contractual thresholds. File credit claims promptly when thresholds are missed -- most contracts require claims within 30-60 days.
• Monitor power billing accuracy. Compare metered consumption (from your own power monitoring or the provider's portal) against invoiced amounts. Billing errors in the provider's favor are common and rarely self-corrected.
• Calendar renewal and termination dates. Set reminders at least 180 days before any renewal or termination deadline. Auto-renewal traps are real -- missing a notice window costs a full year of commitment.
• Document all incidents. Maintain your own log of outages, environmental excursions, security incidents, and service failures. This documentation is essential for SLA credit claims and for renegotiating terms at renewal.
• Annual contract review. Review your contract annually against current market rates and your actual usage patterns. If your deployment has changed significantly (higher density, different cooling requirements, more cross-connects), the contract may no longer be optimal. Use the annual review to prepare for renegotiation.

A well-negotiated colocation contract protects your infrastructure investment for years. The time spent reviewing, understanding, and negotiating these 25 terms pays for itself many times over through lower costs, better service, and stronger contractual protections when things go wrong.