Operations | Monitoring | ITSM | DevOps | Cloud

The latest Resilience Testing documentation update brings Chaos Hub directly into the docs, making it easier to discover and use fault, probe, and action templates. It also introduces a Prompt Library with ready-to-use AI prompts for Harness MCP, helping teams run resilience workflows faster using natural language.

AI has fundamentally changed software development. Developers are writing more code than ever. AI coding assistants can generate features, tests, documentation, and infrastructure configurations in minutes. Engineering organizations are seeing meaningful productivity gains as AI becomes embedded throughout the software development lifecycle. But there is a catch. Security teams now face a difficult reality: application security was already struggling to keep pace with software delivery before AI arrived.

Cloud cost visibility at scale usually works great… until it suddenly doesn’t. At first, everything feels manageable. You can track spend by service. You know which team owns which resources. Reports are clean, and the numbers make sense. Then one day, there’s a $47,000 spike spread across three AWS accounts that no one noticed for eleven days. Leadership wants answers. Engineering wants context. And your carefully designed tagging strategy?

AI is changing artifact management in two ways at once. Every AI-generated pull request, dependency update, and automated build creates more container images, packages, and Helm charts than ever before. Registries are growing faster than engineering teams can manage them, driving up storage costs and leaving thousands of stale artifacts behind. At the same time, the cost of deleting the wrong artifact has never been higher.

As organizations ship software faster than ever, runtime behavior changes are becoming just as frequent as code releases. Teams need a way to update application behavior without waiting for code deployments while maintaining visibility, governance, and control. ‍ Now available in beta, Config Management provides a governed runtime control plane that separates runtime configuration from application deployments, enabling organizations to deliver configuration changes instantly across environments.

Harness shipped 71 features in July, about one every 10 hours. That's more than June's 62, and the surge lines up with what AI is doing to the rest of the SDLC: coding agents are writing more of the code, test agents are now generating and running more of the tests by default, and every stage downstream: deployment, security, cost, and resilience has to absorb that pace without falling over.

AI has quickly become one of the largest and fastest-growing enterprise expenses, exposing many of the same governance and visibility challenges organizations previously faced with cloud. Based on findings from the 2026 State of AI in FinOps report, we explore how mature organizations improve AI cost ownership, reduce waste, and build a culture focused on measurable business value.

Versioning reference data in Git with Liquibase OSS changelogs enables consistent, auditable, and automated deployments across environments. Using loadUpdateData with versioned CSV files provides fast, reliable rollbacks and reduces production risk. Modern applications do not just depend on schema changes. They also depend on data that powers the application itself.

In April, Harness announced the Harness Cursor Plugin, a native integration that lets developers manage CI/CD pipelines, deployments, and security posture using natural language inside Cursor, governed by the same RBAC, OPA policies, and audit trails already enforced across the Harness platform. That experience has, until now, lived entirely at a desk.

Discover 8 critical questions engineering leaders must ask to measure and improve developer productivity. Learn how to assess team velocity, identify bottlenecks, and leverage DORA metrics for data-driven decisions that enhance engineering performance and developer experience. Why does developer productivity feel like it's declining even as your team grows? You hire more engineers, yet features ship slower. Sprint velocity looks healthy on paper, but deployment frequency tells a different story.