Systems | Development | Analytics | API | Testing

Every CIO has a slide deck full of AI pilots by now. A chatbot that answers FAQs. A copilot that drafts emails. An agent that summarizes meetings and files the notes nobody reads. The demos get applause in the boardroom, the budget gets approved for “phase two,” and then largely nothing happens. The pilot quietly lives on in a sandbox, forever 80% done, forever six weeks from launch. If that sounds familiar, you are not behind. You are, statistically, in the majority.

Every team we talk to has a running list of questions they wish they could get fast, reliable answers to. What changed in our performance last month and why. Which clients are showing the early signs of churn. Which channels are actually pulling weight and which ones are quietly burning budget. The pull toward AI for this kind of work is obvious. The answers should be a question away.

Data center teams are skilled at solving familiar problems such as storage outages, missed forecasts, and late refresh cycles. These are known quantities. Teams have playbooks for them. But 2026 has brought a different kind of pressure. After years of enterprise AI investment concentrated almost entirely on model training, the industry has crossed a threshold: the workload that now defines AI infrastructure isn’t building models. It’s running them. Continuously. At scale. Every day.

With the release of Xray Cloud 15.0.0, Xray expands its latest AI capabilities with the introduction of AI Test Prioritization, joining two recently released features: Xray's Rovo Test Plan Summarizer and AI-generated Manual Scripts for Test Case Designer, introduced in Xray Cloud 14.0.0. Testing is rarely just about executing test cases. Teams need to understand where risk exists, how testing is progressing, and whether a release is ready to move forward.

Webinar recap: Andy Cotgreave (co-founder, How to Speak Data) and Francois Lopitaux (SVP of Product, ThoughtSpot) on hallucinations, accountability, and what it actually takes to trust AI with your data.

In the first experiment, I wanted a baseline: if an AI coding agent gets the same production signal a human would get, can it fix bugs in a codebase it has never seen? Yes, but only when I gave it better context. With only an alert, the agent passed 51% of the runtime tests. When I added captured traffic, the actual request and response for the failing call, it climbed to 77%. This post is the second pass.

If you have watched a Temporal demo and an n8n demo back to back, the reaction is almost universal: “Wait, aren’t these the same thing?” Both stitch together a sequence of steps. Both retry failures. Both, as of 2026, market themselves around AI agents. On a whiteboard, they look like cousins. They are not. Temporal vs n8n is one of the most common false equivalences in modern engineering, and getting it wrong is expensive in both directions.

Explore the architecture, open standards, and semantic layer that give AI agents access to accurate, reusable business context.

When we released the OctoPerf MCP Server, most teams connected to it straight from Claude.ai. Then we showed how to run the whole stack on-premise with a local model. But a question kept coming back from European teams: can we drive our load tests with a French LLM, hosted in Europe, instead of a US model? The answer is yes, and it takes about five minutes.

A CFO asks her AI agent a simple question: "What was our ARR at the end of Q3?" The agent finds the subscriptions table, spots a column called arr, sums it up, and returns $16.4M. Strong quarter. Everyone nods. The real number was $13.9M, but no one in the room knew it yet. I hear some version of this story from nearly every data leader I talk to right now, and it almost always starts the same way. They stand up an AI pilot. It looks sharp in the POC.