Deployments

Deployments

Overview

Deployments in Bluebricks provide a consistent, controlled, and repeatable way to execute a blueprint against a specific environment. A deployment represents the ongoing workflow responsible for provisioning, updating, and destroying all infrastructure defined by the blueprint—across every package, artifact, and dependency it contains.

Once created, a deployment serves as the stable interface for managing the lifecycle of your infrastructure in that environment. It centralizes configuration, tracks every change, and ensures that updates are performed safely and predictably, regardless of how they are triggered.

How Deployments Work

When you run a deployment, Bluebricks evaluates the blueprint and all of its child packages to produce a unified execution plan. This plan captures every expected change across all layers of infrastructure, allowing you to:

• Preview changes before applying them

• Understand the full impact of updates

• Maintain an auditable history of every modification

Each execution of a deployment creates a run, which encapsulates the plan, logs, state updates, and resulting outputs. Runs are fully versioned and traceable, enabling teams to understand how infrastructure evolves over time and why each change was made.

Why Deployments Matter

Deployments provide the backbone of infrastructure management on Bluebricks by delivering:

• Consistency — every change is executed using the same workflow and evaluation logic

• Traceability — each run is captured with logs, diffs, inputs, and outputs

• Repeatability — deployments can be re-run safely at any time, enabling iterative updates

• Separation of concerns — blueprints define what should exist, deployments define where and how it’s applied

• Safety — approval flows, environment policies, cost checks, and unified plans help prevent unintended changes