GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • docs home page
  • Deployment
  • Inventory
  • Reference
  • Architecture
  • GitHub
  • Community
  • Why Ctrlplane?
  • 5-Minute Overview
  • Quickstart
  • Installation
  • Ctrlplane vs Alternatives
  • Multi-Region Deployments
  • Environment Promotion

This view

  • Original page
  • New address

GeezerVison is showing docs.ctrlplane.dev — Introduction - docs

​
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 orchestrates the rest through three core concepts:
ConceptQuestion It AnswersExample
DeploymentWhat to deploy and how”API Service” deployed via ArgoCD
EnvironmentWhere to deploy”Production” = all clusters with env: prod
PolicyWhen to deploy”Only after staging succeeds and SRE approves”
Your CI/CD    ──►    Ctrlplane    ──►    Your Infrastructure
 (builds)         (what, where, when)         (deploys)

​
Start Here

Why Ctrlplane?

See the problems Ctrlplane solves—you’ll recognize them

5-Minute Overview

Understand the mental model quickly

Quickstart

Set up your first deployment pipeline in 15 minutes

Comparisons

How Ctrlplane fits with ArgoCD, Spinnaker, GitHub Actions

​
Two Core Systems

Deployment Orchestration

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

Infrastructure Inventory

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

​
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

Why Ctrlplane?

Problems you’ll recognize

Quickstart

Build your first pipeline

Was this page helpful?

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.