An Infrastructure Blueprint defines a reusable infrastructure pattern that can be applied to two or more Infrastructure Environments.
The blueprint identifies common infrastructure structure and intent without binding that structure to one environment instance. The blueprint may identify:
An Infrastructure Blueprint differs from an Infrastructure Configuration:
Applying an Infrastructure Blueprint may produce or contribute to an Infrastructure Configuration for a particular Infrastructure Environment.
Environment-specific values may be supplied through parameters, inherited configuration, or explicit overrides without changing the reusable blueprint content.
reusable specification of infrastructure resources, relationships, configurable properties, and constraints applicable to two or more infrastructure environments
Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
An Infrastructure Blueprint does not represent a deployed Infrastructure Environment.
An Infrastructure Blueprint may use a declarative and machine-readable representation.
The term does not require a particular configuration language, file format, provisioning technology, cloud provider, virtualization platform, container platform, or operating system.
Changes to environment-specific parameters do not constitute changes to the Infrastructure Blueprint when the reusable blueprint content remains unchanged.
An Infrastructure Blueprint specifies a common application environment comprising compute, storage, network, access-control, logging, and monitoring resources. Development, test, and production Infrastructure Configurations apply the same blueprint with different capacity, address, retention, and access values.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.