Enterprise colocation requirements, drafted before you talk to providers
Enterprise colocation is leased data center space set up around a large company's rules: private cages or suites, audited security, several carriers and multi-year terms. Answer eight questions and your requirements document fills in as you go.
Rather start with a person? Ask for a shortlist and our team replies by email within 24 hours.
What enterprise colocation services include, and where retail stops
Enterprise colocation services cover the same basics as any colocation: you own the servers, the provider runs the building, power, cooling and physical security. The difference is scale and accountability. Retail colocation sells cabinets off a price list. An enterprise rents a defined footprint, gets audit reports and written service levels, and negotiates the contract line by line.
A colocation cage
A colocation cage is a locked mesh enclosure inside a hall shared with other tenants. It fits a few dozen cabinets and moves quickly, because the hall already exists.
A suite of your own
A walled room with its own door, access list and often its own cooling. It suits security teams that want nothing shared past the corridor.
A wholesale hall
A full data hall, usually a megawatt and up, leased on longer terms. You decide the layout; the provider keeps the power and cooling running.
Enterprise data center vs colocation, line by line
Enterprise data center vs colocation comes down to who carries the building. Owning means your capital, your staff and your schedule. Colocation moves the building to a provider and leaves you the hardware, so the comparison of colocation vs enterprise data center is really a comparison of commitments.
| Your own data center | Enterprise colocation | |
|---|---|---|
| Capital | Land, building, generators, UPS and cooling sit on your balance sheet and age there. | Paid monthly under contract. Your capital goes to servers, storage and network. |
| Staffing | Facilities engineers, security guards and maintenance contracts around the clock. | The provider staffs the building. You staff your systems, in person or through remote hands. |
| Power | Limited to what your utility feed and generators can carry, and upgrades take years. | Bought by the kilowatt, with redundancy set in the contract. Adding more depends on what the building has free. |
| Time to capacity | New buildings need land, permits and a utility connection before any server goes in. | Months for space already built. In tight markets, new capacity is often leased well before it is finished. |
| Exit | A building to sell, repurpose or keep running after the systems leave. | A notice period and a removal window, both set when you sign. |
| Control | Every rule is yours, and so is every failure. | Your rules inside the cage; the provider's audited rules for the building around it. |
Primary-market vacancy fell to a record low of 1.4% in the first half of 2026, and 80.4% of capacity under construction was already preleased. Source: CBRE research, H1 2026 data center report, cbre.com.
Secure colocation: what your security team will check
Secure colocation is a building where every step closer to your hardware is controlled, recorded and kept on file. Security teams read it from the outside in: fence, front door, the interlocked entry, the data hall, your cage, your cabinet. At each layer they ask who can pass, how that is proven, and how long the record lasts.
- Identity at the door. Government ID and a pre-approved access list, checked by staff at a staffed desk.
- Data center access control. Badge plus PIN or biometrics to enter the hall, with one person through at a time.
- Your own access list. You decide who enters your cage, and changes take effect the same day.
- Logs and footage. Badge records and camera footage kept long enough for your audits, with extracts on request.
- Chain of custody. Every drive and server logged in, logged out and, at the end, destroyed with a certificate.
Compliant colocation solutions: SOC 2, HIPAA, PCI DSS and FedRAMP
Compliant colocation solutions work on shared responsibility: the provider proves the building, and you prove everything you put in it. No facility makes a tenant compliant. What a good one does is hand your auditor clean evidence for the physical controls, so your own team only has to cover its systems.
What the facility's reports cover
- Perimeter, entry and data hall access
- Cameras, guards and visitor handling
- Power, cooling and fire suppression
- The provider's own staff, vendors and procedures
- Hardware arriving and leaving the building
What stays with you
- Who on your team gets cage access, and when it ends
- Servers, operating systems, data and encryption
- Network security inside your space
- Logs from your own systems
- Your policies, risk assessment and audit
SOC 2 Type II
An independent auditor's report on how the provider's controls worked over a period, not just on one day. Security is always included; availability, confidentiality, processing integrity and privacy are optional, so check which ones the report covers.
AICPA, 2017 Trust Services Criteria, revised 2022.
HIPAA
HHS treats a provider that maintains ePHI on your behalf as a business associate, even if it holds only encrypted data without the key. Whether a space-and-power provider falls under that depends on its access, so get its position on a BAA in writing.
HHS, HIPAA FAQ 2076.
PCI DSS
Requirement 9 covers physical access to cardholder data. Under version 4.0.1, cameras or access controls must monitor sensitive areas, and the records must be kept at least three months unless law says otherwise.
PCI Security Standards Council, PCI DSS v4.0.1, Requirement 9.2.1.1, document library.
FedRAMP and government
FedRAMP authorizes cloud services, not buildings. A colocation provider's role is to document the physical and environmental controls your system inherits; FedRAMP's catalog lists 51 controls and enhancements in that family.
FedRAMP, Physical and Environmental Protection, 2026 rules.
This is planning information, not legal or compliance advice. Your auditor or counsel confirms what applies to your systems.
Carrier neutral colocation and direct cloud connections
Carrier neutral colocation means the building lets any network carrier in, so you choose and switch carriers on your terms instead of the landlord's. For an enterprise, that choice is about resilience as much as price: two carriers on separate fiber paths into the building keep one cut cable from becoming an outage.
- The meet me room. The room where every carrier's fiber ends inside the building. Your cross-connects are patched there, so ask who can enter it and how fast a new connection is installed.
- Count the carriers, then check the paths. Ten carriers sharing one conduit into the building are one risk, not ten.
- Cloud on-ramps nearby. Each cloud publishes the buildings where its private links land: Google Cloud Interconnect, AWS Direct Connect, Oracle FastConnect and Azure ExpressRoute all do. A short cross-connect beats a long circuit.
- An internet exchange port. Useful when you trade a lot of traffic with networks you can peer with directly.
- Cross-connect terms. One-time and monthly fees per connection add up across many links, so fix them in the contract.
Managed colocation services: who runs the hardware
Managed colocation services sit on a scale, and the right point depends on where your people are. Some enterprises keep engineers near the building. Others run everything remotely and buy remote hands services, paying the provider's staff to be their hands. A few hand over day-to-day hardware care entirely.
| Your staff on site | Remote hands | Managed | |
|---|---|---|---|
| Racking new hardware | Your team | Provider staff, to your written instructions | The managed provider |
| Swapping a failed drive | Your team | Provider staff, on a ticket | The managed provider, often without a ticket from you |
| Watching alerts | Your operations team | Your operations team | Shared, as the contract defines |
| Fits best when | You have engineers within reach of the building | Your team is elsewhere but owns every decision | You want to stop running hardware yourself |
Whichever you choose, put response times and rates in the contract. "Smart hands" is a name some providers use for skilled remote hands work; the label matters less than the written scope.
Multi-site plans: primary and DR, or two sites live
Most enterprises end up with a primary and DR pair, and some run two sites active-active. The building is only part of the plan. The rest is distance, replication and contracts that keep both sites moving in step.
- Distance with a reason. Separate power utilities and separate flood and storm exposure, close enough for replication to keep up with your recovery targets.
- Same rules at both ends. Matching security procedures and audit reports, so your auditor reviews one standard, not two.
- Contracts that end together. Co-terminous terms, or at least renewal dates close enough to negotiate both at once.
- Test the failover. A DR site that has never carried the load is a plan, not a capability.
Power was the leading cause of impactful data center outages in Uptime Institute's 2026 analysis, and 57% of respondents said their latest major outage cost more than $100,000. Source: Uptime Institute, Annual outage analysis 2026.
What an enterprise colocation contract should include
An enterprise colocation contract runs for years, so the terms you skip at signing are the ones you live with longest. These are the clauses we see enterprises regret leaving vague. None of this is legal advice; your counsel writes the final language.
- Committed power
- The kilowatts you commit to per site, how that commitment steps up over the term, and whether you pay for what you reserve or what you draw.
- Service level credits
- What counts as a power, cooling or network failure, how it is measured, what each failure earns you, and the cap on credits.
- Price escalators
- The yearly increase in writing, with a ceiling that holds for the whole term, renewals included if you can get it.
- Room to grow
- A right of first refusal on the space next to yours, or capacity held for you, with the terms agreed now while you have leverage.
- Renewal and notice
- How renewal works and how far ahead you must give notice to leave. Notice windows are easy to miss in a busy year.
- Exit and removal
- How long you have to move out, the rate if you overrun, and how drives and media are destroyed on the way out.
North American data center construction was 95% pre-committed in the first half of 2026, with vacancy near 1%. Source: JLL, H1 2026 data center report. In Chicago, CBRE expected no contiguous space of 5 MW or more to come free this year. Source: CBRE, Chicago H1 2026.
Who this site serves, and who it doesn't
We work with larger companies placing their own systems, usually from 20 racks to several megawatts, often in more than one market.
- IT and infrastructure leaders leaving a data center they own, consolidating sites, or replacing a contract that is ending.
- Regulated companies in healthcare, finance, insurance, government contracting and retail that need SOC 2, HIPAA, PCI DSS or FedRAMP-ready space.
- Procurement and vendor management teams asked to source colocation with security and audit terms attached.
- Enterprises adding AI or high-density capacity beside the footprint they already run.
This site is not the right fit for
- One or two servers, or a single rack. A retail provider can usually set that up directly and faster.
- Providers, MSPs, resellers and brokers. We don't take or pass on pitches.
- Students and job seekers. The sections above are free to read, but the form is for buyers.
A reply by email within 24 hours.
Behind this site
Enterprise Colocation is run by the Metro Colo Advisory team. The firm advises companies on data center space, and no provider owns any part of it or steers its advice.
Who pays us
When a company we introduce signs with a provider, that provider pays our fee, and you pay nothing for the introduction. Bigger projects can also hire us for fixed-fee work on requirements, provider selection and contract terms, priced in writing before any work begins.
Who sees your request
Only our team reads what you send. Your name, company and requirements stay with us until you say yes, and you know which providers before we contact any of them.
When you'll hear from us
Within 24 hours, by email. If colocation is the wrong answer for what you described, the reply says so.
Questions enterprise buyers ask
What makes colocation "enterprise" rather than retail?
Mostly the paperwork and the size. Retail colocation sells cabinets on standard terms. Enterprise colocation is sized in suites, halls or several hundred kilowatts, comes with audit reports your security team can read, and is negotiated: power commitments, credits, expansion rights and exit terms written for your company.
Is colocation cheaper than running our own data center?
We don't answer that with a single figure, because it depends on how old your building is, what your power costs and how much capacity sits idle. What colocation changes for certain is the shape of the spend: a monthly contract in place of a building on the balance sheet, and no facilities staff of your own.
Does a colocation provider make us compliant?
No provider can. A facility's SOC 2, ISO 27001 or PCI DSS reports cover the building and the provider's own staff. Your systems, your access policy and your data stay your responsibility, and your auditor decides how much of the provider's evidence you can rely on.
Do we need a business associate agreement with our colocation provider?
It depends on what the provider does with your equipment and data. HHS treats anyone who maintains ePHI for you as a business associate, even without a decryption key. A provider that only supplies locked space and power may take a different view, so get its position in writing and let your counsel decide.
How far apart should a primary and DR site be?
Far enough that one regional event cannot take out both: separate power utilities and flood exposure are the usual tests. Close enough that replication keeps up with how much data you can afford to lose. Your recovery targets set the distance, not a rule of thumb.
How long does an enterprise colocation project take?
The builder plans for roughly 30 to 60 weeks from scoping to the last migration, longer with FedRAMP work, two active sites or AI density. Build-out and security review are the usual long poles. Space is tight in many markets, so the earlier you scope, the more buildings stay on the list.
Do you work with small deployments, resellers or students?
This site is built for companies placing their own systems at scale, usually 20 racks or more. If you need one or two racks, a retail provider can usually help you directly. If you sell colocation, cloud or managed services, the form will tell you before anything is sent.
What happens after we send our requirements?
Our team reads them with your builder answers and replies by email within 24 hours, often with a few questions. If you want a shortlist, we name the providers we would approach and why. No provider hears your name until you agree.