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

1–10 of 38 posts

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

#6

Post by slajax »

Founder here - We created CTO.ai to help foster accessible developer experiences by lowering the cost of leveraging Slack in your developer workflows.

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.

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.

Please AMA, we'd love to hear your thoughts.

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

#7

Post by slajax »

deeblering4 wrote: post #5

Doesn’t this give slack employees root on your infrastructure?

Founder here - 100% not. We've build a specialized PaaS that ensures your credentials and workflows are encrypted and there is no additional security vector here. Also Slack is one of our investors and they have worked with us a great deal to make sure that the security is handled properly!

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

#8

Post by dvohro »

stevehiehn wrote: post #3
dvohro wrote: post #2

How does this compare to GitHub Actions for Slack?

full disclosure: I work for CTO.ai. It is a similar concept really, but the Ops Platform has a built in interop layer for communicating between the containers & slack channels.

what do you mean by containers? a company's dockerized infra?

I watched the video, you guys are centralizing all the team's scripts inside Slack. I can see a lot of Slack addicts loving this!

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

#9

Post by slajax »

eslamsalem wrote: post #4

Very interesting. Can I set permission for every slack member? What resources he can control ?

Founder here - Since a workflow in the context of CTO.ai is just a container, which executes your code, you can build out as robust permissions as you need to by leveraging our vault integration, configs and teams.

Currently, our teams are a basic ACL that lets you manage who in Slack can run the workflow, but we also allow you to associate any of your teams to private channels, so you can more granularly control access using Slack's user membership.

We're looking at more RBAC on top of this for enterprise but for most smaller teams, this covers the majority of their use cases. They often create a team for ops and a team for dev and then associate these teams to members + channels as needed.

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

#10

Post by slajax »

dvohro wrote: post #8
stevehiehn wrote: post #3

Earlier quoted context omitted.

full disclosure: I work for CTO.ai. It is a similar concept really, but the Ops Platform has a built in interop layer for communicating between the containers & slack channels.

what do you mean by containers? a company's dockerized infra? I watched the video, you guys are centralizing all the team's scripts inside Slack. I can see a lot of Slack addicts loving this!

Founder here - Thanks! Yes that's the general idea.

We're making it so you can port your existing scripts and allow them to easily run in Slack so that they are more discoverable and intuitive for all experiences.

Post reply on HN