Blueprint
Blueprints are declarative representations of your overall application's architecture. They serve as a comprehensive plan, enabling you to design every aspect of your product without deploying resources to the cloud.
They encapsulate all configurations required to create and manage cloud environments, including resource definitions, service discovery, and secrets. Stored as files in a Git repository, blueprints provide a single source of truth for infrastructure design and deployment.

A sample blueprint in Facets
Benefits of using Blueprints
Consistency and Zero Drift
Blueprints ensure that all your environments follow the defined architecture unless explicitly overridden. You can always compare an environment against the blueprint defaults, maintaining consistency across deployments.
Default Configurations
Blueprints let you set default configurations. For example, if you set your production configuration as the default, you can launch a performance environment identical to production whenever needed.
Single Source of Truth
Blueprints act as a single source of truth for your infrastructure. They help you tag resources correctly for billing and cost tracking. Since blueprints capture everything needed to run an environment, including resource configurations, service discovery, and secrets, you can launch environments with a single click.
Efficient Resource Management
Blueprints help you manage resources by defining and tagging them correctly. This ensures your cloud infrastructure is organized and costs are tracked accurately.
Version Control with Git
Every Blueprints reside in a Git repository, so all infrastructure changes are versioned and under your control. This approach offers several advantages:
- Versioning: Fine-grained versions in resource configurations are beneficial as your team grows. You can use PR raise and merge flows similar to your code for infrastructure, observability, and application configuration changes.
- Innovation: Infra-as-Code files in JSON allow internal teams to be innovative. Some customers have written Slack bots for resourcse creation, policies to scan before each release, and automation to rightsize resources based on feedback from observability platforms.
Updated 9 days ago