Environments
An Environment represents a concrete infrastructure target where your software runs. This could be a Kubernetes cluster, an AWS ECS service, a bare-metal server, a serverless function, or any other deployment destination.Managing Environments
Environments are managed via thechainloop environment command group. For example:
Logical Environments
A Logical Environment represents a lifecycle stage in your delivery pipeline. While Environments define the physical or virtual infrastructure, Logical Environments define the purpose or phase of a deployment, such as development, staging, or production. When you create an organization, Chainloop automatically provides three default logical environments:| Logical Environment | Description |
|---|---|
development | For development and testing |
staging | Pre-production validation |
production | Live production workloads |
qa, performance-testing, canary).
In an upcoming release, Logical Environments will also enable running Policies scoped to specific lifecycle stages — for example, enforcing stricter compliance checks for artifacts deployed to
production than to development.Managing Logical Environments
Logical environments are managed via thechainloop logical-environment command group. For example:
Next Steps
- Artifact Deployment Tracking — Record and query what’s running where
- Projects and Versions — Organize your software components