KiCI

Your coding agent writes KiCI pipelines in typed TypeScript, runs them on your machine or your own agents before it pushes, then reads and re-runs the result over MCP.

KiCI hosts the dashboard, identity and the webhook relay. Your code, secrets, logs and artifacts stay on infrastructure you run. Here is exactly what transits.

KiCI ships no cloud drivers. A TypeScript workflow you write boots the machine, so any cloud with an API can host your CI agents.

Walkthroughs of what you can build with KiCI, with real, tested TypeScript code you can copy.

Global workflows run one pipeline on every repo in your org from a single workflow repo, with no file added to the repos it covers.

Hosted CI services run your jobs — and hold your source and secrets — on their cloud. KiCI keeps execution on your own infrastructure while still giving you a managed control plane, so your code stays sovereign without you operating a CI server.

KiCI pricing — free forever with full functionality; paid tiers raise the limits.

Honest, sourced comparisons of KiCI against GitHub Actions, GitLab CI, CircleCI, Jenkins, Dagger, and Buildkite — plus the underlying concepts (TypeScript vs YAML, self-hosted vs SaaS).

Two hybrid CI platforms that keep your source and secrets on your own infrastructure. The difference is authoring: KiCI is typed TypeScript with schema-validated values, where Buildkite uses YAML steps and shell commands.

A point-by-point look at KiCI — typed-TypeScript pipelines that run on your own infrastructure — versus CircleCI’s YAML pipelines on its cloud compute (or self-hosted runners).

KiCI and Dagger both replace YAML with real, typed code that runs locally — kindred spirits. The difference: Dagger is a portable pipeline engine you run inside your existing CI, while KiCI is a complete CI/CD platform with a hosted control plane, trigger matching, job dispatch, and a built-in multi-backend autoscaler.

KiCI's orchestrator and agent are open source (AGPL-3.0). Run them fully self-hosted in independent mode: git webhooks hit your orchestrator directly, jobs run on your infrastructure, and KiCI's servers are never in the loop.

KiCI is built by Alberto Marchetti and runs KiCI's own production deployments. Public status page, public changelog.

KiCI is a complete CI/CD system that runs your pipelines on machines you control. Your coding agent can drive the whole dev loop before anything reaches your branch. KiCI never receives your source or secrets.

Woodpecker is a fully open-source, self-hosted CI engine — you run the whole platform (server + agents) and define pipelines in YAML. KiCI brings typed-TypeScript pipelines and a managed control plane, so you keep execution sovereign without operating a CI server yourself.

GitHubRepository owner