So they can keep pace with dynamic application architectures and minimize service disruption. Without augmentation there’s higher costs, delays, and rates of disruption.
Entire teams can use RigD to become more effective without any need to code or manually define the automation.
Users start reducing incident times right away and continuously drive times down as their use of RigD matures.
Clicking between PagerDuty and Slack, I found myself using PagerDuty less and less. RigD solved that problem for us, and we are now fully integrated with PagerDuty within Slack using RigD. The RigD integration is saving us time and money by being able to more easily and collaboratively troubleshooting incidents immediately!
“You Guys are on the right Track. I need to give my developers access and this is a better solution than our homegrown portal”
“This will be the coolest and exciting DevOps tool to get work done, can't wait to see voice and sms modes for other applications too.”
“Hell Yeah [I would give this to my dev teams] This would make life so much easier”
“This is like a better MuleSoft without all the complex junk”
“This technology is very promising. Both for us to use in accelerating our development, and also as another way to deliver our services to users.”