Operations | Monitoring | ITSM | DevOps | Cloud

Having backups doesn't mean you have disaster recovery. And that gap could kill your business. Backups are just data snapshots stored safely for restoration when files get corrupted or deleted. Disaster recovery is your complete operational playbook for bringing back servers, applications, networks, and entire infrastructure after catastrophic failures. You can restore every byte of data from backup and still watch your business stay offline for hours or days because you lack the recovery procedures, failover systems, and tested runbooks to actually get operations running again.

April was a big month at Harness. AI is changing how code gets written — and the rest of the SDLC is catching up. In this update, Dewan Ahmed walks through Harness product releases across three themes: AI in the developer workflow, security and governance for AI assets, and self-service maturity for developers and platform teams. What's covered (with timestamps): Found this useful? Subscribe for monthly product updates, and drop a comment telling us which release you want a deep dive on next.

Want to start chaos engineering? Don't randomly break stuff and hope for the best. Real chaos engineering starts with defining your system's steady state metrics like latency, throughput, and error rates. Then you form a clear hypothesis about what should happen when failures occur. Next, you inject controlled failures, starting small with single pod kills or network drops, not production meltdowns. Finally, you limit the blast radius by running experiments in safe environments first.

What's the most debated DORA metric? Nathen H from Google's DORA team breaks down the change lead time debate — and why even the experts can't fully agree on when a change is "committed." Is it at commit? After merge? The answer matters more than you think. Subscribe for more DevEx and DORA insights from our Web Summit series.

Meet the new Harness Plugin for Cursor, you can now bring the software delivery outerloop and have it meet your innerloop for development all in your Cursour IDE.

Stop context-switching between your IDE and your CI/CD dashboards. In this video, we demonstrate the new Harness Cursor Plugin, a native integration that brings the full power of the Harness AI Software Delivery Platform directly into Cursor. Using the Cursor Agent window and the new Harness Model Context Protocol (MCP) server, you can now manage your entire software delivery lifecycle through natural language. From triggering pipelines to governing deployments, this plugin ensures you stay in your flow while maintaining enterprise-grade security and control.

Welcome to the Season 4 finale of the Ship Talk podcast! Join special host Thomas Dockstader and several industry leaders at AWS re:Invent to discuss the intersection of AI and software delivery. The following is a series of interviews with partners, customers, and engineering leaders on the front lines of AI transformation. Don't miss the "Ship It or Skip It" segment, where our guests give their rapid-fire takes on everything from AI code reviews to the four-day work week.

In this video, we introduce Harness Resilience Testing and show you how to move beyond once-a-year DR drills to a continuously validated, pipeline-driven process. You'll see how Harness lets you validate regional failovers, check database replication lag under pressure, and confirm your hot standbys genuinely take over live traffic, all in one place. We also walk through a live DR test execution, showing exactly how Harness triggers the full failover sequence, runs every validation step automatically, and gives you a clear pass or fail result in real time.

Struggling with disaster recovery planning? Learn the simple difference between RTO and RPO, the two most important metrics every developer, DevOps engineer, and SRE must understand. RTO (Recovery Time Objective) tells you exactly how long your systems can stay down before it hurts your business. RPO (Recovery Point Objective) shows how much recent data you can afford to lose in an outage.