Code Security

To guarantee the security of your builds we use virtual machines for builds. Every build runs in its own, clean virtual machine and we discard the whole virtual machine after the build finishes, erasing every file your build uses and every change you make during your build.

This is also true for the Linux/Android stacks, which use Docker containers to run the build. The build itself still gets a full virtual machine where no other Docker container is started, only the one used as the environment of the build. In short we only use Docker containers to manage the environment, not for build environment isolation - that's ensured by using full virtual machines for every build.

This way your builds are always protected from changes made by others and from your previous builds, no one else can access your code and you can use a stable environment to define your build workflow. Every build is completed in an isolated environment, unrelated to any previous or paralelly running builds.

Source code

We don't store your source code. The source code is only accessed on the build machines (virtual machines) the way you define it in your Bitrise Configuration (workflow). If you don't have a Git Clone step in your configuration, then the source code won't be touched at all. At the end of the build the whole Virtual Machine is destroyed.

Code signing and other files

The files you upload in the Workflow Editor (Code Signing & Files section of the editor) are stored on Amazon S3 in a way that it's only accessible for the web servers.

The required credentials are not stored in any database, it is only available in the web servers' environment. Build servers can't access the files directly either. When a build starts the web server generates a read-only, time limited access URL for these files, using Amazon S3 presigned URLs.


Passwords are stored in a hashed, encrypted form. We are encrypting the passwords with bcrypt algorithm, using multiple stretches.