Website • Releases • Documentation
Ctrlplane is the orchestration layer between your CI/CD pipelines and your infrastructure.
Your CI builds code. Your clusters run 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)
| Problem | How Ctrlplane Helps |
|---|---|
| Manual environment promotion | Auto-promote staging → prod when verification passes |
| "Did the deploy actually work?" | Automated verification via Datadog, Prometheus, HTTP checks |
| Deploying to 50 clusters is painful | One deployment definition, Ctrlplane handles the fan-out |
| No visibility into what's running | Unified inventory: which version, which cluster, which region |
| Inconsistent deployment policies | Centralized policy engine with flexible selectors |
- Gradual Rollouts — Deploy to targets sequentially with configurable intervals and verification between each
- Policy Gates — Require approvals, enforce environment sequencing, set deployment windows
- Automated Verification — Integrate with Datadog, Prometheus, or any HTTP endpoint
- Auto-Rollback — Automatically revert when verification fails
- Infrastructure Inventory — Unified view of resources across Kubernetes, cloud providers, and custom infra
- Pluggable Execution — Works with ArgoCD, Kubernetes Jobs, GitHub Actions, Terraform Cloud, or custom agents
- Platform teams building internal developer platforms
- DevOps/SRE enforcing deployment policies at scale
- Engineering orgs with 10+ services across multiple environments
- Multi-region deployments needing coordinated rollouts
The fastest way to get started is with Ctrlplane Cloud.
For self-hosted options, see our installation guide.
| Method | Link |
|---|---|
| Docker |  |
| Kubernetes |  |
- CI creates a version — Your build pipeline registers a new version with Ctrlplane
- Ctrlplane plans releases — Based on environments and selectors, it creates release targets
- Policies are evaluated — Approval gates, environment progression, gradual rollout rules
- Jobs execute — Ctrlplane dispatches to your job agent (ArgoCD, K8s Jobs, GitHub Actions)
- Verification runs — Metrics are checked; pass → promote, fail → rollback
- Quickstart — Deploy your first service in 15 minutes
- Core Concepts — Systems, deployments, environments, resources
- Policies — Approvals, verification, gradual rollouts
- Integrations — GitHub Actions, ArgoCD, Kubernetes
Development system must have Docker engine installed and running.
git clone https://github.com/ctrlplanedev/ctrlplane.git
cd ctrlplane
cp .env.example .env
docker compose -f docker-compose.dev.yaml up -d
cd packages/db && pnpm migrate && cd ../..
pnpm devAsk questions, report bugs, join discussions, voice ideas, make feature requests, or share your projects.
If you believe you have found a security vulnerability, we encourage you to responsibly disclose this and not open a public issue.
Email [email protected] to disclose any security vulnerabilities.