Operations | Monitoring | ITSM | DevOps | Cloud

Your AI calls already emit OpenTelemetry: your LLM gateway exports it, and it’s the open standard your own services can speak. But you don’t have anywhere to turn those spans into spend you can allocate to an outcome. Now you can. CloudZero exposes an OpenTelemetry endpoint that doesn’t care what’s on the other end.

GPU utilization is one of the most expensive metrics in cloud infrastructure to get wrong. A GPU running at 30% utilization costs the same as one running at 90%, but it's doing a third of the useful work. For workloads measured in tens of thousands of GPU-hours, the difference between average utilization in the 30s and average utilization in the 70s is hundreds of thousands of dollars across the life of the workload.

We rebuilt large parts of the Qovery Console: new navigation, overviews at every level, dark mode, and a modernized frontend architecture with TanStack Router and React Suspense. Rémi is a staff frontend engineer at Qovery. He writes about frontend architecture, developer experience, and building scalable UI systems for platform engineering tools. Théo is a senior product designer at Qovery.

It's 7am. An alert fired overnight. You open your monitoring solution, navigate to the alert, cross-reference the waits, check the query plans. Twenty minutes later: it should not have fired. You knew that before you started, but you had to check anyways. The feeling of being overwhelmed by alerts is real. And so is the cost. Thresholds set once and forgotten, firing on patterns that have been normal for months. The inbox fills. DBAs learn to ignore most alerts. The workaround becomes the workflow.

If anyone knows how to operate under scrutiny, it’s database teams within finance organizations. It’s a given considering the more rigorous compliance requirements and processes they must follow. But the 2026 State of the Database Landscape: Finance Edition reveals something more specific, and more uncomfortable, than the familiar story of regulatory pressure.

On June 9, 2026, the OpenSSL project released patches covering 18 vulnerabilities across its supported releases. The headline flaw, CVE-2026-45447, is rated high severity and has the potential for remote code execution. Not too long ago, a security advisory with 18 vulnerabilities would have been routine. Microsoft’s Patch Tuesday provided a predictable cycle, and organizations operated with the expectation of a meaningful remediation window. That model is under pressure.