Boundaries you can verify, not badges.
Korvu’s security posture is architectural: the engine is open source and runs inside your network, fixes are verified in ephemeral sandboxes, and the evidence attaches to your commits. This page describes what the system does — not certificates we don’t yet hold.
Security properties you can check yourself.
Each row below is a verifiable property of the architecture, not a promise. The source is public — don’t take our word for any of it.
Your code stays put
by architectureOn self-hosted Core, diffs are read from your Git, fixes are drafted and verified on your machines, and results post back over your network. There is no Korvu-side copy of your source, because there is no Korvu side.
Your LLM, your keys
read from env · never stored by usThe engine calls whichever endpoint you configure — a provider key you hold, or a self-hosted model behind your gateway. On self-host, keys live in your environment; we never see them.
Auditable engine
agpl-3.0 · one engine, one licenseThe whole loop is open source. Your security team can read what the engine does with a diff before granting it one — and the AGPL keeps the version we run honest with the version you can read.
Evidence attached
receipts on every verified fixEvery proposed fix carries its verification receipt — the commands that ran, what passed, where it ran. The proof lands in your Git history, the audit surface you already trust.
Untrusted code runs like untrusted code.
A candidate fix is untrusted by definition — that’s why it’s verified. The sandbox that runs your build and tests against it is built to contain it.
What the managed layer is designed to see.
Cloud is pre-GA, so this section describes design intent — labeled as such. The boundary rule it’s built around: the managed layer runs the fleet; it doesn’t read your code.
Found something? Tell us directly.
Coordinated disclosure, a human on the other end, and credit if you want it. Engine issues can also be filed privately through GitHub security advisories.
What this page doesn’t claim yet.
No certification logos, no “in progress” badges standing in for results. When these ship, they move up the page with evidence attached.
Independent security review
Third-party review of the engine and (post-GA) the Cloud control plane. We’ll publish the artifacts when they exist — not the engagement letter.
◷ on the roadmapSigned releases & SBOM
Signed container images and a software bill of materials for every Core release, so your supply-chain tooling can verify what you deploy.
◷ on the roadmapAudit-log export
Streaming engine and control-plane events to your existing log pipeline, in a format your security tooling can ingest.
◷ on the roadmap