Creating Environments

Create environments that bind a blueprint to a target collection, configure properties, and manage the plan-apply-destroy lifecycle.

Overview

An environment in Bluebricks represents the binding between a Blueprint and a target Collection.It defines what should be provisioned (the blueprint composition) and where it should be provisioned (the collection’s cloud accounts and configuration).

Environments serve as the operational layer as they track the full lifecycle of infrastructure changes, from planning to applying, auditing, and teardown. Environments lets members of your organization, spin-up, update, or uninstall infrastructure from your blueprints. This guide walks you through creating an environment and understanding its possible statuses.

Environment Runs

An environment is the parent of all your runs. Each run represents an execution you perform within that environment, such as a plan, apply, or destroy action. The environment defines what you’re provisioning and where, while runs capture when and how those actions happen. Over time, your runs create a complete history of changes, making it easy for you to review, compare, or reapply past executions without redefining the blueprint or collection.

Creating an Environment

You can create an environment directly from the Environments page in the Bluebricks web app or by using the CLI and API if you prefer automation. Once the environment exists, each run within it can be initiated through multiple interfaces. You can trigger a run manually from the web UI, automatically through the API, or programmatically via webhooks or CI/CD pipelines. You can also initiate runs through MCP (Model Context Protocol) for seamless integration with compatible environments and tools. No matter how it starts, every run is fully tracked in the environment’s history, keeping your execution flow consistent and auditable across all interfaces.