Just out of curiosity, and since this is vaguely related to the content, how has Fly.io adjusted to SOC 2 when it comes to infrastructure changes and deployment? I read a while ago about how you guys passed SOC 2 which was an enlightening read, but I'm curious what systems you have put in place to keep velocity going and how you manage change more generally across infrastructure?
My current experience is that once we started transition to SOC 2 compliance and brought in new processes everything crawled to a halt, we now have multiple layers of reviews and scheduling, and the bureaucratic process is followed at the cost of expediency and doing sensible things in a sensible way (i.e., everything must follow the process, no matter how trivial or significant.)
My current experience is that once we started transition to SOC 2 compliance and brought in new processes everything crawled to a halt, we now have multiple layers of reviews and scheduling, and the bureaucratic process is followed at the cost of expediency and doing sensible things in a sensible way (i.e., everything must follow the process, no matter how trivial or significant.)