Skip to main content


We take security very seriously at WarpBuild. Here are some of the measures we take to ensure that your builds, runners, and build environments are secure.


SOC2 Type 2

WarpBuild is in the process of getting SOC2 Type 2 certified. The controls required for SOC2 compliance are implemented. We are happy to share our security documentation and work with you to ensure that we meet your compliance needs. Please email us at [email protected] to discuss your requirements.


Compute isolation

Each runner runs in its own virtual machine with cpu pinning to ensure there are no shared compute cores. The VMs are created on demand and destroyed after each build. This ensures that your builds are isolated from other builds and that no data is left behind.

The VMs use a KVM-based hypervisor for maximum performance and security. This is the same technology used by cloud providers such as AWS to power their virtual machines.

Storage protection

Each runner has its own encrypted storage volume that is created on demand and destroyed after each build. When caching is enabled to speed up your builds, the cache is encrypted and stored securely in a location that is only accessible to your runner.


WarpBuild does not access or store any build secrets. Secrets are stored in your source code repository and are only accessible to your runner environment.