KiCI

Frequently asked questions

Common questions about KiCI — each answer links to the docs.

Does KiCI see my source code or secrets?
No. Your code never leaves your infrastructure — the hosted control plane only verifies and routes webhooks, while the orchestrator and agents that touch your code run on your own servers.
Can I write CI/CD pipelines in TypeScript instead of YAML?
Yes. KiCI workflows are real, typed TypeScript — you get type safety, autocompletion, loops, conditionals, and async/await for your pipelines.
Can I test a workflow before pushing?
Yes. kici run --local and kici run remote run any workflow against your current working tree — including unstaged changes — on your own machine or against the real remote pipeline, before you commit or push.
How much does KiCI cost?
The hosted control plane is free with full functionality; paid tiers only raise the limits. You run jobs on your own infrastructure, so you provide that compute.
Does KiCI automatically scale build agents?
Yes. A built-in auto-scaler provisions ephemeral agents on demand across Docker/Podman containers, bare-metal processes, and Firecracker microVMs — on your own infrastructure, with no extra controller.
Do I have to run and maintain a CI server?
Yes — the orchestrator and agents that run your jobs live on your own infrastructure, so you operate and maintain those. What you do not run is the hosted control plane: KiCI manages the dashboard, identity, billing, and webhook relay for you.
Get started with KiCI Compare KiCI