The answers your security team will ask for
CI security review
SOC 2 Type 2, penetration test summaries, tenant isolation architecture and a completed security questionnaire.
Handing a third party the ability to execute code with access to your repository is a real risk decision. This page is written for the person who has to sign off on it.
Isolation model
- One job, one VM — never a container on a shared kernel
- The VM is destroyed after the job; disks are wiped, not reused
- Cache objects are scoped per repository with cryptographic isolation
- No operator shell access to running job VMs
Compliance
- SOC 2 Type 2, audited annually
- Annual third-party penetration test, summary available under NDA
- GDPR DPA with published sub-processors
- Vulnerability disclosure programme
Common questions
- What isolation model do you use?
- One job, one microVM with its own kernel — never a container on a shared kernel. The VM is destroyed and its disk cryptographically wiped at job end.
- Can I see the SOC 2 report?
- Yes, under NDA, along with the annual third-party penetration test summary. Ask for Type 2 rather than Type 1: Type 1 attests to a single day.
- Do operators have access to running jobs?
- No. There is no operator shell access to a running job VM, and every configuration change is recorded in an append-only audit log.
Your next build could be twice as fast, at half the price
Start free. Migrating away is the same one line, and we publish that diff too.