A reversal nobody wanted to say out loud
For most of the last decade, the CIO playbook treated on-premises infrastructure as a liability to be retired as quickly as budget and application dependencies allowed. Kyndryl and Broadcom just put real headcount and training dollars behind the opposite bet. The two companies expanded their alliance around VMware Cloud Foundation, adding consulting, managed services, and agentic AI guardrails aimed squarely at enterprises pulling workloads back toward private and hybrid environments. The scope spans advisory work, strategy, architecture, design, platform upgrades, modernization projects, and ongoing day-two operations for both virtualized and containerized workloads running on VCF.
Giovanni Carraro, Kyndryl's global strategic alliances leader, put it plainly in describing the shift: clients are starting to look at trade-offs and try to find the right balance between public and private infrastructure. Public cloud is great at certain things, he said, adding that enterprises are coming to a maturity point where they recognize it is not perfect for every workload. That is a notable admission from a systems integrator whose consulting revenue for years leaned heavily on migration mandates that pointed almost entirely toward the public cloud.
Data residency and sovereignty are doing the driving
The stated rationale behind the expanded alliance is not primarily cost, which was the driver behind the last wave of repatriation conversations roughly a decade ago. Kyndryl frames this shift around data residency, technological sovereignty, and operational sovereignty, three concerns that have moved from compliance footnotes buried in vendor contracts to board-level agenda items as regulators across the European Union, the United Kingdom, and increasingly other jurisdictions tighten rules governing where enterprise data and AI processing workloads are permitted to physically reside and be accessed from.
Regan McGrath, Broadcom's president of Americas, described the partnership's goal as giving mutual customers expert guidance to run VCF as a strategic private cloud platform, positioning it as forward-looking infrastructure rather than a legacy holdover from before the public cloud era. For operators managing due diligence across a portfolio of companies, that framing carries real weight: sovereignty requirements have become an operational constraint shaping where AI workloads can legally and practically run, and that constraint shows up earlier in deal timelines than most technology teams currently expect it to.
AI workloads need guardrails before they need speed
The partnership's second pillar centers on AI governance built into the infrastructure layer itself, rather than bolted on as a separate monitoring tool after deployment. Kyndryl's Agentic AI Framework restricts what autonomous agents are allowed to do based on business and regulatory requirements defined ahead of time, an acknowledgment that AI is accelerating security threats at roughly the same pace it accelerates productivity gains. Autonomous systems can now probe for vulnerabilities at machine speed, and enterprises running agents on shared public infrastructure have fewer direct levers available to contain that exposure once an agent starts behaving unpredictably.
That framing represents a meaningfully different argument than the classic repatriation pitch that dominated the 2010s, which centered almost entirely on unpredictable egress fees and runaway cloud bills. This time the case being made is about control: who can see the underlying data, who or what can act on it autonomously, and how quickly an enterprise can produce a clean audit trail for a regulator or customer when an AI agent takes an action nobody explicitly authorized.
Betting several thousand consultants on a skills gap
The scale of the retraining commitment is arguably the strongest signal in the announcement. Kyndryl and Broadcom are jointly investing in skills development for several thousand Kyndryl consultants, architects, and delivery specialists, spanning the full lifecycle of advisory work, strategy, architecture, design, upgrades, modernization, and day-two operations for virtualized and containerized workloads running on VMware Cloud Foundation. That level of staffing investment reflects a bet on sustained multi-year demand, not a short-term marketing push timed to a single sales quarter.
Systems integrators generally do not commit to retraining thousands of people on a platform they expect enterprise interest in to fade within a year or two, since that kind of certification pipeline takes real budget and time to stand up and is expensive to unwind if demand does not materialize as forecast. The investment implies both companies see private and hybrid cloud skills as a durable, growing line of business through at least the end of the decade. For CIOs whose own architecture roadmaps and vendor relationships remain locked into public-cloud-only strategies, that scale of commitment from two major players is worth treating as a market signal rather than dismissing as opportunistic vendor positioning.
What this means for the ERP and platform conversation
The timing lines up with a broader pattern this year of enterprises re-litigating where their core systems of record should physically run. ERP platforms carrying financial, supply chain, and operational data are exactly the workloads where sovereignty requirements and audit obligations are strictest, and where building an internal case for repatriation, or at least a hybrid split, is easiest for a CIO to justify to a board already anxious about AI data exposure.
CIOs currently evaluating multi-year public cloud commitments should treat this Kyndryl and Broadcom alliance as evidence that two historically cloud-agnostic, large-scale players are betting hybrid and private cloud infrastructure, rather than full public cloud, will host a meaningful and growing share of AI-era enterprise workloads over the next several years. That bet should factor into any renewal negotiation currently underway, particularly where AI governance and data residency clauses remain unresolved in the existing contract language and nobody on the vendor side has offered a clear answer about where a given workload will actually run two years from now.
