Skip to main content
Ctrlplane’s deployment system orchestrates releases across environments with configurable policies, verification, and approval workflows.

What is Deployment Orchestration?

Deployment orchestration manages how releases flow through your environments — from build to production — with:
  • Progressive delivery — Canary, blue-green, and phased rollouts
  • Policy-driven gates — Approvals, verification, and dependencies
  • Environment promotion — Automated staging → production progression
  • Rollback & recovery — Automatic rollback on verification failure

Core Concepts

How It Works

1. CI Creates Versions

Your CI pipeline creates a version after successful builds:
- name: Create Version
  run: |
    curl -X POST ".../deployments/$DEPLOYMENT_ID/versions" \
      -d '{"tag": "${{ github.sha }}", "status": "ready"}'

2. Ctrlplane Creates Releases

For each release target (deployment × environment × resource), Ctrlplane:
  1. Evaluates policies (approvals, gates, dependencies)
  2. Creates a release with the new version
  3. Dispatches a job to the job agent

3. Job Agents Execute

Job agents perform the actual deployment:
  • GitHub Actions — Trigger workflows
  • ArgoCD — Create/sync Applications
  • Terraform Cloud — Create workspaces and runs

4. Verification Validates

After deployment, verification checks health:
verification:
  metrics:
    - name: error-rate
      provider:
        type: datadog
        queries:
          errors: "sum:errors{service:api}.as_rate()"
      successCondition: result.queries.errors < 0.01

Policies

Policies control how releases flow through environments:

Job Agents

Execute deployments on your infrastructure:

Key Benefits

BenefitDescription
Consistent processSame workflow for all deployments
Policy enforcementGates prevent unauthorized releases
VisibilityTrack what’s deployed where
Automatic rollbackFailed verification triggers rollback

Next Steps