Sovereignty

Every self-hosted CI asks you to build and run a control plane: a dashboard, sign-in, roles, approvals, a webhook path into a private network. That work has nothing to do with your builds, and it never stops. KiCI hosts that layer, and only that layer. Your code, your secrets and your compute stay where they already are.

What the hosted platform is

The hosted platform provides the dashboard, identity and authentication, organizations, teams and roles, billing, and webhook ingestion.

What the platform holds, and what stays with you

The hosted platform is the point where your team sees and controls runs. It is not where runs happen. Every row below cites the KiCI docs.

What the platform holds, so your team can see it

webhook payloads, to route them

The platform checks each inbound webhook signature and relays the payload to the right orchestrator.

run status and timing

Run lifecycle metadata — status, timestamps and durations — is stored by the platform, so your team has run history.

the live log stream you open in the dashboard

Live log lines pass through the platform to your browser while a run streams. The platform does not store them.

What stays on your infrastructure

your source code

Your source code and cloned repositories stay on your infrastructure.

your secrets

Secret values are masked before they leave the agent sandbox. Only key names appear in run metadata.

your logs at rest

Log storage lives on your orchestrator, never on the platform.

your build artifacts

Build artifacts are written to object storage your orchestrator owns and you configure.

Your source code

The platform never processes, stores, or executes your code, and never sees your secrets.

Logs and artifacts at rest

Your orchestrator writes logs, caches and the cold-store archive to object storage you configure and run.

Where the dashboard runs

Where the dashboard runs

The hosted platform is EU-sovereign.

Your orchestrator and your agents run wherever you put them, in any region or in no cloud at all. The hosted platform's location matters for the control-plane records it does hold: organizations, members, roles, billing, and run status.

If we stop, your pipelines do not

If we stop, your CI does not

The orchestrator and agent do all of the execution work and run fully self-hosted in independent mode, with the hosted platform out of the loop.

The orchestrator and the agent are open source under AGPL-3.0. In hybrid mode your git host can deliver webhooks straight to your orchestrator while you keep the dashboard. In independent mode the hosted platform is out of the path entirely. Moving between the modes is a configuration change, not a migration.

Read how independent mode works →

Residency is not sovereignty

Data residency answers one question: which region stores the copy a vendor already holds. Sovereignty answers a harder one: who holds a copy at all, and who can be compelled to hand it over. A region setting does not change the second answer. KiCI takes the other route — your source and secrets are never sent to us, so there is no copy to locate, to disclose, or to migrate. That is a deliberate trade: we give up the ability to run your builds for you, and you give up nothing to get the dashboard.

Why this is being asked now

In September 2025 the EU General Court dismissed the first direct challenge to the adequacy decision behind the EU–US Data Privacy Framework, so transfers under it stand for now. Court of Justice press release, 3 September 2025 ↗
The European Commission has proposed a Cloud and AI Development Act, which adds one EU-wide sovereignty framework with four assurance levels for cloud and AI services. European Commission, Cloud and AI Development Act ↗

KiCI reads neither as settled. The architecture is built so the answer does not depend on it: your code and your secrets never reach us, whatever the next decision says.

Questions

Run status and timing

The platform aggregates the execution telemetry and status your orchestrators forward, which is what the dashboard shows.

Where the dashboard runs

The hosted platform is EU-sovereign.

If we stop, your CI does not

The orchestrator and agent do all of the execution work and run fully self-hosted in independent mode, with the hosted platform out of the loop.

Run a pipeline locally Read the architecture