Operations | Monitoring | ITSM | DevOps | Cloud

The discussion around AI in infrastructure and operations has become increasingly model-centric. Teams want to know what model a platform uses, how current it is, how much reasoning capacity it has, and how quickly it can be updated as the model landscape shifts. Those are reasonable questions, but they tend to arrive too early. In production operations, the more consequential question is what happens to the data before any model is asked to interpret it.

The recent unveiling of Anthropic’s Claude Mythos preview has radically shifted the cybersecurity landscape. We are now in an era where AI can autonomously discover and exploit zero-day vulnerabilities in mature codebases at machine speed.

Anthropic just shipped an Enterprise Analytics API with user-level token and cost data. Today, we're shipping the CloudZero adapter that maps that data to teams, budgets, and cost centers — so Claude spend gets the same accountability as the rest of your stack. Anthropic released the first beta of its Enterprise Analytics API this week. Admins can pull token usage and dollar cost through a programmatic endpoint, broken down by user, model, context window, region, and product surface.

AI has massively accelerated code deployment. In fact, since the introduction of agentic coding, GitHub has seen exponential growth in PRs, commits, and new repos. What they originally predicted would require 10X capacity, they’re now estimating it’s going to require 30X capacity, and the biggest driver is agentic development. Companies across industries are building agentic pipelines to ship features faster than ever before. That acceleration isn’t without risk.

I've had this same conversation with 60+ engineering teams in the last six months. A team adopts AI tooling. One developer figures out how to use it well, builds up a vault of skills, MCP configs, and slash commands that 10x their output. The rest of the team has whatever they can scavenge from a shared Notion doc.

The first time an AI assistant suggests "restart the service" during a live incident and nobody on the bridge can tell whether that suggestion came from a current runbook, a stale wiki page, or thin air, you stop caring about model benchmarks. You start caring about what the agent actually knew, where that knowledge came from, and whether you can trust the chain of reasoning behind it.

When people talk about trusting AI, they usually focus on the interface. It summarizes and uses confident language with a level of clarity that feels reliable. But that’s all window dressing. None of it builds trust. Trust doesn’t come from what the AI says. A verifiable record of what the AI did makes it trustworthy.

Data is almost always scattered across too many tools. Usually, if you want to see it all in one place, you're stuck building messy pipelines or paying for a warehouse you don't really want. SquaredUp is a window into all those tools. It lets you see what’s happening across your entire stack in real time without moving any of the data. Think of it as a universal translator that lets your tools talk to each other so you can stop the manual digging and just see the big picture.