Create a deployment environment
A deployment environment is one destination for one service: a tier, an ordered workflow of adapter steps captured immutably in every plan, the connections those steps use, and an approval policy.
Create
Section titled “Create”- Choose New environment.
- Pick the Service and enter an Environment name.
- Pick the Tier: Development, Staging, or Production.
- Pick the Deployment method:
- Ansible playbook: an Approved working directory below a root allowlisted on the runner, an Inventory, a Playbook, and optional Fixed extra variables.
- Deployment webhook: a ready webhook Connection and the Webhook URL.
- Sandbox marker: a Marker path relative to the runner-owned sandbox root, for deterministic proof of the lifecycle without touching real infrastructure.
- Set the Runner labels a runner must carry to take this environment’s work.
- Enter a Readiness URL. It is required for production and optional otherwise, and adds an HTTP verification step expecting a 200 response after the mutating step.
- Choose Create environment.
Every environment requires approval, and a production environment can never disable it. The approval window defaults to sixty minutes.
Revisions and pausing
Section titled “Revisions and pausing”Each environment card shows its service, tier, revision, state, required labels, and workflow steps. There is no edit form; Pause and Activate are the only changes from this tab.
Pause blocks new plans and runs and stops already queued work from validating. Any change to an environment increments its revision and supersedes every plan that was Ready or Approved against the previous revision.