As we look to continue to provide value to our Remediate customers, we focused on how we create simple and effective workflows in the product. Our customers have told us there are some really important quality of life features that would go a long way in helping reduce the pain and frustration of remediating vulnerabilities and enable them to better communicate with their security partners.

Relay has a substantial library of external services and tools — as of March 2021 there are 60 integrations in our Github organization. Each integration repo can contain multiple triggers, containers that receive webhook payloads from other services, and steps, which Relay executes to get stuff done in your workflow.

Today we’re proud to announce the general availability of Relay, a cloud-native workflow automation platform. We launched our public beta of Relay last June, and we’re now officially out of beta and open for business! We’ve been pretty busy during the beta period - early users have executed thousands of workflows, processed tons of events, and given us incredibly helpful feedback.

Whether you’re a current customer looking to expand across your Windows estate, or thinking of deploying Puppet across your infrastructure for the first time, we hope this blog post — based on real-world customer questions and problems — can help answer some of the questions you may have about Puppet.

Patching vulnerabilities can be daunting, especially if the information is confusing, and the process to deploy patches is long. There are going to be times where a zero day presents itself, and the vulnerability requires immediate action. Whether it’s a simple fix or not, the seriousness of some vulnerabilities can put organizations at risk. Deploying patches, especially for critical infrastructure, takes planning.