Operations | Monitoring | ITSM | DevOps | Cloud

Our Results Daemon processes about 92 million messages a day. We recently rewrote it from Node.js to Go, and we let Claude Code write it. We wanted to know whether we could trust an agentic rewrite for a critical, high-throughput production service rather than a prototype. It shipped with zero incidents, a 70% reduction in running pods, and a lighter database load.

The U.S. government has cataloged over 1,700 active AI use cases, and nearly 90% of federal agencies are already using or planning to use AI. The European Commission has disclosed nearly 1,500 AI use cases across EU member states. With over 3,200 combined AI use cases cataloged across the US and EU, public sector IT leaders face an identical roadblock: traditional application delivery controllers were not designed to parse or throttle Layer 7 LLM payloads, leading to backend GPU exhaustion.

Let’s say your team shipped a support agent last quarter. The launch demo went well, stakeholders were pleased, and everyone moved on. A few months later, things start to look off. Summaries of long conversations are truncated, and monitors show latency spikes on tool calls to the billing API. Your team’s first instinct is to ship fixes such as tweaking prompts or upgrading the model.

AI usage tracking means measuring who and what consumes AI across your company, by team, feature, and model, then converting the usage into spend and cost per unit of work. Provider consoles stop at totals per API key. Tracking puts names on those totals: which team, which product, which model, and whether any of it was worth the money. In May 2026, CNBC reported that “almost every Fortune 500 is tracking overall AI usage,” quoting ModelOp CTO Jim Olsen. The same reporting carried his warning.

As a product manager at Upsun with a computer engineering background, Kateryna Dvornichenko had spent months researching competing tools in the agentic development space, running tests, comparing features, and building a picture of where the market was heading. She realized the tools were impressive, but something kept standing out. "Collaboration was not the strong point of any of them," she says. "Everyone stays on their own machine with their own setup.".