It’s been a busy month at FireHydrant. We’ve had our heads down shipping loads of improvements across the platform, and I want to take you on a quick tour of the changes. At the core of all these updates is a common theme: things are now a heck of a lot more intuitive. There’s a lot to digest here; read the full roundup of June releases below or follow us on Twitter for a bite-size demo each day this week.

‍ This post highlights some of the features and improvements that we have released in the last 3 months. If you want to submit your own ideas or vote on existing feature requests, you can now use our new public roadmap at roadmap.ilert.com.

Customer retention is critical. Studies show that acquiring a new customer is five to 25 times more expensive than retaining an existing one. On top of this, a marginal increase in customer retention can yield increases in revenue up to 95%. Customers spend a lot of time interacting with businesses online and their user experience can have a major impact on how they view a company. One bad user experience can send a customer into the arms of a company's competitor.

Digital business is an imperative for 21st-century companies. Increasingly, organizations are directing investments toward technologies that deliver outcomes fast and enable more resilient digital business models. In this landscape, incidents such as software bugs, power outages, or downed networks have major consequences that affect both revenue and customer loyalty.

Imagine having the ability to instantly know when a Kubernetes compliance or security violation occurs. Now you can with Shipa Insights. Coupling Shipa Insights with the robust notification and alerting capabilities of PagerDuty makes this very possible. Shipa has the capability of sending fine-grained events externally e.g to PagerDuty. Now with the power of Shipa Insights, you have the capabilities to alert on policy violations. Let’s take a look at gettings started.

I recently published a couple of blog posts about what happens when you invest in a thoughtful incident management strategy and three first steps to take to do so. What I’m getting at in these posts is that we need a shift toward proactivity in the software operators community. I’d wager most of the world is responding to incidents as they happen, and nothing more.

With cybersecurity boundaries going beyond the traditional walls of an office and attack surfaces constantly expanding, data breaches are inevitable. Managing risks from data breaches requires organizations to develop a comprehensive incident response plan – an established guideline that facilitates incident detection, response and containment, and empowers cybersecurity analysts to secure a company’s digital asset.

Service ownership is a DevOps best practice where team members take responsibility for supporting the software they deliver at every stage of the development lifecycle. This level of ownership brings development teams much closer to their customers, the business, and the value being delivered. Service owners are the subject matter experts (SMEs) for their services – and in a service ownership model, they are also responsible for responding to any production issues.

Summer means things are heating up. And things are definitely heating up at Blameless! We’ve been hard at work delivering new features and capabilities to our customers, so today I wanted to share a quick summary of all the latest. Here are 4 exciting product updates that enhance the way teams manage incidents and deliver reliable products to their customers.