Operations | Monitoring | ITSM | DevOps | Cloud

Seven developer-requested features. Tighter control over branches, history, and large repos. No CLI detours required. If you have been using GitKraken Desktop in a complex repo, you already know what it feels like when the commit graph turns into a wall of branches. When rebasing requires more ceremony than it should. When you just need one file back from three commits ago but have to orchestrate a whole checkout to get it. GitKraken Desktop 11.10 is built for those moments.

SAP operations teams are drowning. Every day is a battle against alert fatigue, complex root causes, and repetitive firefighting. And while vendor spin will tell you that moving to the cloud or adopting SAP RISE magically simplifies everything, the reality on the ground is entirely different. We call it the Hybrid Cloud Paradox: Different providers might own different parts of your critical business landscape, but you still own the business risk.

Automated Diagnostics closes the gap between detection and diagnosis instantly. Every IT operations team knows the pressure. When an alert hits at 2 a.m., it’s a race against time to find the root cause before users feel the impact. But gathering diagnostic data such as logs, process stats, and thread dumps can eat up critical minutes. That manual lag is exactly what Automated Diagnostics eliminates.

Today we’re announcing the CloudZero Claude Code Plugin, a new capability that puts CloudZero’s full cost intelligence model directly inside Claude Code, where engineers and technical FinOps practitioners already work. The plugin connects a Model Context Protocol (MCP) server and nine pre-packaged investigation skills to CloudZero’s cost data, covering cloud and AI spend across AWS, GCP, Azure, Snowflake, MongoDB, OpenAI, Anthropic, and more.

As we gear up for Grafana 13, the next major release of the open source data visualization platform that we’ll announce at GrafanaCON this April, our engineering team is still shipping some powerful new features along the way. Case in point: Grafana 12.4 is officially here, and there’s a lot to be excited about. The latest minor release includes a ton of updates that help you build and design dashboards faster than ever, as well as manage and scale those dashboards seamlessly over time.

Today, Harness is announcing the General Availability of Artifact Registry, a milestone that marks more than a new product release. It represents a deliberate shift in how artifact management should work in secure software delivery. For years, teams have accepted a strange reality: you build in one system, deploy in another, and manage artifacts somewhere else entirely. CI/CD pipelines run in one place, artifacts live in a third-party registry, and security scans happen downstream.

We just released React Native SDK 8.0.0, here's what's new, and what's changed. It's been a while since the last major version. The last major release, 7.0.0, shipped on September 2, 2025. After 13 minor and 2 patch releases, it's finally time for a new major version to land: 8.0.0. This version is a maintenance and capability major. This means we: It should be straightforward to upgrade, but check the migration guide for your setup.

We’re excited to announce that Speedscale’s proxymock is now available as an OpenClaw skill on ClawHub, bringing powerful API traffic replay capabilities directly into your Claude workflows.

The error monitoring scene has changed a ton over the past few years. We've gone from basic exception tracking to fully integrated platforms that correlate errors with performance metrics and logs. We’ve even got AI-powered debugging! But in the midst of the AI explosion, some things remain unchanged and most teams are still drowning in data with little actionability.

"I wish I knew about this a couple years ago..." Over my seven years as a cofounder, I've heard some version of that line more than any other. Usually, it comes at the end of a demo to someone who has spent a year getting to something not even close to what they're seeing on my screen. The story is always the same. An organization adopts Kubernetes and arrives at the inevitable conclusion that they need a platform.