AI is clearly accelerating demand for cloud computing, but not in the same way previous technology waves did. The most significant development today is not a breakthrough in software algorithms or a new application category. It is the enormous flow of capital into physical infrastructure designed to support artificial intelligence at scale. Chips, networking gear, power systems, and massive data centers have become the strategic center of gravity for the cloud market as providers compete to support model training and inference workloads.
The financial figures are difficult to ignore. US technology companies, including Alphabet, Amazon, Meta, and Microsoft, are expected to spend roughly $650 billion on AI-related infrastructure in 2026, up from about $410 billion in 2025, according to analysis cited by Reuters. This rate of growth signals something important: AI is not just another software wave that sits neatly on top of the existing cloud stack. It is forcing a redesign of the stack itself, from silicon to networking to data center design.
That redesign reaches deep into networking and data movement. Nvidia recently announced plans to invest $2 billion each in photonics companies Lumentum and Coherent, underscoring where the pressure points are emerging. The issue is no longer only raw compute. It is also how quickly data can move between processors, racks, and clusters without creating unacceptable bottlenecks or power inefficiencies. As AI systems scale, latency, throughput, and energy usage become first-order economic concerns.
The physical footprint of AI also changes the competitive landscape. Hyperscale providers are locking in long-term supplies of land, electricity, and chip inventory. They are partnering with utilities and even exploring modular nuclear reactors to meet power demand. In doing so, they are turning infrastructure into a strategic weapon. The scale of investment creates barriers to entry for smaller rivals and reinforces the advantages of the largest cloud vendors. Yet it also opens opportunities for specialized providers that can deliver focused AI capacity without the overhead of full-scale enterprise cloud portfolios.
Most AI starts in the public cloud
When companies are experimenting, speed matters more than optimization. Public clouds give teams immediate access to GPUs, foundation model APIs, vector databases, orchestration tools, security controls, and integration services. They also allow businesses to start pilots quickly without waiting for procurement cycles, data center expansions, or specialized infrastructure teams.
Given the high level of uncertainty, the public cloud is often the right choice for first-generation AI. Enterprises do not yet know which use cases will deliver value, how much inference traffic they will see, or which architecture model will ultimately survive. At this stage, the ability to quickly try many things is more important than squeezing every dollar from the underlying infrastructure. Managed services reduce friction, and friction is the enemy of early adoption.
This is why we are seeing strong initial demand for AI land in public cloud environments. Enterprises are building chatbots, copilots, knowledge assistants, document automation systems, and code generation tools there because the cloud dramatically lowers the barrier to entry. It provides compute as well as a full operating environment for AI experimentation, including integrated observability, identity management, and data governance features that would take months to assemble internally.
Next-gen AI systems present choices
The second generation of enterprise AI systems looks different. Once a use case proves its value and usage becomes persistent, the financial model changes. A workload that looked inexpensive during a proof of concept can become shockingly expensive when it runs at production scale, especially if it depends on premium GPU instances, high-performance storage, constant network traffic, and managed services layered on top of one another.
That is where repatriation enters the conversation. We are starting to see a pattern in which enterprises build first-generation AI systems on public clouds, learn what works, and then move some of those workloads back on-premises or onto so-called neocloud providers that offer AI-optimized infrastructure at lower cost.
On-premises deployment is attractive when utilization is steady, data gravity is high, governance requirements are strict, and the organization has sufficient scale to justify owning or directly controlling the infrastructure. Neocloud options become attractive when enterprises still want an external provider but do not want to pay the full premium often associated with large hyperscalers. These specialized providers are increasingly positioning themselves around dense GPU capacity, simpler pricing, and architecture built specifically for AI rather than for general-purpose enterprise IT.
This is an important adoption pattern because it dispels the old assumption that cloud migration is always one-way. In the AI era, workload placement is becoming more fluid. Enterprises are learning that the best place for experimentation may not be the best place for steady-state production and that AI economics can punish architectural laziness much faster than traditional enterprise applications ever did.
AI and public cloud demand
How much demand will AI drive for public cloud computing? Quite a lot, especially in the near term. Every major enterprise AI initiative will likely engage the public cloud in a meaningful way, whether for model development, training bursts, integration services, security tools, or global deployment. But it would be a mistake to assume that all demand will remain locked in traditional hyperscalers over time.
Some AI workloads will stay in the public cloud permanently because they are bursty, globally distributed, hard to predict, or tightly coupled to cloud-native services. Other workloads, especially those with stable usage patterns and heavy inference volume, will be candidates for relocation. Economics will drive those decisions more than ideology.
The likely outcome is a more segmented market. Public clouds will dominate the front end of AI adoption and continue to play a major role in hybrid operations. On-premises environments will regain relevance for cost-sensitive, steady-state, and compliance-heavy workloads. Neocloud providers will grow as a middle option for enterprises seeking external AI capacity without paying full hyperscaler prices. In short, AI will increase public cloud demand, but it will also heighten scrutiny of the correct fit in the long term.
One important nuance is that not all AI workloads behave the same way. Training jobs are often short-lived but extremely resource-intensive. They can be scheduled flexibly and tolerate some delay, which makes them good candidates for burst capacity on public clouds or specialized neoclouds. Inference workloads, by contrast, are continuous and latency-sensitive. They require a stable environment close to the data and users. As these two classes of AI work evolve, they are likely to pull in opposite directions: training toward flexible, cost-effective capacity, and inference toward distributed, optimized edge and on-premises environments.
Three factors to consider
First: Speed and cost are distinct metrics. The public cloud is usually the fastest way to get an AI initiative off the ground, and that speed has real business value. But the architecture that wins a pilot may end up destroying the production budget. Enterprises need a placement strategy from day one, even if they start in the cloud.
Second: AI workload economics differ from those of traditional applications. Training, inference, data movement, storage, and model serving can interact in ways that quickly create cost surprises. Organizations should model not only compute usage but also utilization patterns, network flows, and the costs of managed services surrounding the core AI stack. Without that discipline, they risk designing systems that are technically elegant but financially unsustainable.
Third: Future flexibility matters more than short-term convenience. Enterprises should avoid building AI systems so tightly around a single provider’s proprietary stack that moving becomes painful or impossible. The winners in this market will be the companies that preserve optionality, enabling them to shift workloads across public clouds, on-premises environments, and emerging neocloud platforms as economics, regulations, and business requirements evolve.
The real question is not whether the cloud will benefit, but how long each AI workload will remain in the cloud. AI will unquestionably generate significant new demand for public cloud computing. For most enterprises, AI workloads will stay in the cloud long enough to enable rapid innovation, but they will not necessarily remain there forever. The smartest organizations will treat cloud, on-premises, and neocloud resources as interchangeable levers in an ongoing cost and capability optimization process rather than as permanent destinations.
Source: InfoWorld News