Pricing

1/100th The
Cost Of Manual Work

Green check
RunWhen charges ~$5 per "RunSession," about 1/100th the cost of doing the same work by hand
Green check
A RunSession starts when an Engineering Assistant responds to an alert* or a chat, running Tasks and drafting a ticket
Green check
The platform tracks MTTR and productivity impact of each RunSession, comparing it to benchmarks set by our experienced Task authors
Start a Free TrialTalk to an Expert
Eager Edgar profile pictureVivacious Venkat profile picture
* Noisy alerts? No problem. RunWhen does alert de-duplication before starting a session.

Our Pricing Plan

blue dot grid

How many alerts and chats is your team chasing down every day?

image showing the impact of driving down kubernetes costs
RunSessions
Price
Description
5,000
sessions
$25k
For teams handling 12-15 alerts and chats and creating ~1-2 tickets per day, this is enough for a year,
10,000
sessions
$45k
For teams handling 25-30 alerts and chats and creating ~2-3 tickets per day, this is enough for a year,
25,000
sessions
$100k
For teams handling 65-75 alerts and chats and creating ~5-10 tickets per day, this is enough for a year,
(This package also includes $10k RunWhen match for bounties paid to authors to develop new tasks for the platform)
Unlimited
sessions
We will work with you to customize plan that fits your team.

A Typical Engagement Timeline

blue dot grid

A typical engagement takes about an hour to install, an afternoon to customize and 3-6 weeks to collect analytics

1-2
hours

Install Defaults

Default read-only tasks, default Assistants

1-2
weeks

Vibe Test

Let your team vibe test with interactive troubleshooting and responses to default alerts

2-4
hours

Workshop

Add more Assistants, connect to alerts or install the slack app

2-4
weeks

Collect Analytics

Let the system respond to alerts and chats, generating mock tickets and analytics

1-2
days

Wrap-up

Business case proposal based on analytics

Pre-Installation Analysis

blue dot grid

Prior to an installation, our team can help with tools to that analyze your existing alerts or chats, measuring which would turn in to automated sessions with Tasks currently in our library.

Before
After
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

blue dot grid

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.

image showing the impact of driving down kubernetes costs

Test your assumptions quickly with Enterprise PoC

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

Get started quickly with the 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.
blue dot grid