Colorado Springs
Second Metro for DR, Replication, and Dual-Site Architectures
NexEdge’s dual‑metro design provides true geographic separation between Denver and Colorado Springs, giving operators a second, independent metro for disaster recovery, synchronous and asynchronous replication, and active/active architectures. With diverse fiber paths, low‑latency interconnect, and isolated failure domains, the platform enables resilient multi‑site deployments without the complexity of managing disconnected environments.
Platform Role & Capacity
1.5MW
8.0M...
Phase 1 Capacity
Critical IT after PUE 4 available within ~6 months of offtake
Phase 2 Capacity
Critical IT after PUE 4 full geoseparated DR node
Network & Connectivity
Regional DCI
Cooling + Water
Long-haul dark fiber + highcapacity wave options back to Denver metro 4 lowlatency regional interconnect
Closed-loop positioning with density upgrade path in Phase 2; water stewardship built into the Phase 2 engineering plan
Ideal Tenant Use Cases
Backup + Replication
Primary storage replication target from Denver metro workloads 4 metro-separated, low-RPO designs
Secondary Inference Cluster
Geo-redundant AI/ML inference with replicated model weights and datasets across failure domains
Regulated Workloads
Finance, healthcare, and defense-adjacent tenants requiring documented metro separation for compliance posture
Primary - DR pairing:
Colorado Springs is engineered as the natural BCP/DR counterpart to all Denver metro NexEdge sites under a single platform contract.