Skip to main content

What is Ctrlplane?

Ctrlplane is the orchestration layer between your CI/CD pipelines and your infrastructure. Your CI builds code. Your infrastructure runs it. Ctrlplane decides when releases are ready, where they should deploy, and what gates they must pass—handling environment promotion, verification, approvals, and rollbacks automatically.
Your CI/CD    ──►    Ctrlplane    ──►    Your Infrastructure
 (builds)            (orchestrates)           (deploys)

Start Here

Two Core Systems

Common Use Cases

ScenarioWhat Ctrlplane Does
Multi-region deploymentsDeploy to 10 clusters sequentially with verification between each
Environment promotionAuto-promote staging → prod when verification passes
Deployment verificationCheck Datadog metrics before marking a deploy successful
Infrastructure inventoryAnswer “what version is running where?” instantly
Dynamic environmentsNew clusters auto-join environments via selectors

Who Uses Ctrlplane?

TeamUse Case
Platform EngineeringBuilding an IDP with deployment orchestration and infrastructure visibility
DevOps / SREEnforcing deployment policies and tracking what’s running where
Scaling StartupsMoving from “we manually deploy” to automated, policy-driven releases
Multi-region TeamsCoordinating deployments across clusters/regions with a unified inventory

How It Fits Your Stack

Ctrlplane doesn’t replace your CI or deployment tooling—it coordinates them:
LayerToolsWhat They Do
BuildGitHub Actions, GitLab CI, JenkinsBuild artifacts, create versions in Ctrlplane
OrchestrateCtrlplaneDecide when/where to deploy, enforce policies
ExecuteArgoCD, K8s Jobs, GitHub Actions, TerraformPerform the actual deployment
MonitorDatadog, PrometheusProvide metrics for verification

Next Steps