
Advice for IT Pros
Repatriation is the market correcting a decade of poor placement decisions. That’s healthy, but the burden of getting it right falls on network, I&O, and data center teams. If you’re facing a repatriation project, here’s where I would focus.
- Lock down capacity first. The single biggest mistake I see is treating space and power as a procurement detail to be sorted out after the business case is approved. With vacancy at historic lows in the major markets and most new construction spoken for before it’s finished, that order of operations no longer works. Engage colocation providers and your own facilities team as early as possible, and be prepared to consider secondary markets, smaller footprints spread across multiple sites, or upgrading an existing owned facility. Get firm answers on power per rack, cooling options, cross-connect availability, and delivery dates before committing to a migration timeline. In many markets, the lead time for space and power can be longer than the migration itself.
- Design the network for a hybrid end state. Repatriation doesn’t end with a clean break from the cloud; it ends with more locations that must work as one. Treat interconnects, cloud on-ramps, WAN, data center fabric, segmentation, and security policy as a single architecture spanning on-prem, colo, and multiple clouds. That means sizing interconnect bandwidth for actual data flows rather than estimates, enforcing consistent policy regardless of where a workload runs, and building in visibility to troubleshoot an application path that spans three environments. If the network is designed as an afterthought, latency and integration problems that already plague many organizations will worsen.
- Plan AI infrastructure explicitly. If AI inference or fine-tuning is part of the repatriation plan, treat it as a separate project. GPU clusters introduce power density, cooling, and networking requirements that are unlike those of a traditional enterprise data center. The back-end fabric connecting GPUs needs high bandwidth, low latency, and lossless behavior. Choices among Ethernet and InfiniBand, rack design, and storage architecture all have long-term consequences. Bolting an AI cluster onto a general-purpose facility and network is a recipe for underused GPUs, which are among the most expensive assets an IT organization can own. Bring in partners who have built these environments before.
- Bring the cloud operating model with you. Developers and business units have spent a decade getting infrastructure via an API in minutes. They won’t accept going back to filing tickets and waiting weeks. Whatever you build on-prem needs self-service provisioning, infrastructure as code, automation, and APIs that feel like the cloud. The same goes for cost visibility: FinOps practices shouldn’t stop at the edge of the public cloud. If you can’t show what an on-prem workload actually costs, including power, space, hardware depreciation, and staff, you won’t be able to prove that repatriation delivered the savings that justified it.
- Invest in people. The skills gap is real and runs in both directions. Many cloud-era engineers have never designed a data center fabric, planned power distribution, or managed a hardware refresh cycle, while many veteran infrastructure engineers have limited exposure to cloud-native tooling. Cross-train in both directions, pair senior data center staff with cloud engineers on migration projects, and consider managed services or partners to fill gaps in the short term. Engineers who understand both worlds will be among the most valuable in IT over the next five years, and companies that develop them internally will move faster than those trying to hire them in a tight market.
Final thoughts
Cloud repatriation is often framed as a referendum on the public cloud, but that misses the point. The Foundry data shows companies are still increasing cloud spending even as they bring a meaningful share of workloads back on-premises. What’s changing is the assumption that every workload belongs in one place. Security, sovereignty, cost predictability, and AI are forcing organizations to be deliberate about where applications and data reside.
For IT pros, that’s both a challenge and an opportunity. The challenge is that hybrid is harder than all-cloud or all-on-prem. It requires scarce data center capacity, a network built to span multiple environments, operations tools that span them all, and skills many organizations let lapse. The opportunity is that infrastructure teams are back at the center of the strategy conversation. For years, the network and data center were viewed as plumbing to be minimized. Repatriation, and AI in particular, puts them back in the role of a competitive differentiator.




















