An Infrastructure Environment is the bounded collection of infrastructure resources, configuration values, relationships, and constraints required to provide an identified operational or development context.
An Infrastructure Environment describes the infrastructure context as a whole rather than an individual resource within that context.
An Infrastructure Environment may include:
Examples of Infrastructure Environments include development, integration, test, staging, production, training, classified, unclassified, connected, disconnected, and Air-Gapped Environments.
An Infrastructure Environment differs from an Infrastructure Configuration:
environment comprising an identified collection of infrastructure resources, configuration values, relationships, and constraints established for a defined operational or development purpose
Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
An Infrastructure Environment may exist as a planned desired state, a deployed environment, or an observed operational state.
The term does not require a particular deployment technology, cloud provider, virtualization platform, container platform, operating system, or physical infrastructure.
An Infrastructure Environment may inherit configuration from another Infrastructure Environment or may use a shared Infrastructure Blueprint, but the environment remains independently identifiable.
A production Infrastructure Environment may include compute instances, storage volumes, network segments, access controls, monitoring services, configuration values, and applicable Baseline references required to operate an application in a controlled production context.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.