Ben Bleikamp 
A lot of devops is tedious, repetitive busy work. Answering the same questions over and over. Making quick fixes to config files for the umpteenth time.
- Did anything change in our metrics after the most recent deploy?
- Is our cloud infrastructure still SOC2 compliant?
- Are we wasting money in AWS?
- Creating another new S3 bucket or ECS instance for a new team
The list goes on and on. And on. So we built Workflows to help you with the busy work.
Workflows can be triggered on a schedule, from an API call, with a GitHub Action, and from Slack messages. A workflow is just a set of instructions for Cased’s agent to follow to take care of some task when it’s triggered.
Instead of alerting you that a piece of infrastucture is out of compliance with SOC2, we spin up an instance of an agent that looks at your infrastructure, proposes a fix for you via a pull request, and let’s you know it’s ready to review and be merged.
Instead of checking observability metrics after deploys, we spin up an agent that checks metrics and handles notifications after each deploy. If a metric spikes, it can start a rollback. If everything looks good, it can share a beautiful flat graph (or one showing an improvement!)
We’re shipping Workflows with 10 pre-built workflows (with more to come). Soon we’ll be opening up custom workflows that you can use to handle even more of the busy work around devops.
