Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Your DevOps Control Plane, in Slack

cto.ai

Post reply on HN
Print view View original

31–38 of 38 posts

Re: Show HN: Your DevOps Control Plane, in Slack

#31

Post by slajax »

mistedissetanti wrote: post #30

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. 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"? 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 resou…

Founder here - can you clarify what you mean by "data plane"?

We let you aggregate events and process metrics, should you want to use our platform as the way you aggregate event driven workflows or calculate delivery metrics.

You can run your entire workload on our serverless environment or you can push your workloads to your existing CI/CD + cloud computes - it's really up to you!

Re: Show HN: Your DevOps Control Plane, in Slack

#32

Post by slajax »

leosantana wrote: post #27
stevehiehn wrote: post #22

Earlier quoted context omitted.

(cto.ai employee here) The obvious ones are any basic CICD operation that you might want to trigger from Slack, i.e: pull code, build code, deploy code. The second use case that comes to mind is treating the platform as a very quick way to build an all purpose SlackBot.

Why in my conscious mind would I ever wanna do something like this? Especially that lately Slack has proven to be so unstable (lots of intermittent downtime). Meaning I would just lock my infra automation code in CTO.ai servers for... what?

Founder here - We recognize that Slack certainly isn't for everyone which is why everything also works in our CLI and also soon by public API. Slack have a great uptime and regularly stay above 99.9% uptime according to their status pages - that said, if you wanted to bypass Slack and still run cloud native workflows using CTO.ai, serverless-ly, we allow you to also do that via CLI or API. This means you could build your own client and just leverage us for inexpensive compute.

Thanks for sharing your feedback!

Re: Show HN: Your DevOps Control Plane, in Slack

#33

Post by slajax »

mistedissetanti wrote: post #28
leosantana wrote: post #27

Earlier quoted context omitted.

Why in my conscious mind would I ever wanna do something like this? Especially that lately Slack has proven to be so unstable (lots of intermittent downtime). Meaning I would just lock my infra automation code in CTO.ai servers for... what?

That's an interesting question and I was wondering the same thing. Sounds like if we set Slack aside, all that CTO.ai is really offering is buy-in into their platform w/ no clear value beyond the initial slackbot-like integration

Founder here - for our users, the initial value proposition of being able to deploy a Slack bot in less than 5 minutes without servers, is usually the starting point.

After that they start digging into our team features for Secrets, Configs, Logs and Events which along with our public registry gives them a significant feature set to work against!

Re: Show HN: Your DevOps Control Plane, in Slack

#35

Post by [deleted] »

slajax wrote: post #18
deeblering4 wrote: post #13

Earlier quoted context omitted.

What prevents a slack employee from issuing chat commands as an authorized user? Similar to what we saw in the recent twitter hack.

Well first of all, as a public company Slack is held to extremely well regulated security protocols to ensure this never happens, so we get the benefit of that out of the box. Additionally, we require the user to associate their Slack user to their CTO.ai account using a secure authentication layer that has dependencies outside of Slack. Theoretically, if a Slack employee were to try to execute a workflow, we would b…

[deleted]

Re: Show HN: Your DevOps Control Plane, in Slack

#36

Post by slajax »

schoolornot wrote: post #34

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.

Founder here - we agree. ChatOps has traditionally required you to build out a specific solution for Chat, which failed the cost of ownership equation, after you consider the cost of setting up servers, code and chat specific logic to run your workflows. Hubot is a good example but we've taking it way further and rethought DevOps from a Slack first perspective.

With CTO.ai your existing CLI "just works" in Slack and you have none of the additional overhead but get all of the benefits of chat such as distribution, transparency and collaboration as well. It's a big paradigm shift.

Many of our users are going all in because of this!

Thanks for your feedback! We'll keep iterating!

Re: Show HN: Your DevOps Control Plane, in Slack

#38

Post by slajax »

kaseyluckk wrote: post #37

Looks cool! Can you share some case studies / coolest use cases?

Absolutely. We have about 5 that are currently in the works that cover many different use case from our community. We’ll be sharing soon on our blog so please keep an eye out for them!
Post reply on HN