Platform

The platform is designed to get you up and running in one afternoon.

A typical deployment involves an agent running in your environment connecting to our SaaS of Self-Hosted back end.

Engineering Assistants can then suggest what to run when they receive slack messages, alerts, tickets, etc.

Self-service troubleshooting in shared environments
Faster ramp-up in cloud and container migrations
Automated alert repsonse
Automated scans for security, compliance and reliability
Automated info collection for failed tests, flaky CI/CD jobs

For Platform Teams

Out of the box, get thousands of automated AI-ready tasks from our experts. Give Engineering Assistants running credentials, and then give them to Devs, QA Engineers, SREs, etc.

For Software Developers

Self-service troubleshooting for other team’s microservices, platform and infrastructure. Find and run the right automation and escalate to the right people when needed.

For Executives

Get both AI and Automation initiatives going in 1/100th the time and 1/100th the cost of building and maintaining it in-house.

From Scripts to Sessions

Community: For community Authors, the RunWhen platform acts like their CI/CD platform with tools to turn a broad range of contributions in to Engineering Assistant-ready Tasks.

Setup: For platform teams, the RunWhen Local tool scans Cloud and Kubernetes accounts to match enterprise resources with Authors' contributions. It generates the required configuration automatically.

Troubleshooting: End users see the results when they start troubleshooting sessions where they collaborate with Engineering Assistants to find root causes, remediate or escalate.

#1

Authors and their scripts

RunWhen Authors in our community can mix and match a variety of programing languages using our Task file format.  When Authors register a git repository, the Platform builds, tests and augments Tasks with metadata from our AI models.  The metadata is ~10x the size of the original source code, effectively pre-computing thousands of scenarios where this code may be used.

#2

Building the map

RunWhen Local (an in-cluster agent) identifies application frameworks, open source projects, platform components and infrastructure that match with Tasks in the library.  Matches are sent to the RunWhen Platform to generate a Map of your environment that Engineering Assistants follow.

#3

Troubleshooting sessions

Troubleshooting sessions ("RunSessions") are the heart of the platform. In response to users' queries, alerts, webhooks, etc., Engineering Assistants follow the Map to suggest Tasks and run them on RunWhen Local instances in your cluster. Tasks cover a broad range of diagnostics, triage and remediation capabilities and are chained together to get to a root cause, a remediation or escalation.

blue dot grid

High Availability and Reliability

For RunWhen Hosted and Hybrid deployments, RunWhen is focused on providing a highly available and reliable platform.  For self-hosted, we provide optional professional services (through partners) for 24/7 operations.

Cautious Cathy profile picture

Hosted and Hybrid

Green check
Regional Kubernetes deployments in the Google Cloud Platform​
Green check
Scripts run in your clusters or in RunWhen clusters (configurable)
Green check
RunWhen-SaaS control plane that initiates script runs, telemetry, error recovery, etc.
Vivacious Venkat profile picture

Self Hosted

Green check
Regular self-hosted release channel that follows hosted and hybrid roadmap
Green check
Telemetry and operational tooling
Green check
Professional services available (through partners) for 24/7 SRE support

Ready to get started?

Let’s take your team to the next level.

Cautious Cathy profile pictureVivacious Venkat profile pictureEager Edgar profile picture