Pricing
"I saved four hours of downtime for the same price as a coffee."
Our Pricing Plan
Simple annual pricing for small teams or outcome-based pricing for larger enterprise deployments
- Number of incidents resolved autonomously
- Percent of cost savings capture from other contracts
- MTTR impact
Note this pricing is only available with Bring-Your-Own-LLM configurations.
A Typical Engagement Timeline
A typical PoC with RunWhen takes about 6 weeks, ending with a quantitative business case and proposal based on AI evaluation of your team's usage.
Pre-Installation 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.
per thousand tickets
>4 hours MTTR
<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.
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.
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 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.
