Kilo Code

US CLOUD Act exposureOpen sourceMIT

STAV REVIEW · LAST REVIEWED 06/14/2026

“Exceptional maintenance velocity and genuine BYOK Inference routing, but default gateway mode sends code context to US vendor infrastructure with unconfirmed retention terms.”

Good for

Teams enforcing BYOK-only mode who want a model-agnostic coding agent without single-provider lock-in
Engineering orgs that value high release cadence and an active open-source community — 1,572 issues closed in 90 days at a sub-daily release rate
Enterprise buyers who need SSO, SCIM provisioning, and audit logging built into the coding-agent tier
Procurement teams comfortable with MIT-licensed, source-auditable tooling as a baseline for Sovereign deployment planning

Watch out for

Default pay-as-you-go mode proxies code context and prompts through app.kilo.ai (US-operated); enforce BYOK by policy before any wide rollout
Customer prompt-storage and retention terms are deferred to a separate Enterprise Agreement — the public Terms of Service states no numerical retention period; obtain and review that agreement before deploying to regulated workloads
Kilo Code Inc. is a seed-stage US startup with a GitLab right-of-first-refusal on acquisitions expiring around August 2026 — a concrete near-term change-of-control event that could affect Cloud Act exposure and data governance
SOC 2 Type II is vendor-claimed on the enterprise page but no independently verifiable attestation certificate has been located across any curator run; treat as unverified until the vendor produces the report

Editorial assessment, not legal advice. Stav's risk ratings, scores, and verdicts are our own analysis of publicly available information and may be incomplete or out of date. Verify independently before making compliance or procurement decisions.

MODEL REQUIREMENTS

What Kilo Code needs from a model.

Required

Streaming
Tool calling

Recommended

Code-native
Long context (≥128k)
Structured output

Known issues6 open

Public security, privacy and governance advisories that are still open. Each row carries a source link — these are factual claims, not editorial judgements.

2026-06-30

lowUpstream change on kilo-code: github_last_push '2026-06-23T04:25:05Z' → '2026-06-30T00:36:52Z'

other · open

Source ↗

2026-06-23

lowUpstream change on kilo-code: github_release 'v7.3.46' → 'v7.3.54', github_last_push '2026-06-16T04:22:22Z' → '2026-06-23T04:25:05Z'

other · open

Source ↗

2026-06-16

lowUpstream change on kilo-code: github_release 'v7.3.40' → 'v7.3.46', github_last_push '2026-06-08T23:23:54Z' → '2026-06-16T04:22:22Z'

other · open

Source ↗

2026-06-09

lowUpstream change on kilo-code: github_release 'v7.3.21' → 'v7.3.40', github_last_push '2026-06-02T05:30:07Z' → '2026-06-08T23:23:54Z'

other · open

Source ↗

2026-06-02

lowUpstream change on kilo-code: github_release None → 'v7.3.21', github_last_push None → '2026-06-02T05:30:07Z'

other · open

Kilo Code

What Kilo Code needs from a model.

Data flow

Telemetry

Security profile

Maintenance health

Popularity

Where Kilo Code shows up on Stav.

What teams using Kilo Code configure.