RunWhen

RunWhen provides an automation and orchestration platform for operating and troubleshooting Kubernetes-based infrastructure.

• Automation workflows for Kubernetes operations and incident response (cloud DevOps)
• Orchestration of diagnostics, runbooks, and remediation across clusters and services (IT operations management)
• Integration with observability, ticketing, and Continuous Integration and Continuous Deployment (CI/CD) tools for event-driven operations (DevOps toolchain)
• Collaboration features that standardize Site Reliability Engineering (SRE) and platform engineering practices (site reliability engineering)
• Support for secure, governed automation suitable for regulated or enterprise environments (enterprise IT management)

More About RunWhen

RunWhen focuses on automation for Kubernetes and cloud-native operations, targeting teams that manage containerized workloads at enterprise scale. Its platform is used by SRE, platform engineering, and DevOps teams to codify operational knowledge into machine-executable workflows that can be triggered by events, schedules, or human operators. The goal is to reduce manual effort in day-to-day operations while keeping automation governed and observable.

The platform sits alongside existing observability and incident management tools rather than replacing them. It consumes alerts, metrics, and events from monitoring systems, issue trackers, and CI/CD pipelines, then orchestrates diagnostics and remediation through predefined runbooks. This positions RunWhen in the cloud DevOps and IT Operations Management (ITOM) categories, with emphasis on Kubernetes operations and troubleshooting.

RunWhen typically interacts with Kubernetes APIs, cloud provider services, and standard DevOps tooling, using common protocols such as HTTPS and standard authentication patterns including tokens and Single Sign-On (SSO) where supported by the surrounding ecosystem. Its workflows can encapsulate kubectl commands, Application Programming Interface (API) calls, and integrations with systems like logging platforms or ticketing tools. This lets teams encode complex multi-step procedures for incident triage, cluster health checks, or deployment verification into repeatable automation units.

For enterprises, the platform is positioned as a way to standardize operational processes across multiple clusters, environments, and teams. RunWhen provides governance features such as access control, auditability, and policy-aligned execution so that automation follows organizational compliance requirements. By centralizing operational runbooks and automations, organizations can reduce reliance on ad hoc scripts and tribal knowledge.

Within a technology directory or marketplace taxonomy, RunWhen fits into categories such as cloud DevOps, Kubernetes operations, incident response automation, and ITOM. It is relevant to organizations that operate production Kubernetes clusters, microservices architectures, or multi-cloud environments and need a structured approach to diagnostics and remediation that integrates with existing observability and ticketing ecosystems.