Operations | Monitoring | ITSM | DevOps | Cloud

Neil Sawyer, Senior Vice President and Managing Director for HP Europe, Middle East and Africa, recently published “Scaling AI Without Losing Control” in Forbes Business Council. His starting point will be familiar to any finance leader. AI pilots looked affordable on pay-per-token and pay-per-query pricing, and that same pricing can get far more expensive at enterprise scale. Gartner forecasts worldwide AI spending will reach $2.7 trillion in 2026, up 49.5%.

AI infrastructure costs span four buying tiers in 2026: API-only teams spend hundreds to tens of thousands per month on tokens, GPU renters typically pay $2 to $10 per GPU-hour by chip class, committed-capacity buyers sign six-to-eight-figure reservation contracts, and owners spend millions per rack. The stack has six layers, and most budgets underestimate everything below the GPU line.

The best open source LLMs by family: DeepSeek V4 for frontier reasoning under MIT, Qwen3.8 and Gemma 4 for clean Apache 2.0 licensing, GLM-5.3 for coding, Kimi K3 for long context, Llama 4 for single-GPU scale. The real ranking depends on your deployment lane and token volume, and this guide prices all three lanes. At CloudZero, Bill Buckley, our SVP of Engineering, gives every engineer a $5,000 monthly AI token budget and published the math behind it.

You can now see which of your Multi-Region Cloud Storage buckets have cross-location read charges worth acting on, and start with the ones where a cache would save the most. It runs automatically for every organization with GCP Cloud Storage, so there’s nothing to set up. Google bills network data transfer when a Google Cloud service in one location pulls data from a Multi-Region bucket in another.

Most cost questions have more than one layer. Which team spent the most, which services drove it, and which accounts were behind those services? Previously, following that path meant changing dimensions, adjusting filters, and re-running the query at every step. Multi-dimensional drill-down has been one of the most-requested features in Explorer. The team shipped two-level group-by earlier this year, collected feedback, and kept going. Now the path goes eight levels deep.

Across a same-store panel of 422 CloudZero customer organizations, AI reached 3.02% of the median company's cloud bill in September 2026, up 37 basis points from 2.66% in August, the largest monthly gain since we began tracking. The 75th percentile rose to 12.55%. The share of organizations spending at least $1,000 a month on AI barely moved, to 68.0%. Companies already spending drove the growth. Last month we called the median the least informative number in this report. September proved us wrong.

Finance teams reconcile cloud spend period by period. They want each month, week, or day in its own column, so they can scan across a row and see how a service or team changed over time. Explorer’s Aggregate view already answers “what changed and by how much.” But when the question is “what did we spend in June, July, and August, line by line,” that summary needs to become a grid.

Kimi API pricing, per million tokens: the flagship Kimi K3 costs $3 input and $15 output with a $0.30 cache-hit rate and 1M context. Kimi K2.6 and the coding-tuned K2.7 Code both run $0.95/$4.00 on 256K context. Kimi K2.5 and the legacy V1 family were retired August 31, 2026.

The question comes up on the 10th, the 15th, and again on the 25th. Where is AI spend going to end up this month? The invoice won’t tell you until it’s closes, and by then there’s nothing left to forecast. “If I’m looking at this on the 15th, I want to know where we’re going to land.” That’s how a finance lead put it during a persona session in September, and it’sthe whole job. You have half a month of real usage behind you.

Claude Opus pricing is $4 per million input tokens and $20 per million output tokens on Claude Opus 5.5, the current model, with cache reads at $0.20 and batch jobs at $2/$10. Opus 5 and the legacy 4-series bill at $5/$25. The 1M context window carries no surcharge. Every Opus model Anthropic shipped in 2026 held the same line: $5 in, $25 out, per million tokens. Opus 4.6 in February, 4.7 in April, 4.8 in May, Opus 5 in July. Four releases, one price. On September 22, 2026, the line broke.

Most people who open CloudZero care about one slice of the spend, like their team, their product, or their region. A View gives them that slice in one click, with the grouping and filters already set, so nobody has to rebuild the same Explorer query every week. Views now work for everyone in your organization, including people with scoped access.

Most AI spend comes in with no tags and no owner attached. Your provider console shows total spend, maybe broken out by API key or model. It won’t tell you that the sales team spent $1,700 on Claude this week, let alone what the work was. And the problem is growing. McKinsey found that 56% of organizations now use AI in three or more business functions. More teams means more spend, and most companies respond with a spending cap. Set it too low and you slow down the work you wanted AI to help with.

Most people who use CloudZero spend their time in one or two places. For some it’s AI Signals, and for others it’s Optimize or Anomalies. If Explorer isn’t one of those places, every sign-in starts with a click to get where you need to be. Dates and numbers are another friction. A date like 04/07 means April 7 in the US and July 4 in much of Europe. When the platform shows a format your team doesn’t use, you end up having to convert each value before you can work with it.

AI spend now comes from every department, and it can double in a week without anyone deciding it should. The invoice arrives after the month closes. By then the usual response is a spend cap, which slows every team, including the ones getting real work done with AI. You need to know about spend that breaks its normal pattern while there’s still time to act. The alert should reach the person who can act on it, with proper context and detail.