Powered by happy clients

Service · 06 · Colocation Services
ModernOps · Colocation

Cabinets,
documented.
Operations, owned.

Managed colocation across two geographically dispersed U.S. data centers: Valley Forge, PA (TierPoint) and Phoenix, AZ (PhoenixNAP). ModernOps is the remote-hands coordinator and infrastructure manager: power, cross-connects, IP, smart hands, LogicMonitor onboarding, and SOC 2-aligned facility oversight.

How it works
Footprint
2U.S. regions
Onsite Staff
24/7365 days
Provider Reviews
SOC
1 + 2
Share of Managed MRR
18.4% in 2025
TL;DR
ModernOps Colocation Services hosts client-owned equipment in Pennsylvania and Arizona while ModernOps coordinates power, connectivity, cross-connects, IP assignments, smart hands, monitoring, and SOC 2-aligned facility oversight, operated to a defined SLA, with Cabinet & Facility Documentation delivered to every customer.
01What is colocation

Colocation
as a managed
service.

Instead of running your own data center or managing the third-party relationship yourself, contract ModernOps to coordinate everything around your hardware: power, cabling, cross-connects, IP, smart hands, monitoring, and physical security oversight.

Colocation is a service model where a customer's dedicated hardware lives inside a third-party data center while a managed service partner like ModernOps coordinates everything around it: rack space, power, cabling, cross-connects, internet, IP addresses, smart-hands tickets, escort logistics, monitoring, and physical security oversight.

ModernOps Colocation Services targets workloads that still require dedicated hardware , DR infrastructure, NetApp / Pure storage, hypervisor hosts, firewalls, and specialty workloads, and removes the operational burden of managing the data center relationship directly.

Locations are Valley Forge, PA (TierPoint) and Phoenix, AZ (PhoenixNAP) , two geographically dispersed U.S. facilities staffed 24/7/365 with mantraps, biometric and keycard controls, CCTV/OSC monitoring, and locking cages and cabinets.

Every cabinet is documented. Every cross-connect is tracked. Every smart-hands request is ticketed. Every piece of equipment is monitored. The data-center relationship becomes a documented operating model instead of a stack of vendor portals.

02Who this is for

Built for the
teams that own
infrastructure.

Colocation shows up in four conversations across the IT org. We answer each of them with documentation, not promises.

01 / Executive
CIO &
VP of IT
A reliable data-center option for dedicated hardware, without the operational burden of facility management, carrier coordination, remote hands, and physical access workflows.
02 / Infrastructure
Data-Center
& Platform Lead
Documented rack, cabinet, power, PDU, circuit, cross-connect, switch port, IP, and equipment details for every piece of colocated infrastructure.
03 / Operations
IT Ops &
NOC Lead
Colocated equipment monitored in LogicMonitor, alerts routed into ITSM, remote-hands requests coordinated, incidents handled through ticketing and escalation.
04 / Risk & DR
DR, Risk &
Continuity Stakeholder
Geographically separated infrastructure in Valley Forge and Phoenix to support DR, replication, and recovery workflows, with annual SOC 1 / SOC 2 review of providers.
03What we hear

Common
concerns,
addressed.

Colocation conversations almost always start with the same set of doubts. We turn each one into an operating commitment, written into the SOW.

Some workloads still need dedicated hardware, but we don't want to run our own data center.
Client-owned equipment is colocated in Pennsylvania (TierPoint) and Arizona (PhoenixNAP) facilities, with ModernOps managing the relationship.
We need one partner to deal with the data center on our behalf.
ModernOps coordinates directly with data-center staff for power, connectivity, and access changes, and acts as remote-hands coordinator and infrastructure manager.
We don't have clean cabinet, power, port, and cross-connect documentation.
Onboarding documents everything: cage/cabinet IDs, PDU assignments, feed A/B, circuit IDs, breaker labels, cross-connect inventory, IP assignments, switch ports, and equipment by U position and power draw.
We need smart hands, but we need the workflow controlled.
Smart-hands tickets are submitted by ModernOps to the colo provider against an authorized contacts list collected during onboarding.
We need DR infrastructure in another geography without replatforming.
Two-region footprint in Valley Forge, PA and Phoenix, AZ, choose the location that fits, replicate between them when DR calls for it.
We need carrier, internet, IP, and cross-connect work tracked.
Six SKUs cover it: Rack Unit, Switch Port, Cross-Connect, Internet, IP Address, and Remote Access, each with documented circuit IDs, port details, and connected endpoints.
We need colocated equipment monitored like the rest of our environment.
LogicMonitor onboarding is part of the service. Equipment alerts automatically create ModernOps ITSM incidents.
Physical access and facility controls need to be more rigorous than our server closet.
24/7/365 onsite security and technical staffing, mantraps, biometric / keycard controls, 24-hour CCTV / OSC monitoring, and locking cages and cabinets.
04How we deliver

A documented
operating
model.

Colocation becomes a controlled service motion: facility coordination, smart-hands tickets, vendor escort logistics, IP and cross-connect documentation, remote access path confirmation, and LogicMonitor onboarding for colocated equipment, all part of the recurring rhythm.

01
Stand up
Document the cabinet
Provider, facility, and data-center location confirmed. Cage and cabinet IDs captured. PDU feed A/B assignments, circuit IDs, and breaker labels documented. Cross-connect inventory, IP assignments, switch port assignments, and equipment captured by make, model, U position, and power draw. Cabinet & Facility Documentation delivered.
02
Coordinate
Tickets, not phone trees
ModernOps submits smart-hands tickets to the colo provider against an authorized contacts list, coordinates onsite vendor access and escort logistics, and confirms remote access path (OOB / IPMI, VPN, or jump host). Changes flow through Jira Service Management with change-management entries for production-affecting work.
03
Operate
Run as a service
Colocated equipment is onboarded into LogicMonitor with automatic ITSM incident creation. Provider SOC 1 / SOC 2 reports are reviewed annually with remediation discussed when issues are identified. Cross-connect, IP, and cabinet documentation is kept current as the environment changes.
05What changes

Before
& after.

Two snapshots of the same colocation footprint. One in the world without ModernOps, one with.

Before
Vendor portals.
Stale spreadsheets.
Phone-tree
smart hands.

Customers manage dedicated hardware through a mix of local server rooms, carrier tickets, data-center portals, spreadsheets, vendor emails, and one-off requests. Hard to know which device is in which U position, which PDU feed or breaker supports it, which port it uses, which IP block applies, and who is authorized to request onsite work.

After · with ModernOps
Cabinets documented.
Smart hands ticketed.
Equipment monitored.
RACI in place.

ModernOps owns facility coordination, smart-hands ticket submission, onsite vendor escort logistics, IP and cross-connect documentation, remote-access path confirmation, and LogicMonitor onboarding. The customer receives Cabinet & Facility Documentation and a repeatable support path.

06Side by side

Legacy colo
vs. ModernOps Colo.

Same physical model. Different operating model. Seven dimensions where the work shifts off your team.

Dimension Legacy approach ModernOps Colocation
Facility coordination Customer teams coordinate directly with data-center staff, carriers, and vendors. ModernOps coordinates directly with data-center staff for power, connectivity, and access changes.
Cabinet documentation Rack elevations, PDU feeds, circuits, and port maps are stale or incomplete. Cage / cabinet IDs, PDU assignments, cross-connect inventory, IP assignments, switch ports, and U positions all documented.
Remote hands Smart-hands requests via ad-hoc calls or portals. Smart-hands tickets submitted to the colo provider with an authorized contacts list.
Monitoring Facility-hosted equipment may not be monitored consistently. Colocated equipment onboarded into LogicMonitor with automatic ITSM incident creation.
Geographic resilience Dedicated hardware in one customer site. Geographically dispersed Valley Forge, PA and Phoenix, AZ facilities.
Physical security Customer server rooms have limited controls. 24/7/365 onsite security, mantraps, biometric/keycard access, CCTV/OSC, locking cages/cabinets.
Vendor risk management Data-center control evidence not reviewed consistently. Annual SOC 1 / SOC 2 examinations reviewed for issues.
07What you get

Six measurable
service
outcomes.

Each outcome maps to a specific operational deliverable, not a marketing promise.

Dedicated hardware,
managed facility motion
Client-owned equipment in Pennsylvania and Arizona facilities, with the data-center relationship coordinated by ModernOps end-to-end.
Documented
cabinet reality
Cabinet, PDU, circuit, breaker, cross-connect, IP, switch port, and U-position details captured and maintained.
Remote hands
without chaos
Smart-hands tickets submitted on behalf of the customer; onsite vendor access and escort logistics coordinated through authorized contacts.
Connectivity
you can trace
Cross-connects, provider circuits, port details, connected endpoints, IP blocks, gateways, DNS, and switch port assignments documented and queryable.
Monitored colocated
infrastructure
Equipment onboarded into LogicMonitor with automatic ITSM incident creation when alerts fire.
Geographic
DR foundation
Two-region footprint in Valley Forge, PA and Phoenix, AZ, designed for replication, recovery, and continuity workflows.
08Operating flow

Ticketed.
Documented.
Monitored.

Colocation only earns its keep when the work around the cabinet is controlled. Power, smart hands, documentation, and monitoring run on a documented loop, not a phone tree.

09Locations & partners

Two U.S.
regions, staffed
24/7.

Both data centers are governed by stronger physical and environmental controls than a typical server closet, and both are formally reviewed against SOC 1 / SOC 2 evidence on an annual basis.

40.0959° N
75.4557° W
Northeast U.S.
Valley Forge,
PA
Provider · TierPoint
  • 24/7/365 onsite security & technical staffing
  • Mantraps · biometric & keycard controls
  • 24-hour CCTV / OSC monitoring
  • Locking cages and cabinets
  • Annual SOC 1 / SOC 2 evidence reviewed
33.4484° N
112.0740° W
Southwest U.S.
Phoenix,
AZ
Provider · PhoenixNAP
  • 24/7/365 onsite security & technical staffing
  • Mantraps · biometric & keycard controls
  • 24-hour CCTV / OSC monitoring
  • Locking cages and cabinets
  • Annual SOC 1 / SOC 2 evidence reviewed
10SKUs & connectivity

Connectivity
priced by the
unit.

Connectivity is packaged into the service. Six SKUs cover everything from a single rack U to a /28 IP block, each documented with circuit IDs, port details, and connected endpoints.

SKU.01 / Rack
Rack Unit
By U position. Equipment captured by make, model, U position, and power draw during onboarding.
U-position power draw
SKU.02 / Network
Switch Port
Top-of-rack port assignments documented per device, with connected endpoints captured.
1 Gb 10 Gb
SKU.03 / Carrier
Cross-Connect
Circuit ID, provider, port details, and connected endpoints documented for every cross-connect.
customer carrier on-net
SKU.04 / Transit
Internet
Tiered transit, sized to the workload. IPsec / SnapMirror friendly for DR replication traffic.
25 Mb 100 Mb 500 Mb 1 Gb
SKU.05 / Addressing
IP Address
Per IP or as a /28 block. Provider blocks, in-use IPs, gateway, and DNS captured on file.
/single /28 block
SKU.06 / Access
Remote Access
Out-of-band path validated during onboarding. Alternates available on request, all documented.
OOB / IPMI VPN jump host
11Proof points

Service
metrics &
coverage.

Representative figures from a typical Colocation + DRaaS engagement, plus the controls and reviews that frame the program.

Share of 2025
Managed Services MRR
18.4%
Deployment
timeline
30 DAYSgo-live target
Facility
resiliency
N+1power & cooling redundancy
Support / operations
coverage
24×7monitoring & remote hands
Representative
IP allocation
/28 blockblock per customer
Provider control
reviews
SOC 1 / 2reviewed annually
12Onboarding

30 days
from assess to
optimize.

Three repeatable phases. Predictable handoffs. A documented finish line, Cabinet & Facility Documentation delivered to the customer at day 30.

Phase 01 / Days 0-10
Assess
scope & intake
  • Confirm facility provider and data-center location
  • Capture cage / cabinet IDs and rack-unit needs
  • Power feeds (A/B), switch port speeds, internet bandwidth
  • IP blocks, cross-connect requirements, remote access method
  • Authorized smart-hands contacts list
Phase 02 / Days 10-20
Implement
document & coordinate
  • PDU assignments, feed A/B, circuit IDs, breaker labels
  • Cross-connect inventory and IP assignment records
  • Switch port assignments per device
  • Equipment inventory by U position and power draw
  • Smart hands and onsite access coordinated
Phase 03 / Days 20-30
Optimize
monitor & deliver
  • Confirm OOB / IPMI / VPN / jump-host remote access
  • Onboard equipment into LogicMonitor
  • Validate monitoring & ITSM incident creation
  • Deliver Cabinet & Facility Documentation
  • Schedule recurring change-management cadence
13Why ModernOps

Why customers
choose ModernOps.

The operating choices that separate a managed colocation program from a co-lo lease and a vendor portal.

01
Built for dedicated-hardware workloads
Designed for the workloads that still require physical infrastructure, DR, storage, hypervisors, firewalls, specialty compute.
02
Two-region colocation footprint
Geographically dispersed presence in Valley Forge, PA and Phoenix, AZ for DR and continuity workflows.
03
Named facility partners
TierPoint and PhoenixNAP, known operators with formal contracts and reviewed control evidence.
04
Complete cabinet documentation
Cabinet & Facility Documentation delivered to every customer and maintained as the environment changes.
05
Remote-hands coordination layer
Smart-hands tickets and onsite vendor escort handled by ModernOps with authorized contacts.
06
Connectivity packaged into the service
Rack Unit, Switch Port, Cross-Connect, Internet, IP Address, and Remote Access SKUs.
07
Monitoring integrated into managed services
LogicMonitor onboarding for colocated equipment with automatic ITSM incident creation.
08
SOC 2-aligned provider oversight
Annual SOC 1 / SOC 2 reviews of colocation providers, with remediation tied to identified issues.
14FAQ

Frequently
asked
questions.

Service definition, geography, SKUs, monitoring, security, and the operating boundaries between ModernOps and its customers, answered in plain language.

Q.01What is ModernOps Colocation Services?+
Support for workloads that still require dedicated hardware, including colocation of client-owned equipment in Pennsylvania and Arizona facilities, and coordination with data-center staff for power, connectivity, and access changes.
Q.02What does ModernOps do operationally?+
Acts as remote-hands coordinator and infrastructure manager for client equipment in third-party colocation facilities, including circuit and IP management, smart-hands coordination, and physical infrastructure oversight.
Q.03Which locations does ModernOps use?+
Two geographically dispersed data centers: Valley Forge, PA and Phoenix, AZ.
Q.04Which colocation providers are referenced?+
TierPoint in Valley Forge, PA and PhoenixNAP in Phoenix, AZ.
Q.05What Colocation SKUs are defined?+
Rack Unit, Switch Port at 1 Gb or 10 Gb, Cross-Connect, Internet from 25 Mb to 1 Gb tiers, and IP Address per IP or /28 block.
Q.06Does ModernOps support customer-owned equipment?+
Yes. ModernOps colocates client-owned equipment in Pennsylvania and Arizona facilities.
Q.07What documentation does the customer receive?+
Cabinet & Facility Documentation covering facility, cabinet, power, cross-connect, IP, switch port, and equipment details.
Q.08What does onboarding include?+
Facility details, cage / cabinet IDs, PDU assignments, cross-connect inventory, IP address assignments, switch port assignments, smart-hands authorized contacts, cabinet equipment inventory, remote access path, LogicMonitor onboarding, and Cabinet & Facility Documentation.
Q.09Does ModernOps manage power documentation?+
Yes, PDU assignments, feed A/B, circuit IDs, and breaker labels.
Q.10Does ModernOps manage cross-connect documentation?+
Yes, cross-connect inventory including circuit IDs, provider, port details, and connected endpoints.
Q.11Does ModernOps manage IP assignments?+
Yes, provider blocks, in-use IPs, gateway, and DNS details.
Q.12Does ModernOps coordinate smart hands?+
Yes. ModernOps submits smart-hands tickets to the colocation provider on behalf of the client.
Q.13Can ModernOps coordinate onsite vendor access?+
Yes, onsite vendor access and escort logistics.
Q.14Is colocated equipment monitored?+
Yes, equipment is onboarded into LogicMonitor.
Q.15How do alerts flow?+
LogicMonitor sends alerts and can automatically create ModernOps ITSM incidents.
Q.16What remote access paths are expected?+
OOB / IPMI, VPN, or jump host.
Q.17How does Colocation relate to DRaaS?+
Colocation often provides the dedicated physical location and connectivity foundation for DRaaS, for example, BYO servers, NetApp / Pure storage, and a firewall in one ModernOps facility, with 1 Gbps internet for IPsec / SnapMirror traffic and DR tests scheduled annually or semi-annually.
Q.18What physical security controls are expected at the facilities?+
24/7/365 onsite security and technical staffing, mantraps, biometric and keycard controls, 24-hour CCTV and OSC monitoring, and locking cages and cabinets.
Q.19Does ModernOps review provider control reports?+
Yes, annual SOC 1 or SOC 2 examinations are reviewed for issues.
Q.20Can customers use their own carriers?+
Yes, some clients have their own carriers and extend a cross-connect into ModernOps infrastructure.
Q.21Can customers connect by VPN instead of cross-connect?+
Yes, clients can connect through secure IPsec tunnels into dedicated firewalls.
Q.22How are changes handled?+
Through Jira Service Management for managed-services requests, with change-management entries for production-affecting work.
Q.23Is Colocation sold standalone or bundled?+
It can be sold standalone but is commonly bundled with DRaaS, server, storage, security, backup, hardware, and licensing services.
Q.24What customer responsibilities remain?+
Complying with contractual obligations, restricting access to authorized personnel, testing requested changes, notifying ModernOps of suspected breaches, maintaining business recovery / continuity plans, and communicating confidentiality changes that could affect sensitive data.
15Make colocation accountable

Bring your
hardware. We'll
own the cabinet.

Send us a rack count, a power draw, and the workloads that still need physical infrastructure. We'll document the cabinet, stand up the cross-connects, onboard LogicMonitor, and deliver Cabinet & Facility Documentation, within 30 days of kickoff.