惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Application and Cybersecurity Blog
Application and Cybersecurity Blog
A
About on SuperTechFans
S
SegmentFault 最新的问题
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Help Net Security
Help Net Security
有赞技术团队
有赞技术团队
博客园 - 【当耐特】
O
OpenAI News
美团技术团队
月光博客
月光博客
Apple Machine Learning Research
Apple Machine Learning Research
Schneier on Security
Schneier on Security
Webroot Blog
Webroot Blog
Cyberwarzone
Cyberwarzone
Hacker News - Newest:
Hacker News - Newest: "LLM"
Google Online Security Blog
Google Online Security Blog
T
Tenable Blog
S
Security Affairs
博客园_首页
S
Schneier on Security
Security Latest
Security Latest
T
Threat Research - Cisco Blogs
T
Tailwind CSS Blog
大猫的无限游戏
大猫的无限游戏
Spread Privacy
Spread Privacy
量子位
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
K
Kaspersky official blog
Hugging Face - Blog
Hugging Face - Blog
TaoSecurity Blog
TaoSecurity Blog
博客园 - 聂微东
Vercel News
Vercel News
M
MIT News - Artificial intelligence
T
Troy Hunt's Blog
B
Blog
MongoDB | Blog
MongoDB | Blog
Martin Fowler
Martin Fowler
Attack and Defense Labs
Attack and Defense Labs
L
LINUX DO - 最新话题
D
DataBreaches.Net
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
Stack Overflow Blog
Stack Overflow Blog
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
博客园 - Franky
W
WeLiveSecurity
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
F
Fortinet All Blogs
www.infosecurity-magazine.com
www.infosecurity-magazine.com
C
Check Point Blog
H
Hacker News: Front Page

Swift for Visual Studio Code comes to Open VSX Registry | InfoWorld

Notion courts developers with a platform for AI agents and workflow automation Using continuous purple teaming to protect fast-paced enterprise environments A better way to work with SQL Server Evidence-driven workflows: Rethinking enterprise process design AWS debuts Graviton-powered Redshift RG instances to cut analytics costs SAP’s AI promises last year? Most are still rolling out First look: Lemonade serves up local AI with limitations GitLab CEO sees developer tool bill increasing 100-fold Red Hat adds support for agentic AI development What’s new and exciting in JDK 26 Kill the loading spinner with local-first data and reactive SQL A networking revolution at AWS Tokenmaxxing is super dumb How to add AI to an existing product (without annoying users) Your AI doesn’t need another database What happens when engineering teams reorganize around AI agents Python isn’t always easy When cloud giants meddle in markets 12 model-level deep cuts to slash AI training costs The best new features in Python 3.15 Teradata launches platform for enterprise AI agents moving beyond pilots Three skills that matter when AI handles the coding MongoDB targets AI’s retrieval problem Building AI apps and agents with Microsoft Foundry Designing front-end systems for cloud failure No, AI won’t destroy software development jobs Diskless databases: What happens when storage isn’t the bottleneck Vibe coding or spec-driven development? The agentic AI distraction Vibe coding or spec-driven development? How to choose Cloud providers are blinded by agentic AI SAP to acquire data lakehouse vendor Dremio Small language models: Rethinking enterprise AI architecture Making AI work through eval hygiene Improving AI agents through better evaluations AI in the cloud is easy but expensive Running AI in the cloud is easy – and expensive Making AI work for databases Harness teams of agentic coders with Squad Harness teams of coding agents with Squad Oracle NetSuite announces AI coding skills for SuiteCloud developers Why it’s so hard to create stand-alone Python apps A new challenge for software product managers The hidden cost of front-end complexity GitHub shifts Copilot to usage-based billing, signaling a new cost model for enterprise AI tools OpenAI’s Symphony spec pushes coding agents from prompts to orchestration The front-end architecture trilemma: Reactivity vs. hypermedia vs. local-first apps Enterprise AI is missing the business core The best JavaScript certifications for getting hired Google begins putting the guardrails on agentic AI Why world models are AI’s next frontier Where to begin a cloud career Google pitches Agentic Data Cloud to help enterprises turn data into context for AI agents How open source ideals must expand for AI Is your Node.js project really secure? How I doubled my GPU efficiency without buying a single new card SpaceX secures option to acquire AI coding startup Cursor for $60B Google’s Gemma 4 shines on local systems – both big and small AI is upending the SaaS game How AI is upending SaaS tools Snowflake offers help to users and builders of AI agents From the engine room to the bridge: What the modern leadership shift means for architects like me Addressing the challenges of unstructured data governance for AI The cookbook for safe, powerful agents Enterprises are rethinking Kubernetes GitHub pauses new Copilot sign-ups as agentic AI strains infrastructure Best practices for building agentic systems Making agents dull Oracle delivers semantic search without LLMs When cloud giants neglect resilience Exciting Python features are on the way Ease into Azure Kubernetes Application Network The agent tier: Rethinking runtime architecture for context-driven enterprise workflows The two-pass compiler is back – this time, it’s fixing AI code generation MuleSoft Agent Fabric adds new ways to keep AI agents in line Salesforce launches Headless 360 to support agent‑first enterprise workflows Tap into the AI APIs of Google Chrome and Microsoft Edge Where will developer wisdom come from? GitHub adds Stacked PRs to speed complex code reviews HTMX 4.0: Hypermedia finds a new gear Google Cloud introduces QueryData to help AI agents create reliable database queries Hands-on with the Google Agent Development Kit Are AI certifications worth the investment? AWS targets AI agent sprawl with new Bedrock Agent Registry Cloud degrees are moving online Swift for Visual Studio Code comes to Open VSX Registry AI agents aren't failing. The coordination layer is failing How Agile practices ensure quality in GenAI-assisted development Anthropic rolls out Claude Managed Agents Microsoft’s reauthentication snafu cuts off developers globally Meta’s Muse Spark: a smaller, faster AI model for broad app deployment Bringing databases and Kubernetes together Rethinking Angular forms: A state-first perspective Minimus Welcomes Yael Nardi as CBO to Facilitate Strategic Growth Microsoft announces end of support for ASP.NET Core 2.3 Get started with Python’s new frozendict type AWS turns its S3 storage service into a file system for AI agents Microsoft’s new Agent Governance Toolkit targets top OWASP risks for AI agents The winners and losers of AI coding GitHub Copilot CLI adds Rubber Duck review agent
The hyperscalers are pricing themselves out of AI workloads
2026-04-14 · via Swift for Visual Studio Code comes to Open VSX Registry | InfoWorld

David Linthicum

opinion

Apr 14, 20266 mins

Large cloud providers still want the market to believe that AI infrastructure is a premium business where customers pay premium prices. That argument worked when buyers had few alternatives, when access to advanced GPUs was restricted, and the operational maturity of the hyperscalers created an advantage that smaller competitors could not easily match. However, the market is rapidly changing, making economics unavoidable. Recent comparisons show that neocloud providers are often much cheaper than major public clouds, with hyperscalers costing about three times to six times as much as specialized competitors for similar compute capacity.

That gap is not a rounding error. Enterprises cannot dismiss this as just the cost of doing business with a trusted vendor. The bills are significant enough to influence architectural choices, vendor strategies, and even the locations of AI innovation. One commonly cited example in current pricing comparisons shows that NVIDIA H100-class compute costs about $2.01 per hour on Spheron versus approximately $6.88 per hour on AWS for a similar workload category. That is roughly a difference of 3.4 times for comparable AI processing. Whether a specific enterprise secures better rates is almost irrelevant. The market now knows that lower-cost alternatives exist, and knowledge changes behavior.

In addition to neoclouds, private clouds, sovereign clouds, and even on-premises GPU strategies are becoming more appealing as buyers increasingly view AI infrastructure as a long-term operating expense rather than a short-term experiment. Once that shift occurs, even small differences in unit costs become strategic. Large cost gaps become hard to justify. That’s when a premium vendor stops appearing premium and begins to seem overpriced.

When ‘premium’ isn’t enough

For years, hyperscalers benefited from a straightforward value proposition. They could provide global reach, mature security controls, integrated tools, elastic capacity, and an ecosystem that minimized operational friction. These factors still matter and remain valuable. However, AI is revealing a flaw in the traditional cloud pricing model. When compute is the core and can be sourced elsewhere at a significantly lower cost, the value of the surrounding ecosystem must be exceptional to justify the markup. Today, in many cases, it is not.

This is where hyperscalers are making a strategic mistake. They seem to assume that AI buyers will continue to accept the same pricing strategies that worked for traditional cloud migrations. That assumption is risky. AI buyers are not just lifting and shifting old enterprise applications. They are training, fine-tuning, and deploying models in environments where utilization, throughput, latency, and token economics are monitored in real time. Their boards are asking tougher questions. Their investors are asking tougher questions. Their finance teams are asking the toughest questions of all. If the answer is that the enterprise is paying several times more for the same class of compute because it’s easier to stick with a familiar brand, that decision won’t go over well.

The real issue is not that AWS, Microsoft Azure, and Google Cloud are expensive in absolute terms. The issue is that they are becoming expensive relative to an expanding set of credible alternatives. That distinction matters. Buyers will always pay more for better outcomes. They will resist paying much more for little or no proportional benefit. In AI, proportional benefit is increasingly difficult for the hyperscalers to prove. A customer does not receive higher model accuracy just because the invoice came from a household cloud brand. A workload does not become inherently more strategic because it runs in a famous control plane. The chip is still the chip. The cluster is still the cluster. The economics are still the economics.

AI buyers become more rational

The next phase of the AI market won’t be about who can generate the most headlines. Instead, success will be based on consistently delivering reliable performance at sustainable costs. This shift favors disciplined operators and providers that are optimized for GPU availability, efficient scheduling, and simple commercial models. It also benefits enterprises willing to blend different environments rather than always relying on the largest cloud vendor for every workload.

The conversation is moving away from simple cloud preference and toward workload placement strategies. Enterprises are becoming more comfortable with the idea that different AI jobs belong in different places. Some workloads will stay on hyperscalers because the integration benefits are real. Others will move to private cloud because security, data gravity, or regulatory concerns demand it. Still others will land on sovereign platforms because national and industry-specific requirements leave no other option. A growing number will be routed to neoclouds because the price-performance equation is too compelling to ignore.

This isn’t a rejection of hyperscalers. It’s a rejection of careless pricing. The biggest cloud providers will continue to be highly important for AI. However, their role is shifting from the default choice to one option among many. This represents a major strategic downgrade, driven not by technological weakness but by pricing practices.

The market rewards discipline

The cloud industry has experienced this cycle before. Established companies believe that their size safeguards them, that customers prioritize convenience above everything else, and that their pricing power is everlasting. Then, a new group of competitors appears with a sharper value proposition and fewer outdated assumptions. Initially, incumbents dismiss them as niche players. However, these players improve, specialize, and attract the most cost-conscious innovators. By the time the incumbents take action, the market has already shifted.

That is exactly the risk hyperscalers face in AI today. If they continue treating GPU-driven workloads as a way to maintain high margins across compute, storage, networking, and managed services, they will train customers to look elsewhere. Once that becomes a habit, it will be hard to change. Customers who develop procurement discipline around lower-cost AI infrastructure won’t quickly return simply because a hyperscaler finally cuts prices.

The next winners in AI infrastructure may be the providers that understand a hard truth: When the market is scaling at this speed, adoption matters more than margin preservation. If AWS, Microsoft, and Google don’t learn that lesson quickly, they might find that they weren’t undercut by competitors, but that they priced themselves out all on their own.

David Linthicum

David S. Linthicum is an internationally recognized industry expert and thought leader. Dave has authored 13 books on computing, the latest of which is An Insider’s Guide to Cloud Computing. Dave’s industry experience includes tenures as CTO and CEO of several successful software companies, and upper-level management positions in Fortune 100 companies. He keynotes leading technology conferences on cloud computing, SOA, enterprise application integration, and enterprise architecture. Dave writes the Cloud Insider blog for InfoWorld. His views are his own.

More from this author