โŒ

Normal view

Cloud has a new bulk capacity market

11 September 2026 at 10:00

For 15 years, public cloud providers have defined the industry for most enterprises: on-demand, automatically metered services delivered over the open internet that give developers immediate access to storage, databases, compute, application development platforms, and AI capabilities. That model remains dominant because it is simple, well-instrumented, and universally supported. Yet an adjacent reality has always existed. Large-scale, off-market capacity deals where technology companies with surplus GPUs, storage, and compute sold blocks of capacity in bulk to other firms under nondisclosure agreements were once common. Those were cloud transactions in substance, since you were using somebody elseโ€™s servers. However, they lacked the automation, metering, and governance that define public cloud services, and they operated entirely outside the frameworks enterprises rely on for budgeting, compliance, and accountability.

A shadow market becomes visible

These arrangements are now becoming more visible and more formalized. Some are even openly auctioned. Metaโ€™s entrance into the cloud capacity space, essentially offering its excess compute infrastructure to outside buyers, represents the maturation of a market that has existed in back rooms for years. Large, multiyear capacity commitments are no longer whispered about during boardroom lunches. They are being announced, financed, and tracked by analysts. This shift is creating a distinct layer in the cloud landscape, one that sits between traditional hyperscalers and true private clouds, and one that enterprises can no longer afford to ignore.

The practical implication is that the cloud market you thought you understood now has a parallel track. When a large enterprise needs maximum GPU capacity for model training or inference, it has more options than a year ago, and those options come with genuinely different trade-offs. You can go to a hyperscaler and pay the published rate for metered GPU as a service, receiving a fully managed platform with all the tools, governance, and integration you need. Or you can reach out to a technology provider that happens to have idle or excess GPU capacity and negotiate a bulk deal at a fraction of the published rate. The first option provides predictability and depth of service. The second offers raw cost savings if you have the operational capability to handle less-managed infrastructure.

This bifurcation is muddying procurement decisions. The gap in pricing between bulk off-market capacity and public cloud offerings can be substantial. Some analysts cite differentials ranging from 10 to 100 times. But headline GPU rates are only part of the evaluation. Bulk deals tend to come with minimal metering, limited monitoring, and a do-it-yourself culture around incident response and optimization. You are, in effect, purchasing wholesale energy. It is robust and capable, but it requires your own wiring and maintenance. Organizations accustomed to the instrumentation and service-level agreements of hyperscalers may find such a different operational reality a bit jarring. Those with mature cloudops teams may find the economics compelling.

Who benefits and who adjusts

The hyperscale incumbents will not be displaced overnight. They offer the complete ecosystem, not just GPU frameworks but development tools, hundreds of managed services, identity, compliance, and integration layers that are genuinely difficult to replicate. However, they are now facing a market where customers with intensive computational needs can source raw GPU capacity from alternative suppliers, particularly for bursty or cost-sensitive workloads. This is not necessarily a threat to hyperscaler dominance, but it is a complication. The hyperscalers will likely respond through partnerships, capacity-coverage agreements, and possibly acquisitions of promising capacity players. Effectively, they will become customers of the same off-market ecosystem they once ignored.

The cloud market is adding a new axis of choice: managed breadth versus specialized efficiency. Enterprises will increasingly construct hybrid operating models, keeping steady-state, security-sensitive, and toolchain-dependent workloads on hyperscaler platforms while offloading cost-intensive training runs and elastic inference to bulk-capacity providers. This is not a binary choice. It is an expanding continuum of sourcing options that demands more sophisticated procurement and architecture planning.

How to take advantage

Know your actual workload cost before you negotiate. If your AI workloads are compute-intensive, model training-heavy, or require burst capacity at unpredictable intervals, the economics of bulk capacity deals can be compelling. Run a pilot that captures total cost of ownership, including data movement, integration effort, operational overhead, and potential downtime during self-managed troubleshooting before you assume bulk is simply cheaper. Compare fully loaded costs, not GPU-hour sticker prices.

Build portability into your AI stack from the start. Bulk-capacity providers often lack the governance, compliance tools, and model life-cycle management enterprises need. Mitigate this risk by standardizing on containerized inference runtimes, open model formats, and CI/CD pipelines capable of deploying across multiple targets. This type of discipline turns vendor diversity into negotiating leverage rather than operational liability. It also ensures you can shift workloads as capacity markets fluctuate.

Treat capacity sourcing as a strategic procurement function. Bulk cloud capacity is not a niche quirk. It is becoming a recognized market that rewards supply-chain thinking. Diversify your supplier base, negotiate multi-vendor commitments where possible, and develop a reserve strategy for critical workloads. Keep your hyperscaler relationship for reliability and breadth, but maintain at least one secondary capacity arrangement for cost-sensitive or elastic workloads. The enterprises that treat capacity as a variable asset, rather than a fixed infrastructure decision will be better positioned as this market continues to expand and formalize.

The cloud market is no longer a simple fork between public and private. A defined middle ground of negotiated bulk capacity is now attracting billions in investment and reshaping how AI infrastructure costs are allocated. Enterprises that understand this landscape and build flexible, portable architectures that can span it will capture more value from AI investments than those who default to the familiar hyperscaler menu alone.

Digital sovereignty sounds great until you try ditching your suppliers

10 September 2026 at 10:05
After years of governments and tech vendors banging the digital sovereignty drum, most large organizations have concluded that true technological independence is beyond their reach. That's according to new research from Capgemini, which found that 59 percent of organizations regard complete digital sovereignty as unrealistic. Instead, two-thirds define it in terms of what the consultancy calls "resilient interdependence" โ€“ accepting continued reliance on outside technology providers while trying to ensure those dependencies do not threaten critical operations. It's a pragmatic conclusion, though perhaps not surprising given how thoroughly tangled those dependencies have become. Digital sovereignty broadly refers to an organization's ability to retain control over its data, infrastructure, software, and critical technology operations, including where they are hosted and whose laws govern them. Capgemini surveyed 1,300 business and technology executives in April 2026, covering companies with more than $1 billion in annual revenue and government departments with budgets above $1 billion. Its separate Digital Sovereignty Index, based on an analysis of 866 organizations, found that 86 percent had significant exposure to foreign or externally controlled supply chains. Across the research, just 14 percent reported end-to-end visibility into dependencies throughout their wider technology ecosystems. Getting out of those relationships isn't necessarily straightforward either. Some 36 percent said moving away from a critical technology provider would take more than a year, while another 10 percent said they had no viable alternative. That leaves organizations trying to work out how much independence they actually need, rather than rebuilding their entire technology stacks closer to home. European respondents appeared particularly receptive to that compromise. Three-quarters defined sovereignty in terms of resilient interdependence, compared with half of respondents in the US. The UK also tended to view sovereignty through the lens of risk: 56 percent of British respondents primarily associated it with resilience and risk mitigation. This doesn't mean the subject has disappeared from the corporate agenda: 93 percent of respondents said it had been discussed at board level, and 44 percent ranked it among their board's top priorities. AI is adding another dependency for those boards to worry about. Three-quarters of organizations identified AI as a key focus of their sovereignty efforts, ahead of cloud infrastructure, cybersecurity, data, and software. Money presents another problem. Just under half said they would pay extra for sovereign technology. Among those willing to do so, the acceptable premium averaged 23 percent. Perhaps the more uncomfortable finding concerns what happens when those carefully accepted dependencies actually fail. Among organizations that had recently suffered an operational disruption, just 42 percent had contingency plans in place. Almost two-thirds of US organizations were prepared, compared with slightly more than a third in Europe and Asia-Pacific. Capgemini argues the answer isn't complete technological independence, but deciding which systems and capabilities matter enough to keep under tighter control, while building alternatives and recovery plans around everything else. Given that one in 10 organizations cannot currently replace a critical provider at all, this may be less a philosophical embrace of interdependence than an acknowledgment of where the exits actually are. ยฎ

โŒ