Founder here - We created CTO.ai to help foster accessible developer experiences by lowering the cost of leveraging Slack in your developer workflows.<p>The key idea is that you build a CLI using our SDK (it's a container) and then we make it instantly accessible to your whole team in Slack, while also providing 12 factor principals such as Secrets, Configs, Logs, Events and Metrics.<p>We are early on but have a very vibrant and growing Slack community of developers who want to build their own Cloud PaaS using AWS, GCP, Azure etc but want an easy to use DX so they can distribute there knowledge and process to others and save themselves tons of time and context switching.<p>Please AMA, we'd love to hear your thoughts.
Slack as a "control plane" is quite the concept, giving operational power to more people around the company through Slack can be a two-edged sword though.<p>Now, aside from the implicit risk that this might offer, if Slack acts as the "Control plane" for DevOps, what's the platform's "Data plane"?<p>Is it right to assume that in order to be independent from Slack we'd need to rely on CTO.ai's own infrastructure and resources? I.e. the data plane where DevOps "effectively happens"
What happens when Slack is down? Does DevOps also stop, or is there a way to do the same commands/workflows outside of Slack?<p>You don't want two separate run books, as they'll never stay in sync. It'll already be enough of an efficiency hit just switching to an alternative interface when Slack is down, let along switching to different tools/processes.
Chatops has failed at every single company I've worked at. This is an extremely noisy and unnatural way of managing resources and it gets old after the first week. A sprinkle of Hubot here and a Slack web hook there but no one is going all-in on this.