Backstage
Integrate Bluebricks with Backstage to let developers provision environments, browse blueprints, and manage infrastructure from the developer portal.
Overview
The Bluebricks–Backstage integration brings your infrastructure workflows directly into your internal developer portal. Backstage becomes the entry point for developers to discover services, provision infrastructure, and interact with collections—while Bluebricks remains the orchestration layer responsible for IaC execution, governance, and lifecycle automation.
With this integration, teams can:
Create new environments from Backstage using predefined Bluebricks Blueprints
View existing Blueprints and the latest versions available
View and edit existing environments, including updating inputs or configuration
Inspect environment status, recent runs, and collection health
Jump directly into Bluebricks with one click for deeper analysis or approval flows
This allows developers to interact with infrastructure in a consistent and self-service way, without leaving Backstage—while ensuring that all execution and policies still run through Bluebricks.
Key Capabilities
1. Create New Environments
From a Backstage service page, developers can spin up new collections based on a selected Blueprint. This allows:
On-demand creation of dev, preview, or ephemeral collections
Parameterized environment using Blueprint properties
Automated orchestration handled entirely by Bluebricks
This is ideal for self-service collection provisioning and sandbox workflows.

2. View Available Blueprints
Backstage displays the list of Bluebricks Blueprints that are available for use. Developers can browse these Blueprints directly from Backstage to understand what environment templates exist in the organization.
For each Blueprint, Backstage shows:
The Blueprint name
The description (when provided)
The latest available version
This gives developers a clear, centralized view of the Blueprints they can deploy—without needing to navigate into the Bluebricks UI.

3. View and Edit Existing Environments
For each Blueprint, Backstage surfaces its associated Environments (e.g., dev, staging, prod). You can:
See real-time environment status
Edit environment properties and trigger a new run with the changes
Edits made in Backstage flow directly into Bluebricks, preserving auditability and policy enforcement.

4. Open Environments in Bluebricks with One Click
Every Blueprint and Environment displayed in Backstage includes deep links to the Bluebricks app. With one click, developers can navigate to the full environment view to:
See complete run logs
Approve or reject pending runs
Inspect drift, configuration, or inputs
Access detailed infrastructure insights
This ensures smooth transitions between the developer portal and the orchestration engine.
Use Cases
Self-Service Collection Provisioning
Let developers create new environments (e.g., preview or dev collections) directly from Backstage, backed by a Blueprint. Bluebricks ensures the correct provisioning workflow and applies collection policies.
Collection Status at a Glance
Teams can quickly see which environments exist for a service, their status, last run results, and configuration—all from the Backstage service page.
Editing Environments Centrally
Developers can adjust environment properties (inputs, parameters, configuration) directly from Backstage, ensuring infrastructure changes flow through a consistent developer interface.
Click-Through to Bluebricks for Deep Analysis
While Backstage gives a high-level view, deeper operations—approvals, logs, plan diffs, drift details—remain available in Bluebricks. One click jumps the user into the exact environment context.
Integration Setup
To enable the Bluebricks–Backstage integration in your organization, please contact Bluebricks Support.
Our team will assist you with:
Plugin installation
API configuration
Authentication setup
Best practices for integrating Backstage with your existing Bluebricks collections
Last updated
Was this helpful?

