FilingsIQ
Back to Blog
Insights
trend of cloud computing

Cloud Computing Trends Every CIO and Technology Strategist Must Know

August 9, 202624 min read

Cloud Computing Trends Every CIO and Technology Strategist Must Know

Close-up of cloud data center GPU servers

Cloud computing in 2026 is an AI-first platform economy where hybrid architecture and centralized governance separate organizations that extract value from those that accumulate technical debt. The dominant trend of cloud computing right now is GenAI workload integration, and the first action you should take is a structured assessment of your AI workload readiness, your data locality posture, and your FinOps maturity.

Your three immediate priorities:

  • Audit which workloads are AI-ready and whether your current cloud architecture can support GPU-intensive inference and training at scale.
  • Centralize cost governance under a FinOps function or Cloud Center of Excellence (CCOE) before AI consumption spending becomes unmanageable.
  • Pilot at least one AI-native or neocloud service to understand the architectural and commercial trade-offs before committing at scale.

The Flexera 2026 State of the Cloud Report confirms that a majority of organizations operate hybrid cloud estates and that CCOE adoption has become widespread among organizations, yet a significant portion of cloud spend is estimated to be wasted. GenAI has accelerated every one of these dynamics.

Pro Tip: Before your next budget cycle, map every planned AI initiative to a specific cloud service and cost model. Vague "AI on cloud" line items are the fastest path to uncontrolled consumption spend.

Key Takeaways

Cloud computing in 2026 is an AI-first platform economy where hybrid architecture, centralized FinOps, and AI governance determine which organizations extract value and which accumulate costly technical debt.

PointDetails
GenAI is the primary growth driverQ2 cloud infrastructure revenues reached $143.4B, with GenAI cited as the main accelerator by Synergy Research Group.
Hybrid cloud is the default73% of organizations operate hybrid estates per Flexera 2026; governance and observability must span all environments.
Wasted spend is a solvable problemAn estimated 29% of cloud spend is wasted; FinOps and CCOE structures with named ownership are the proven fix.
AI governance cannot lag AI deploymentData lineage, model ownership, and access controls must be in place before AI workloads reach production at scale.
Upskilling beats hiring in most casesBLS data shows IT talent demand outpacing supply; internal upskilling in FinOps, Kubernetes, and AI governance is the faster path.

Table of Contents

What are the current trends in cloud computing?

The recent trends in cloud computing converge on a single structural shift: cloud is no longer primarily a compute-and-storage utility. It is the delivery platform for AI, and that changes almost everything about how you architect, govern, and pay for it. Below are the 11 trends that matter most right now, ranked by strategic urgency.

1. GenAI and AI-first cloud services Generative AI is the primary accelerator of cloud demand. Synergy Research Group reports that Q2 cloud infrastructure service revenues reached $143.4 billion, with trailing twelve-month revenues hitting $500 billion, and GenAI is the cited primary driver. Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform (GCP) have all restructured their service catalogs around AI-optimized compute, managed model APIs, and data pipeline tooling. Providers like CoreWeave, Anthropic, and OpenAI have introduced AI-native infrastructure and model services that are reshaping procurement decisions at the architectural level.

2. Hybrid and multi-cloud as the default architecture Hybrid cloud is not a transitional state. The Flexera 2026 State of the Cloud Report shows 73% of organizations operate hybrid estates, and most of those are multi-cloud by design or by acquisition history. The practical implication: your governance, security, and observability tooling must span environments, not just optimize within one hyperscaler.

3. AI-native clouds and neoclouds A new category of provider has emerged alongside the hyperscalers. Neocloud and AI-native cloud providers offer GPU-dense infrastructure, model-serving APIs, and developer tooling purpose-built for AI workloads. TechTarget's analysis identifies AI-native clouds as a distinct architectural option that organizations should evaluate when hyperscaler pricing or availability constraints limit AI workload performance.

4. Edge computing and micro-cloud edge Latency-sensitive workloads, including real-time inference, industrial IoT, and autonomous systems, are pushing compute to the edge. Micro-cloud edge deployments let organizations run containerized workloads closer to data sources while maintaining centralized management. TechTarget's 2026 trend analysis lists micro-cloud edge as a priority for organizations with distributed operations.

Micro-cloud edge unit near industrial IoT sensors

5. Serverless and hybrid serverless for agentic AI Serverless architectures have become the default for event-driven and agentic AI tasks. Hybrid serverless, where functions run across on-premises and cloud environments, reduces latency and addresses data residency requirements without sacrificing the operational simplicity of serverless models.

6. Containers, Kubernetes, and platform engineering Kubernetes remains the orchestration backbone for portable, scalable workloads. Platform engineering teams are building internal developer platforms on top of Kubernetes to provide consistent deployment pipelines across hybrid estates. This trend directly supports the portability and DevOps scalability that multi-cloud strategies require.

7. Data sovereignty and sovereign clouds Regulatory pressure is making data residency a first-order architectural decision. Sovereign cloud offerings from AWS, Azure, and GCP, as well as purpose-built sovereign providers, are growing in regulated industries including financial services, healthcare, and government. Gartner identifies cross-cloud strategies and industry cloud platforms as top strategic priorities, partly because they address sovereignty requirements.

8. FinOps evolution: from cost-cutting to value measurement FinOps has matured from a cost-reduction exercise into a discipline focused on unit economics and cost-per-service measurement. The Flexera report shows CCOE adoption at 71% and organizations increasingly measuring cloud value delivered to business units rather than just tracking spend.

9. Observability and data lineage for AI governance As AI workloads proliferate, observability must extend beyond infrastructure metrics to include model drift, inference latency, and data lineage. Organizations that cannot trace how data flows through their AI pipelines face both governance risk and regulatory exposure.

10. Sustainability and energy efficiency Data center energy consumption has become a board-level concern, driven by the power demands of GPU clusters for AI training. AWS, Azure, and GCP have all published sustainability commitments, and enterprise procurement teams are increasingly factoring carbon intensity into vendor selection.

11. Skills, upskilling, and organizational change The U.S. Bureau of Labor Statistics projects continued strong demand for computer and information technology occupations, and the gap between available cloud talent and organizational need is widening. Platform engineering, AI governance, and FinOps are the three roles most organizations are struggling to staff.

What macro forces are driving these cloud shifts?

Understanding why these trends are accelerating helps you determine which ones apply to your organization with urgency and which can wait.

Business drivers

GenAI value creation is the single largest business driver. Every major enterprise is under pressure to demonstrate AI ROI, and cloud is the fastest path to AI capability. SaaS proliferation has compounded this: organizations now run dozens of SaaS products, each generating data that AI models need to access, which creates data gravity problems that push more workloads to cloud. Unit-economics focus, driven by tighter capital markets, has made cost-per-service measurement a CFO priority rather than just an engineering concern.

Statista's AI market revenue data shows sustained high growth in AI-related spend globally, and that growth is translating directly into incremental cloud infrastructure demand. Organizations that delay AI cloud readiness are not just missing productivity gains; they are falling behind on the infrastructure investments that AI-at-scale requires.

Technical drivers

GPU and accelerator availability has become a genuine constraint. Training large language models and running high-throughput inference requires infrastructure that most on-premises environments cannot provide at competitive cost or speed. Data gravity, the tendency for data to attract compute rather than move to it, is pushing AI workloads toward the cloud environments where the data already lives. Network capacity, particularly private 5G and high-bandwidth interconnects, is enabling edge deployments that were impractical two years ago.

Regulatory and geopolitical drivers

Data sovereignty requirements are tightening across financial services, healthcare, and public sector. The EU's data localization rules, U.S. federal data handling requirements, and sector-specific regulations like HIPAA and SEC data retention rules are all pushing organizations toward private or sovereign cloud configurations. Gartner's analysis explicitly identifies industry cloud platforms as a top trend, partly because they bundle compliance controls that general-purpose hyperscaler services do not.

Geopolitical forces are adding a new dimension: geopatriation, the deliberate choice to host workloads in specific jurisdictions for political or supply-chain risk reasons, is now a real procurement criterion for multinational organizations. Trade policy uncertainty and concerns about cross-border data access are accelerating investment in regional cloud infrastructure.

How should you choose your cloud deployment architecture?

The choice of deployment model is now inseparable from your AI strategy and your regulatory posture. Each model carries distinct trade-offs across cost, complexity, security, and fit.

Practical definitions:

  • Hybrid cloud: A mix of on-premises infrastructure and one or more public cloud services, managed as a unified environment. Most organizations are here by default.
  • Multi-cloud: Using two or more public cloud providers, often to avoid lock-in, optimize for specific services, or meet regional requirements.
  • Private/sovereign cloud: Dedicated infrastructure, either on-premises or in a provider-managed facility, that meets strict data residency and compliance requirements.
  • AI-native/neocloud: Providers purpose-built for AI workloads, offering GPU-dense compute, model APIs, and developer tooling without the general-purpose overhead of hyperscalers.
DimensionHybrid cloudMulti-cloudPrivate/sovereignAI-native/neocloud
Cost and TCOModerate; on-prem capex plus cloud opex; rightsizing complexity grows with AIHigher management overhead; potential for arbitrage savings on specific servicesHigh upfront capex; predictable opex; best TCO for stable, high-volume workloadsCompetitive for GPU-intensive AI; pricing models still maturing
Maturity and adoptionDominant model; 73% of organizations per Flexera 2026Widely adopted; most hybrid estates are also multi-cloudGrowing in regulated industries; sovereign cloud offerings expandingEmerging; CoreWeave and similar providers gaining enterprise traction
Operational complexityHigh; requires unified management plane and consistent security policyVery high; tooling fragmentation is the primary riskModerate once established; staffing and procurement are the constraintsLow for AI workloads specifically; limited breadth outside AI use cases
Security and complianceRequires consistent policy enforcement across environmentsData classification and access control must span providersStrongest compliance posture; meets most sovereignty requirementsVaries; evaluate each provider's compliance certifications individually
Best-fit use casesGeneral enterprise workloads, legacy modernization, burst capacityAvoiding lock-in, best-of-breed service selection, geographic redundancyRegulated data, sensitive IP, government workloads, geopatriation requirementsLLM training, high-throughput inference, AI-native application development

Private and sovereign clouds make the most sense when your regulatory environment mandates data residency, when your data classification includes sensitive IP or personally identifiable information subject to strict handling rules, or when geopolitical risk makes hyperscaler dependency a board-level concern. Financial services firms subject to SEC data retention rules and healthcare organizations under HIPAA are the clearest candidates.

Pro Tip: Before deciding to repatriate workloads from public cloud, run a total cost of ownership model that includes staffing, hardware refresh cycles, and the opportunity cost of delayed AI capability. Repatriation often looks cheaper on paper than it proves in practice.

Which technologies are powering the latest cloud computing trends?

The enabling technologies beneath the trends are not independent choices. They form a dependency stack, and gaps in any layer create bottlenecks for the workloads above.

  • GPU and accelerator infrastructure: AWS (Trainium, Inferentia), Azure (NDv5 series), and GCP (TPUs) have all built proprietary accelerator lines alongside NVIDIA H100 and H200 availability. For most organizations, the practical question is not which accelerator to buy but how to access sufficient capacity through reserved instances, spot markets, or neocloud providers like CoreWeave. Model-serving at scale requires careful attention to inference latency, batch size optimization, and cost-per-token economics.

  • Containers and Kubernetes: Kubernetes has become the portability layer that makes multi-cloud and hybrid cloud operationally viable. Platform engineering teams build internal developer platforms on top of Kubernetes, providing standardized deployment pipelines, service meshes, and policy enforcement that work consistently across AWS, Azure, GCP, and on-premises environments. The Purdue Global analysis of cloud trends identifies containerization as a foundational enabler of the portability that modern hybrid estates require.

  • Serverless and hybrid serverless: AWS Lambda, Azure Functions, and GCP Cloud Run handle event-driven workloads without requiring infrastructure management. For agentic AI, where tasks are triggered by model outputs rather than scheduled jobs, serverless is often the most cost-effective execution model. Hybrid serverless extends this to on-premises environments, addressing latency and data residency constraints.

  • Edge computing and micro-cloud edge: Edge deployments reduce round-trip latency for real-time inference, industrial automation, and distributed data collection. Micro-cloud edge architectures run containerized workloads at the edge while maintaining centralized observability and policy management. The cost trade-off is real: edge hardware and connectivity add upfront cost, but the latency and data residency benefits often justify the investment for manufacturing, retail, and financial trading use cases.

  • 5G and networking: Private 5G networks are enabling edge deployments in environments where Wi-Fi reliability is insufficient, including factory floors and logistics hubs. High-bandwidth, low-latency connectivity is a prerequisite for real-time AI inference at the edge. Quantum computing remains a long-term potential enabler, with practical cloud-accessible quantum services from IBM and others still in early experimental stages for most enterprise use cases.

Statista's AI market revenue tracking reinforces that AI-related infrastructure investment is growing at a pace that makes these enabling technologies a near-term capital priority, not a future consideration.

How do security and compliance reshape your cloud strategy?

Security in a hybrid, AI-era cloud environment is not a checklist. It is an architectural discipline that must be embedded from the design stage, not bolted on after deployment.

Priority controls

Identity and entitlement management is the highest-leverage control in a multi-cloud estate. Overprivileged service accounts and inconsistent identity federation across providers are the most common vectors for lateral movement in cloud breaches. Implement least-privilege access policies using tools like AWS IAM, Azure Entra ID, and GCP IAM, and enforce them consistently across environments.

Cloud-to-cloud encryption and data classification matter more as AI workloads move data between services at high velocity. Data classification policies must be automated, not manual, and encryption must cover data in transit between cloud services, not just data at rest.

Data residency strategies are increasingly non-negotiable. Sovereign cloud offerings from hyperscalers and purpose-built sovereign providers give regulated organizations a path to compliance without sacrificing cloud economics entirely.

Practical governance

Policy-as-code tools like HashiCorp Sentinel, AWS Service Control Policies, and Azure Policy let you enforce governance rules programmatically across your estate. Data lineage tooling, including Apache Atlas and cloud-native options like AWS Glue Data Catalog, provides the audit trail that AI governance and regulatory compliance both require.

AI model governance deserves specific attention. You need documented ownership for every model in production, validation and testing protocols before deployment, access controls on training data, and lifecycle management processes that include model retirement.

Quick wins for AI workload risk reduction

  • Enforce MFA and conditional access on all accounts with access to AI training data.
  • Classify all training datasets before they enter any AI pipeline.
  • Implement automated cost anomaly detection to catch runaway AI training jobs early.
  • Require data lineage documentation for any model deployed to production.
  • Conduct a privilege audit of all service accounts used by AI workloads quarterly.

TechTarget's analysis of 2026 cloud decisions confirms that data sovereignty and AI governance are now primary architectural drivers, not secondary compliance considerations.

How do AI workloads change your cloud cost structure?

The business impact of the current cloud phase is most visible in cost structures. AI workloads are consumption-intensive, unpredictable, and difficult to rightsize using traditional cloud cost management approaches.

  • Wasted spend remains high: TechTarget's coverage of the Flexera report puts estimated wasted cloud spend at a significant level. AI workloads make this worse because GPU instances are expensive, and idle or underutilized GPU time is far more costly than idle CPU time.

  • Consumption-based pricing complexity: Hyperscalers price AI services on tokens, API calls, and GPU-hours, each with different discount structures. Committed use discounts and reserved instances help, but they require accurate demand forecasting, which is harder for AI workloads than for stable application workloads.

  • Vendor lock-in risk: Deep integration with a single hyperscaler's AI services, such as Azure OpenAI, AWS Bedrock, or GCP Vertex AI, creates switching costs that compound over time. Neocloud providers like CoreWeave offer an alternative for GPU-intensive workloads, but they introduce their own integration complexity.

  • Organizational fragmentation: When AI projects are funded and managed by individual business units rather than a central platform team, cost governance breaks down. The 12-percentage-point increase in organizations reporting value delivered to business units, cited in the Flexera/TechTarget analysis, reflects organizations that have solved this fragmentation problem through centralized FinOps and CCOE structures.

Pro Tip: Align your finance, engineering, and product teams around a single cost-per-service metric for each AI workload. When everyone sees the same number, rightsizing decisions happen faster and budget conversations become more productive.

What operational practices turn cloud strategy into repeatable capability?

Strategy without operational discipline produces pilots that never scale. The organizations extracting the most value from cloud are those that have built repeatable operational practices around FinOps, platform engineering, and AI governance.

Establishing FinOps and CCOE

  1. Define decision rights clearly: the CCOE sets policy and standards; FinOps practitioners enforce cost accountability at the team level.
  2. Integrate FinOps into the procurement cycle so committed discounts and reserved instance purchases are coordinated, not ad hoc.
  3. Assign a named FinOps owner for every AI workload, with authority to pause or resize resources.
  4. Report cost-per-service metrics to business unit leaders monthly, not just to engineering.
  5. Review CCOE policies quarterly to account for new AI services and pricing model changes.

Platform engineering

A well-designed internal developer platform reduces the cognitive load on application teams and enforces consistent security and cost policies by default. Build your platform on Kubernetes with standardized CI/CD pipelines, service mesh policies, and observability instrumentation baked in. The goal is that deploying a new AI service should not require a team to make security or cost decisions from scratch.

Observability and telemetry

For cloud and AI workloads, measure:

  • Infrastructure latency and throughput per service.
  • Cost-per-service and cost-per-inference for AI workloads.
  • Model drift and prediction confidence over time.
  • Data pipeline freshness and lineage completeness.

Tools like Datadog, Grafana, and cloud-native options (AWS CloudWatch, Azure Monitor, GCP Cloud Operations) provide the telemetry foundation. Model-specific observability requires additional tooling, such as MLflow or Weights & Biases, for drift detection and experiment tracking.

AI governance checklist

  • Assign a named owner and a documented use case for every model in production.
  • Require a validation report before any model moves from staging to production.
  • Implement access controls on training data with audit logging.
  • Schedule quarterly model reviews to assess drift, performance degradation, and compliance.
  • Document the data lineage for every training dataset.

Pro Tip: The BLS occupational outlook shows sustained demand for IT roles outpacing supply. Rather than competing for scarce external talent, invest in upskilling existing engineers in FinOps, Kubernetes, and AI governance. Internal candidates already understand your architecture and your compliance requirements.

The Flexera 2026 data showing CCOE adoption at 71% suggests that the organizations ahead of the curve have already made this operational investment. Those that have not are managing AI workloads reactively.

What do the market numbers tell you about cloud's trajectory?

The market data behind the latest cloud computing trends gives you the context to make a credible internal case for investment.

Synergy Research Group reports that Q2 cloud infrastructure service revenues reached $143.4 billion, with trailing twelve-month revenues at approximately $500 billion. Synergy describes this as the highest growth rate in eight years, with GenAI identified as the primary accelerator.

MetricValueSource
Q2 cloud infrastructure service revenues$143.4 billionSynergy Research Group
Trailing twelve-month cloud revenues~$500 billionSynergy Research Group
Organizations operating hybrid cloud estates73%Flexera 2026 State of the Cloud
CCOE adoption among surveyed organizations71%Flexera 2026 State of the Cloud
Estimated wasted cloud spend29%Flexera/TechTarget
GenAI public cloud usage among organizations58%Flexera 2026 State of the Cloud

AWS, Azure, and GCP continue to hold the dominant share of cloud infrastructure revenue, but neocloud and specialist providers are growing faster in percentage terms, particularly for GPU-intensive AI workloads. CoreWeave's rapid growth in the AI infrastructure segment illustrates how quickly specialist providers can capture share when hyperscaler capacity or pricing creates an opening.

Geographically, North America remains the largest cloud market, but Asia-Pacific growth rates are outpacing other regions, driven by manufacturing automation, financial services digitization, and government cloud programs. For capacity planning, this means hyperscaler availability in specific regions is a real constraint for organizations with distributed operations.

Statista's AI market revenue data shows that AI-related spending growth is sustained, not a single-year spike, which supports the case for multi-year cloud infrastructure investment rather than point-in-time pilots.

What do the market numbers tell you about cloud's trajectory? — overview diagram

A practical roadmap for CIOs and CTOs: five steps to act on now

Converting this briefing into a plan requires sequencing. Here is a realistic five-step roadmap with time estimates.

  1. Assess (weeks 1–8): Inventory all AI workloads and planned AI initiatives. Map data locality for each workload. Audit your current cloud posture: which environments, which providers, which governance gaps. Identify the top three cost inefficiencies and the top three security gaps.

  2. Pilot (months 3–8): Run structured pilots of AI-native services on AWS Bedrock, Azure OpenAI, GCP Vertex AI, or a neocloud provider. Test hybrid serverless for at least one event-driven AI use case. Evaluate one edge deployment if you have latency-sensitive workloads. Define success criteria before each pilot starts.

  3. Govern (months 2–4, then continuous): Stand up or formalize your FinOps function and CCOE. Implement policy-as-code for security and cost guardrails. Establish AI governance ownership and documentation requirements. This phase runs in parallel with piloting, not after it.

  4. Scale (incremental quarters): Platformize the pilots that meet their success criteria. Build or extend your internal developer platform to cover AI workload deployment. Centralize observability across all environments. Expand committed use discounts based on validated consumption patterns from pilots.

  5. Measure (recurring cadence): Report unit economics and cost-per-service metrics to business unit leaders each quarter. Track model performance and drift monthly. Review CCOE policies and FinOps benchmarks against the Flexera State of the Cloud annually to calibrate your maturity.

Key milestones to track:

  • AI workload inventory complete by end of week 8.
  • At least one AI-native pilot with defined success metrics underway by month 4.
  • FinOps function with named ownership operational by month 3.
  • Cost-per-service reporting to business units live by month 6.

How this article compiled its findings

This article draws on a combination of analyst survey data, market revenue reports, and technology journalism to triangulate the trends and recommendations presented.

Primary sources used:

  • Flexera 2026 State of the Cloud Report: The most comprehensive annual survey of enterprise cloud adoption, covering hybrid prevalence, FinOps maturity, CCOE adoption, and AI usage. Trusted for its large sample size and consistent year-over-year methodology.
  • Synergy Research Group: Quarterly market revenue data for cloud infrastructure services, widely cited by analysts and journalists for its methodology and consistency. Used for market size and growth rate figures.
  • Gartner: Analyst press releases and conference coverage identifying top strategic cloud trends for infrastructure and operations leaders. Used for trend framing and strategic prioritization.
  • TechTarget: Editorial coverage of the Flexera report and original analyst commentary on 2026 cloud decisions. Used for wasted spend figures and AI-native cloud analysis.
  • Statista: AI market revenue datasets used to contextualize the scale of AI-related spending driving cloud demand.
  • U.S. Bureau of Labor Statistics: Occupational outlook data for computer and information technology roles, used to support workforce and upskilling claims.

Methodology note: Findings were triangulated across survey data (Flexera), market revenue data (Synergy Research), and analyst opinion (Gartner, TechTarget) to identify trends with convergent support rather than single-source claims. Market size estimates vary by vendor methodology; readers should consult the source links for raw data and definitions.

The governance gap is the real cloud problem

The most underappreciated aspect of the current cloud moment is not the technology. It is the governance gap between how fast AI workloads are being deployed and how slowly organizations are building the oversight structures to manage them.

Every major hyperscaler, AWS, Azure, and GCP, has made it genuinely easy to spin up a large language model API call, connect it to a data source, and put it in front of users in days. The speed is real. The problem is that most organizations are doing this without documented data lineage, without named model ownership, and without cost controls that account for token-level consumption. The result is a new category of technical debt that combines the worst of shadow IT with the cost unpredictability of unmanaged cloud spend.

The organizations that will look back on this period as a competitive advantage are not the ones that moved fastest on AI. They are the ones that moved fast enough on AI while building the FinOps, CCOE, and AI governance structures in parallel. The Flexera data showing strong CCOE adoption is encouraging, but CCOE adoption and CCOE effectiveness are different things. A CCOE that does not have decision rights over AI workload procurement is a reporting function, not a governance function.

The practical warning: do not let the urgency of AI pilots override the discipline of governance setup. A three-month delay to establish proper cost controls and data lineage documentation will save you from a much more expensive remediation 18 months from now.

Sources

The following sources provide the primary data and analysis behind this article. Each is worth bookmarking for ongoing strategy work.

FAQ

What are the current trends in cloud computing?

The dominant trends are GenAI integration, hybrid and multi-cloud architecture, AI-native and neocloud providers, data sovereignty, FinOps maturity, and edge computing. Synergy Research Group reports trailing twelve-month cloud revenues of approximately $500 billion, with GenAI as the primary growth driver.

What are the key cloud trends for 2026?

AI-first cloud services, sovereign cloud adoption in regulated industries, FinOps evolution toward unit economics, and platform engineering for hybrid estates are the highest-priority trends for 2026, per Flexera, Gartner, and TechTarget analysis.

Is cloud computing worth it in 2026?

Yes, but governance determines the return. An estimated 29% of cloud spend is wasted, and organizations with mature FinOps and CCOE structures report significantly higher value delivered to business units than those without centralized governance.

Will AI replace cloud computing?

No. AI is accelerating cloud adoption, not replacing it. GenAI workloads require the GPU infrastructure, managed APIs, and global data pipelines that cloud providers deliver, making cloud the foundational platform for AI rather than a competing model.

How is cloud computing evolving for regulated industries?

Regulated industries are driving growth in private and sovereign cloud deployments, where data residency and compliance requirements cannot be met by standard public cloud configurations. Gartner identifies industry cloud platforms as a top strategic trend specifically because they bundle the compliance controls that financial services, healthcare, and government organizations require.

Recommended

Related insights

Ready to analyze filings faster?

Try FilingsIQ free and turn SEC filings into actionable research in minutes.