Connect Self-Hosted Infrastructure

Connect any cloud account or on-premise setup to Bluebricks using the self-hosted runner (BDC).

Prerequisites

• A Kubernetes cluster (version 1.28+) running in your infrastructure

• Helm 3.8 or later

• A collection created in Bluebricks (create one first)

• An environment token from Bluebricks (obtained during collection setup)

What Is a Self-Hosted Cloud?

A self-hosted cloud connects your own infrastructure — any cloud provider or on-premise setup — to Bluebricks. It requires installing the Bluebricks Deployments Controller (BDC), a Kubernetes operator that orchestrates IaC jobs inside your cluster.

Step 1: Install BDC in Your Cluster

helm repo add bbx-helm-repo https://storage.googleapis.com/bluebricks-helm-public
helm repo update

helm install bdc bbx-helm-repo/bluebricks-deployments-controller \
  --set orchestrator.secret.value=YOUR_ENVIRONMENT_TOKEN \
  --namespace bluebricks \
  --create-namespace

Replace YOUR_ENVIRONMENT_TOKEN with the token from your Bluebricks collection settings.

Step 2: Verify the Installation

# Check BDC pods are running
kubectl get pods -n bluebricks

# Stream operator logs
kubectl logs -f deployment/bdc-bluebricks-deployments-controller -n bluebricks

Step 3: Connect in the Bluebricks App

1. Open app.bluebricks.co/collections

2. Click Connect Cloud on the target collection

3. Select Self-Hosted as the cloud provider

4. Follow the prompts to complete the connection

Managing Cloud Accounts via CLI

# List all connected cloud accounts
bricks clouds ls

# List including inactive
bricks clouds ls --all

# Remove a cloud account
bricks clouds delete --slug <slug>

See also

• Self-Hosted Runner — full BDC architecture and installation guide

• Self-Hosted Configuration — BDC Helm values reference and tuning

• Collections — how collections use cloud accounts