Operations | Monitoring | ITSM | DevOps | Cloud

Shipped: Views now work for every access level

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.

Shipped: See what your AI spend is actually paying for

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.

Shipped: Start every session where your work lives

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.

Why engineers ignore cloud cost governance (and fixes)

Discover why engineers ignore cloud cost governance and how to build developer cost accountability. Learn how Harness helps empower engineering teams. Engineers often overlook cloud costs due to friction in traditional FinOps tools and a lack of real-time visibility. By embedding automated guardrails and shift-left cost insights into developer workflows, organizations can drive accountability without slowing velocity.

Shipped: Get alerted when AI spend spikes, with the cause attached

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.