hushgit
join waitlist →

Customer-controlled CI for encrypted repos

CI has to decrypt source code to build it, so HushGit starts with runners you control instead of managed build workers.

Why managed CI is not first

A hosted runner that sees plaintext code becomes part of your source-code trust boundary. HushGit avoids pretending otherwise: the first integration path is bring-your-own runner, explicit runner authorization, and auditable decrypt permissions.

Runner flow

  1. Register a runner device key.
  2. Approve access for specific repos or workflows.
  3. Decrypt only inside your runner environment.
  4. Emit signed build events back to the repository timeline.