January 2026

Source to Blueprint

This release focuses on streamlining blueprint composition directly from source, improving cloud account visibility, and enhancing infrastructure-as-code (IaC) hydration for more reliable deployments.

🚀 New Features

In-Line Blueprint Creation from Source

You can now add new packages directly from a Git source during the blueprint composition flow. This includes a dedicated "New package" flow that lets you select a technology, enter Git sources, and manage metadata without leaving the blueprint page.

What does it mean for you?

A much faster authoring experience. You no longer need to pre-register packages; you can pull them into your blueprint on the fly, with the system intelligently pre-filling details and persisting sources after publishing.

⚡ Improvements

S3-Backed Logs with Presigned URLs

To improve performance and scalability, deployment logs can now be stored in S3. The API now supports generating 60-minute presigned URLs for log retrieval, while maintaining backward compatibility for older logs stored in Postgres.

Accurate Child Package Hydration

We've enriched the blueprint format to preserve child package metadata during hydration. This ensures that even if you override output names, the backend can accurately track and display outputs for artifact-published packages.

Unified Cloud Account Visibility

We've aligned the display of Discovery and Orchestration accounts across the entire platform. Whether you are in the Environment table, the Graph view, or Account Settings, the labeling and modal behavior are now consistent.

Standardized Blueprint Terminology & Options

• Terminology Update: We've replaced "Slim" terminology with standard product language. You can now "View manifest" to see your bricks.yaml or bricks.json directly.

• Action Consolidation: Blueprint actions are now normalized across the app, replacing multiple "Review" variations with a single, clear "Review deployment" entry point.

• Plan Page Clarity: The "Deployer" label on the Plan page has been updated to "Initiated by" to more accurately reflect the user who started the run.

Modernized Job Scheduling

The job scheduler's data ownership has moved directly into the Bluebricks API. This architectural shift ensures that schedule changes are persisted immediately and allows for more robust queue reconstruction.

Framework & Security Enhancements

• JWT Passthrough: Cloud to Code agent calls now support JWT passthrough for authenticated callbacks, enhancing security for generation flows.

• Tailwind CSS v4: We have upgraded our styling engine to Tailwind CSS v4 as part of our ongoing commitment to modern, high-performance dependencies.

🐛 Bug Fixes

Consistent Deployment State Locations

Fixed an issue where state files were occasionally created in the incorrect directory during the Plan phase. All state and backup files are now consistently stored alongside the DAG for reliable file layouts.

Duplicate Prop Key Consolidation

The backend now correctly identifies duplicate prop keys across multiple packages and maps them to a single input ID, preventing cluttered UI forms and redundant data entry.

Members List & Pagination Reliability

Resolved a backend crash that occurred when navigating the members list if a user record was missing an email address. Pagination now works reliably across all user sets.

UI & Layout Fixes

• Zoom Accessibility: Fixed the Environment page cost block so it remains fully accessible and readable even when browser zoom is increased.

• Avatar Alignment: Standardized creator avatars to 24x24 pixels across the Deployment, Plan, and Environment pages for better visual hierarchy.

• Packages Sorting: Fixed the "Published by" column in the Packages table to correctly sort by the most recent timestamp.

• Empty State Interactions: Removed a broken "Edit input" action that appeared in empty deployment states, preventing the modal from closing prematurely.

Connect. Import. Accelerate.

This release introduces native Slack and GitHub integrations, a powerful new "Cloud to Code" import workflow, and significant performance enhancements to our cloud discovery and deployment engines.

🚀 New Features

Slack Integration

We've enabled comprehensive Slack integration management directly within Bluebricks. This includes OAuth-based connectivity, organization-level enablement, and the ability to trigger interactive actions directly from Slack messages.

What does it mean for you?

Streamline your workflows with real-time deployment notifications and take action without leaving your Slack workspace.

GitHub Integration

A new GitHub integration is now available under Account Settings. This feature includes a dedicated management page to connect your GitHub organizations and view all connected repositories.

What does it mean for you?

Easily link your source code providers to Bluebricks, providing better visibility and a tighter connection between your repositories and managed blueprints.

Cloud to Code: Automated Blueprint Import

We've introduced a new backend workflow that transforms discovered cloud resources into managed Blueprints. This API-driven process utilizes a sidecar agent to perform deep discovery and streams real-time status and logs back to the UI via WebSockets.

What does it mean for you?

Significantly reduce the time spent on manualizing existing infrastructure. You can now import live cloud resources and turn them into version-controlled Bluebricks packages with full visibility into the import process.

⚡ Improvements

Add from Source (Artifactless Projects)

You can now register packages directly from a raw source string. The system automatically detects the IaC type, clones the repository, and hydrates the package via bricks.yaml. If no blueprint file exists, it uses intelligent auto-detection to publish the package.

What does it mean for you?

A smoother onboarding experience for existing codebases, allowing you to bring in raw source code and let Bluebricks handle the complexity of hydration and publishing.

Scalable Cloud Discovery Runtime

We’ve re-engineered our discovery engine to use per-tenant orchestrated pods. This update includes dynamic configuration refreshing, ensuring that provider connections are always up-to-date and isolated for better performance.

Proactive Infrastructure Monitoring

New automated alerting has been implemented for our internal caching layers. By monitoring for memory-related incidents (OOM) in real-time, we can mitigate potential performance degradation before it impacts your experience.

🐛 Bug Fixes

Reliable Apply Artifacts

Fixed an issue where deployment state files were generated in inconsistent locations. State files are now correctly placed alongside the deployment graph, ensuring consistent runner output and more reliable state management.

Prevent Duplicate "Approve & Apply" Submissions

Added client-side protections to prevent multiple approval requests caused by accidental double-clicking. This ensures a cleaner audit trail and prevents redundant deployment executions.

Accurate Deployment Metadata

Resolved a UI bug where the deployment overview would sometimes show the most recent activity user instead of the original deployment creator. The overview now accurately reflects who initiated the deployment and when.

Environment Duplication Fix

Fixed a bug in the environment setup flow where using shared discovery or execution roles could result in the creation of redundant, duplicate environments.

Enhanced Validation for Complex Input Types

Added frontend validation feedback for complex property types, including maps, lists, and tuples. This prevents silent errors by ensuring all required complex inputs are valid before you hit deploy.