Skip to main content

​
Sound Familiar?

The pain: You check Kubernetes, then AWS console, then your team’s spreadsheet. 15 minutes later, you’re still not 100% sure.With Ctrlplane: Single inventory showing every resource and its current version, updated in real-time.
The pain: Slack message sent. Thread dies. Deploy sits for hours. You ping again. Finally someone approves at 6pm.With Ctrlplane: Built-in approval workflows with notifications. Approvers see pending releases in one place.
The pain: Manual step someone forgets. Or worse, staging didn’t actually pass but prod got deployed anyway.With Ctrlplane: Auto-promote to production only when staging verification succeeds. No manual intervention needed.
The pain: Update 6 config files, 3 CI pipelines, and remember to tell the team. Miss one and deploys fail silently.With Ctrlplane: New clusters auto-join environments via selectors. Tag it env: production and it starts receiving deployments.
The pain: Scramble to find the right commands. Which version was stable? Did we roll back all regions? Did we miss one?With Ctrlplane: Automatic rollback when verification fails. One-click manual rollback when needed.
The pain: Either deploy to all at once (risky) or manually babysit each region (slow and error-prone).With Ctrlplane: Gradual rollouts deploy one region at a time, verify health, then continue—automatically.

​
The Problems at Scale

When you have 5 services and 2 environments, everything is manageable. When you hit 20+ services across 4 environments and 8 clusters, you start feeling the pain:
ChallengeWhat Teams Do TodayWhat Goes Wrong
Environment promotionManual deploy after checking stagingSomeone forgets, or staging wasn’t actually verified
Deployment verification”It deployed successfully!”Service is broken, but pipeline says green
Infrastructure visibilitySpreadsheets + multiple dashboardsOutdated info, no source of truth
Adding new infrastructureUpdate configs everywhereMiss something, deploys fail
Multi-region deploysSequential manual deploys or YOLO all-at-onceToo slow or too risky
RollbacksAd-hoc scripts and hopeInconsistent, slow, error-prone

​
How Ctrlplane Helps

Ctrlplane is the orchestration layer between your CI/CD pipelines and your infrastructure: 
Your CI/CD    ──►    Ctrlplane    ──►    Your Infrastructure
 (builds)            (orchestrates)           (deploys)

​
Two Core Systems

Deployment Orchestration

Controls when and where releases happen:
  • Auto-promote after verification
  • Approval gates for production
  • Gradual rollouts across regions
  • Automatic rollback on failure

Infrastructure Inventory

Tracks what exists and what’s running:
  • Real-time resource inventory
  • Dynamic environment membership
  • Version tracking across all targets
  • Works with K8s, AWS, GCP, custom

​
What Ctrlplane Is NOT

Ctrlplane doesn’t replace your existing tools—it coordinates them:
  • Not a CI system — Your CI (GitHub Actions, GitLab, Jenkins) still builds code
  • Not a GitOps engine — ArgoCD/Flux still syncs manifests to clusters
  • Not infrastructure provisioning — Terraform still creates your resources
Ctrlplane decides when deployments should happen, where they should go, and whether they passed verification.

​
Quick Example

Here’s what deployment orchestration looks like with Ctrlplane: 1. CI builds and creates a version: 
ctrlc api upsert version \
  --workspace my-workspace \
  --deployment $DEPLOYMENT_ID \
  --tag v1.2.3
2. Ctrlplane automatically:
  • Calculates which release targets need this version
  • Deploys to staging first (environment progression policy)
  • Runs verification checks against Datadog metrics
  • After staging passes, requests approval for production
  • Once approved, gradually rolls out to production clusters
  • Verifies each cluster before proceeding to the next
  • Auto-rolls back if any verification fails
3. You get:
  • Full visibility in one dashboard
  • Consistent process every time
  • Confidence that verification actually passed

​
Next Steps

5-Minute Overview

Understand the mental model

Quickstart

Set up your first deployment pipeline

Use Cases

See specific scenarios solved

Comparisons

How Ctrlplane compares to other tools