Operations | Monitoring | ITSM | DevOps | Cloud

The latest News and Information on Cloud monitoring, security and related technologies.

Adding friction to your AI spend isn't saving money. It's costing you growth.

Enterprises are putting hard ceilings on AI spend. Accenture now centrally funds $29 a month per person for Claude and charges anything above that to a project budget code. Uber used up its 2026 AI budget in four months and restricted access. A cap stops waste and useful work at the same rate. The alternative is seeing AI cost by team, by project and by outcome, then funding what returns. Companies spent the past year telling employees to use more AI. Now a lot of them are putting a lid on it.

Shipped: Slice AI spend eight ways in AI Explorer

You can already break down cloud spend by team, product, or customer in Explorer. But AI spend has been harder to decompose. Which models is each team running? What activity is driving the cost growth you saw this month? Before AI Explorer, answering those questions meant exporting raw event data and building your own breakdowns, or waiting days for reconciled billing to land in Explorer.

Before you build your own internal platform, run these numbers

"We'll just build it ourselves" is usually said with confidence and a rough headcount estimate. Six months later, the team that was supposed to spend two sprints on it is still maintaining it a year in, and the platform that was meant to save engineering time has become one of the things engineering time goes to. Build isn't automatically the wrong call. Sometimes it's the right one.

Strengthening the Security of Qovery's Access to Your AWS Account

Qovery now sends your organization ID as the sts:ExternalId when it assumes the IAM role in your AWS account, and the role's trust policy only accepts it on behalf of your organization. Your role is already updated. If you manage it with the qovery-role-creation CloudFormation stack, update the stack to the latest template. Romain is a staff engineer at Qovery working on the control plane and AI integrations. He writes about distributed systems, incident response, and MCP-based tooling.

AWS Interconnect Is Coming to Megaport

AWS Interconnect is coming to Megaport, giving enterprises and AI infrastructure providers another way to scale private AWS connectivity with automation, encryption, and built-in resilience. Megaport customers just got a new AWS connectivity option, and it fits perfectly with how we’ve always believed infrastructure should work: direct, automated, resilient, and easier to operate.

Capping the AI free-for-all? Know what each dollar returns first.

Most companies gave everyone AI access and thought they’d sort out the costs later. Engineering, support, product, marketing, and finance all got licenses to the best models. The early results looked good, and for a while it didn’t matter there wasn’t an explicit business case. Let’s call the first half of 2026 the free-for-all period for many companies. AI adoption spread across the org fast, people and teams loved it, and then the invoices started coming in.