BuildBuddy is designed to be easy to run on-premise for those use cases where data absolutely must not leave a company's servers. It can be run your own servers, or in your own cloud environment. It supports major cloud providers like GCP, AWS, and Azure.
The software itself is open-source and easy to audit.
For companies, we offer an Enterprise version of BuildBuddy that contains advanced features like OIDC Auth, API access, and more.
There are three ways to run BuildBuddy on-prem:
Bazel Run: get the source and run a simple
- Docker Image: pre-built Docker images running the latest version of BuildBuddy.
- Kubernetes: deploy BuildBuddy to your Kubernetes cluster with a one-line deploy script.
The simplest method of running BuildBuddy on your own computer is to download and run it with "bazel run". Doing that is simple:
- Get the source
git clone "https://github.com/buildbuddy-io/buildbuddy"
- Navigate into the BuildBuddy directory
- Build and run using bazel
bazel run -c opt server:buildbuddy
We publish a Docker image with every release that contains a pre-configured BuildBuddy.
To run it, use the following command:
docker pull gcr.io/flame-public/buildbuddy-app-onprem:latest && docker run -p 1985:1985 -p 8080:8080 gcr.io/flame-public/buildbuddy-app-onprem:latest
If you run or have access to a Kubernetes cluster, and you have the "kubectl" command configured, we provide a shell script that will deploy BuildBuddy to your cluster, namespaced under the "buildbuddy" namespace.
This script uses this deployment file, if you want to see the details of what is being configured.
To kick of the Kubernetes deploy, use the following command:
For documentation on all BuildBuddy configuration options, check out our configuration documentation.