Pricing

"I saved four hours of downtime for the same price as a coffee."

RunWhen costs ~$5 per session

1/100th the cost and 10x the speed of doing incident investigations by hand

Enterprise outcome-based contracts at scale

Start a Free Trial Talk to an Expert

Our Pricing Plan

Simple annual pricing for small teams or outcome-based pricing for larger enterprise deployments

image showing the impact of driving down kubernetes costs

Agent Sessions

Price

Description

5,000

sessions

$25k / year

Typical for a 3-4 person Dev/Ops SRE team supporting 20-50 developers using RunWhen interactive agents and some critical alerts sent to background agents.

10,000

sessions

$45k / year

Typical for a 5-10 person DevOps/SRE team supporting 50-100 developers using RunWhen interactive agents and all critical alerts sent to background agents.

25,000

sessions

$115k / year

Typical for a 5-10 person DevOps/SRE team supporting 50-100 developers using RunWhen interactive agents and noisy alerts sent to background agents.

Unlimited

sessions

Outcome-based pricing

We will work with your team to create an outcome-based annual contract, e.g.:
‍
- Reduction in escalations per month
- Reduction in headcount per incident
- Reduction in MTTR

Note this pricing is only available with Bring-Your-Own-LLM configurations.

A Typical Engagement Timeline

In a large organization, RunWhen typically starts with infrastructure SRE or platform teams that are "guilty until proven innocent." After freeing up their time, they serve as automation ambassadors for a team-by-team roll-out across applications.

1
hour

Install Defaults

Install local runner with read-only cloud/kubernetes credentials

1
week

Background Learning

Let agents run read-only automation in the background to learn the environment

2-4
hours

Workshop

1-2 senior engineers ask typical first responder questions

Target ~50% "thumbs up" rate that this would have avoided an escalation

30
days

30 New Tools

Our FDEs work with your team to build 30 new tools in 30 days to integrate with you apps, data and toolchain

1-2
days

PoC Wrap-Up

3-5 senior engineers ask typical broader range of questions
‍
Target ~90% "thumbs up" rate that this would have avoided an escalation‍

An Incident Analysis?

Prior to an installation, our team can help with tools to that analyze your existing alerts or tickets to build a preliminary business case.

Before

After RunWhen

900

Engineering hours
per thousand tickets

80%

of tickets with
>4 hours MTTR

156

Engineering hours per thousand tickets

56%

of tickets with
<1 minute MTTR

Automation can cut observability costs

Some of our most popular automation libraries copy logs directly from pods and VMs into Jira/Github tickets. Connecting this to VSCode, alerts and CI/CD webhooks removes the need to ingest and store 90%+ of non-prod logs.

Talk to an Expert

Operate at lower cost with AI Engineering Assistants

Kubernetes stands as a cost-effective cloud platform choice. Integrating AI tools for non-experts, like app developers or junior SREs, brings a 60% reduction in KTLO engineering costs.

Get a KTLO Analysis

Test your assumptions quickly with Enterprise PoC

RunWhen offers a troubleshooting library for all environments, streamlining knowledge and consolidating tools.

Talk to an Expert

Get started quickly with the RunWhen PoC/PoV guide

This document provides reference materials for architecture, security reviews, sample discussion guides, and outlined directions for quantitative business case development. Additionally, PoCs include weekly check-ins with the RunWhen engineering team and support via email, Slack, and video conferencing during US Eastern business hours.

Thank you! Your guide will be downloaded automatically in a few seconds. Or click here to download it manually.

Something went wrong while submitting the form. Please try again.