Automate Operations
with Runbooks

Trigger workflows in your favorite CI/CD tools to respond to incidents, integrate with your deployment process, or execute tasks across your infrastructure—all from a centralized Ctrlplane dashboard.

Run anything, anywhere, anytime

Ctrlplane connects to your existing CI/CD tools, letting you trigger your workflows from a central location in response to various events or conditions.

Incident Response

Trigger alert-based workflows in your CI/CD tools to automate recovery actions and minimize downtime.

Deployment Hooks

Execute your existing CI/CD pipelines at key points in your deployment lifecycle—before, during, or after changes.

Scheduled Maintenance

Trigger maintenance workflows in your CI/CD systems on a schedule without having to build new scheduling tools.

Batch Operations

Run CI/CD workflows across multiple resources or services with a single command from the Ctrlplane UI.

Resource-Level Actions

Execute specific workflows for individual VMs, Kubernetes clusters, databases, or services from one interface.

Metrics-Driven Actions

Connect with monitoring systems to automatically trigger the right CI/CD workflows when metrics cross thresholds.

Runbook Use Cases

Discover how Ctrlplane Runbooks can transform your operations and incident response

Automated Incident Response

When monitoring systems detect an issue, Ctrlplane can trigger the right CI/CD workflow to restart services, scale resources, or execute other recovery procedures before your team is even notified.

Monitor detects high error rate

Prometheus alert fires when error rate exceeds threshold

Runbook triggers automatically

Ctrlplane launches the appropriate GitHub Action workflow

Recovery actions execute

Service is restarted, cache is cleared, team is notified

Deployment Safety Checks

Connect pre-deployment workflows to validate infrastructure, check dependencies, and verify configurations before pushing changes to production. Post-deployment workflows can validate the deployment succeeded and trigger a rollback if needed.

Pre-deployment validation

Security scan, dependency check, schema validation

Deployment orchestration

Coordinated rollout across multiple services and regions

Post-deployment health check

Verify metrics, check endpoints, automatic rollback if needed

Why Use Ctrlplane for Workflows?

Ctrlplane doesn't replace your CI/CD tools—it enhances them by providing a unified interface to trigger and orchestrate workflows defined in the tools you already use and love.

No need to replace your current CI/CD tools
Use workflows already defined in your CI/CD tools
Trigger the same workflows across environments and teams
Centralized history and execution tracking
Resource-level and lifecycle-based triggers

Connect Existing Tools

Link to workflows defined in your favorite CI/CD systems

GitHub Actions

org/repo • workflow.yml

GitLab CI

group/project • job-name

Jenkins

instance • job-name

Powerful Trigger Capabilities

Multiple ways to execute your CI/CD workflows

•On demand from the Ctrlplane dashboard
•Per individual infrastructure resource
•Post-creation or post-deletion hooks
•Based on metrics and alert thresholds

Automation & Operations

One interface for all your workflows

Execute workflows from GitHub Actions, GitLab CI, Jenkins, and more—all from a single interface that ties them to your resources and deployment lifecycle.

Workflow Execution

Success

Workflowdatabase-backup.yml

TriggerScheduled (Daily)

Duration3m 12s

StatusAll steps passed

ToolGitHub Actions

Automate Operations with Runbooks