Pricing

From tutorials to trials

Green check
A Kubernetes environment can be trial-ready in less than an hour. Expect a few weeks with the RunWhen team for VM-based applications.
Green check
In an afternoon workshop, we can help add tasks specific to your applications and integrate with alerts, Slack, VSCode, etc.
Green check
At the end of a PoC, the RunWhen team can export usage data to create an ROI analysis for executives.
Download PoC GuideTalk to an Expert
Eager Edgar profile pictureVivacious Venkat profile picture

Our Cost Savings Guarantee

blue dot grid

While our pricing is consumption based, we offer preliminary usage reports on the estimated cost savings that RunWhen is providing your team and a 50% cost saving guarantee based on these reports. 
Talk to our team to find out just how much your team can benefit from these savings.

1-2
hours

Install

Default tasks

1-2
weeks

Automate Response

Automate Response to Tickets and Help Requests

2-4
hours

Workshop

Add non-default tasks and Integration

2-4
weeks

Setup Alerts

Configure and prioritize alert response

1-2
days

Wrap-up

ROI Analysis proposal

Our Pricing Plan

blue dot grid

RunWhen automates the next steps to alerts, tickets, and chat responses with “RunSessions”

image showing the impact of driving down kubernetes costs
RunSessions
Price
Description
5,000
sessions
$25k
For teams handling 12-15 alerts, tickets and chats per day, this is enough for a year,
10,000
sessions
$45k
For teams handling 25-30 alerts, tickets and chats per day, this is enough for a year,
25,000
sessions
$100k
For teams handling 65-75 alerts, tickets and chats 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.

KTLO Analysis

blue dot grid

Start with an analysis done based on tickets, alerts or chat conversations to show where improvement will impact engineering teams.

Before
After
1800
Engineering hours
for 2,000 tickets
80%
of tickets with
>4 hours MTTR
312
Engineering hours
for 2,000 tickets
56%
of tickets with
<1 minute MTTR

Automation can cut observability cost

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 99%+ 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