Operations | Monitoring | ITSM | DevOps | Cloud

CUR 2.0 is generally available and on by default, so every AWS connection you make now starts with the richest billing data AWS offers. That richness is important. CUR 2.0 carries AWS caller identity, which is what puts Bedrock and other AI spend on the role that drove it instead of leaving it as one number in your bill. It also populates AWS Account Name automatically. Both of those are yours the moment the connection is live. Getting there is a single step now.

GitHub Copilot Enterprise pricing is $39 per user per month, and since June 1, 2026, each seat includes $39 in monthly GitHub AI Credits, pooled across your whole organization and consumed by token usage at per-model rates. The seat price is fixed. The bill is not: usage beyond the pooled credits is charged on top, which is why the real Enterprise question in 2026 isn't the price per seat. It's your engineers' token consumption.

If your company runs on Google Workspace, your team lives in Google Chat. That is where the standup happens and where threads turn into decisions. Cost alerts can now go there too. This is relevant because an alert only does something if it reaches people in a place where they can talk about it. Email is great for a record but not great for a reaction. An anomaly notification sitting in an inbox waits for that person to open it, decide it is real, and then go tell everybody else.

Telemetry streams carry the unit metrics behind every cost-per-unit number you report. Now each one can say in plain language what it measures. You can call a stream whatever you want to: “MCP tool calls” or “Checkout transactions” or “Documents processed.” Spaces, capitals, and punctuation all work, and you can change the name whenever the metric’s purpose gets clearer. The identifier the pipeline uses stays exactly where it is.

AI cost governance is the set of policies and controls that keep AI spend predictable and attributable: budget caps and token quotas set before deployment, prompt caching to cut repeat token costs, hard limits on reasoning steps and tool calls, and unified allocation so every dollar maps to a team, feature, or customer. Governance fails when it's advisory. It works when the caps are enforced in the platform and someone owns the number.

CloudZero Explorer answers a cost question in two parts. The chart shows what your spend did and the table underneath shows which service, account, or team did it. Until now, the chart pushed the table below the fold, and actions like creating a View or checking Anomalies were buried multiple clicks deep. Now the chart and table share the screen and a new right rail puts Favorites, Views, Anomalies and Insights one click away without covering your data.

AI costs are changing. As noted by research from EY, outputs that cost just $0.04 in 2023 now cost $1.20, a 30x increase over just three years. It’s worth noting that task operations and complexity have also changed. In 2023, the process was simple. Users input a question, retrieval engines found relevant data, and AI models returned a response. Today, many tasks are handled by orchestrated AI agents capable of much more complex reasoning and analysis.

When the changelog doesn’t keep pace with the product, two things can happen. One, you keep working around something that was already fixed weeks ago. Or two, a behavior changes, you assume it’s a bug, and you spend an afternoon on triage and a support ticket before learning it was an intentional improvement. CloudZero now ships around 30 improvements a week, a pace driven by the Next Gen Platform and the AI-first approach we’re building for our customers.

Anthropic, the company behind Claude, ran the most honest experiment in agentic AI: they gave a version of their own model $1,000, a small fridge in the office lunchroom, and one job. Run a shop. Make a profit. They named it Claudius. Claudius did not make a profit.

Instead of building a separate role for every team, region, or department, admins can create a single role that automatically personalizes access for each user based on their SSO attributes. Someone moves teams or a new group gets created, and the new access takes effect at their next login with no CloudZero configuration. As AI spend grows, more companies are looking to give teams visibility into their own AI costs without exposing every individual’s usage across the org.