Original Summary

After having spent years in the realm of CI/CD and DevOps, I've grown a bit irritated with the state of things: GitHub downtime, ever heard of this? We want infrastructure that we control, that we know. With the advent of LLMs, YAML is no longer a manageable way of defining CI workflows. We need testability before we push commits, we need static code analysis, we need a normal modern typed language. We need a test loop that does not need to wait for git pushes to work, shift left. Coming from a European country, we want sovereignty of data, of the execution infrastructure. I have built https://kici.dev , which is a full CI platform, divided into an observability dashboard (centralized) and the execution side (fully OSS and self-hosted). The platform is NOT mandatory for the orchestration to work and is a relay/observability/access management product that provides pure add-ons to the core OSS product (the orchestrators). The orchestrators can receive webhooks and process workflows in full independence from the platform itself. I categorize the product as a beta, and I have plenty of future plans towards a more fully self-hosted solution if enough interest gathers. I am fully aware, as a DevOps Engineer, how important it is to OWN the software you use. I just need to see some traffic and feedback before a full send-in, because once you lock features on OSS, you don't go back :) The workflows are written in TypeScript, and LLMs can write and test them directly on the infrastructure the orchestrators run on, without having to pass through slow git operations. Push the workflow payload, run it, test it, check logs, etc. There is a lot to KiCI, and you can start from https://docs.kici.dev/user/why-kici/ or from a quickstart at https://docs.kici.dev/user/quickstart/ :) Throw an LLM at it, it will be even faster!   submitted by   /u/Cmaster11 [link]   [comments]

  • 情报分类：技术学习与提效
  • 分类依据：内容涉及技术、AI、软件工具或工程实践
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/10/12 16:42:51