Operations | Monitoring | ITSM | DevOps | Cloud

Our CLI team has been cooking up some awesome new AI functionality that we think you will love. The latest release includes several new commands such as changelog, commit, pr, and a command to check the remaining tokens on your subscription. They are all nested under a new top level command, gk ai.

AI adoption isn’t just accelerating, it’s compounding. From GPT-5 to Claude to Llama and beyond, engineering teams are integrating diverse LLMs across products, experiments, and services. And finance teams are now grappling with a new kind of cloud complexity: token-based economics and volatile inference costs, often spread across multi-model, multi-cloud, and multi-region architectures. The modern FinOps stack needs to keep up. CloudZero was built for this moment.

When a service slows down, metrics will tell you that it’s happening but logs tell you why. For MySQL, slow queries can be a silent performance killer, gradually chewing through resources until users start complaining. By enabling MySQL’s slow query log and forwarding it to Loki (via Promtail), you can visualize query-level details right alongside your metrics on Grafana dashboards. This makes it easy to correlate what is slow (metrics) with what is causing the slowdown (logs).

I’ve spent most of my career building and optimizing cloud, on-prem, and data platforms for growing companies. It’s been an amazing journey so far. Through it all, FinOps has become more than just a methodology for me (Fred FinOps didn’t just come from my love of the Flintstones, though I do appreciate a good cartoon). It’s a community, a discipline, a tribe I’ve come to call home. Lately, some tough questions have kept me up at night: These challenges got me thinking.

Explore IaaS, PaaS, and SaaS cloud models to accelerate your shipping. This guide defines each, compares their benefits and drawbacks, and introduces a modern approach to get IaaS power with PaaS simplicity.

Chaos Engineering has proven itself to be incredibly effective at tracking down failure modes, remediating reliability issues, and preventing risks before they happen. Unfortunately, it can also come with a steep adoption curve. In order to get the most out of Fault Injection testing, a practitioner needs to have a deep knowledge of the service, its expected behavior, and the code behind it. Ultimately, the rewards are worth the time.

Software quality assurance has changed dramatically over the past few years. Today, the velocity of software development demands more than traditional staging and shared QA environments. Releases are expected to be faster, integration cycles shorter, and quality standards higher. These pressures have inspired a growing interest in preview environments—ephemeral, production-like spaces spun up on demand for testing code changes in isolation.