Replace toil with Engineering Assistants, split the savings 50/50
Engineering Assistants provide self-service support for developers while freeing up Kubernetes experts. Improve developer experience, replace toil with Engineering Assistants, and share the cost savings.
Bring on-call in-house
Replacing low-cost on-call services with automation frees up enough budget to add high-end SREs to your team.
The vast amount of automation required is hard to justify if you need to write it all yourself. It takes too long and costs too much. Leveraging our shared libraries makes the ROI simple (and fast).
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.
Workspace example and recommended tiers
18 point workspace
This work space is appropriate for troubleshooting a single application that roughly corresponds to a small team or 1-2 Kubernetes namespaces.
This workspace falls into our “<25” size, appropriate for a small application team and would most likely fall in the Growing tier unless specific security considerations require the At-Scale tier.
78 point workspace
This work space is appropriate for troubleshooting a range of the platform services typical in a medium size dev, test or production kubernetes cluster.
This workspace falls into our “51-100” size. If it is used only by the platform team, it is most likely in the Low Usage tier (Free) though our open source project may be a practical alternative.
333 point workspace
This workspace would likely span 2-5 application teams served by a platform team for a dev/test environment of a ~50-100 person engineering team.
This workspace most likely starts in the Growing tier for the first year and then graduates into the At-Scale tier as application teams use it more heavily than going directly to the platform team.
4,000 point workspace
This workspace has 4,000 SLXs with multiple different maps, each for different teams. It would likely span 5-50 application teams served by a platform team with multiple clusters representing various dev/test/prod environments.
This workspace most likely starts in the At-Scale tier and would be priced at $8/point.
Frequently asked pricing questions
If your questions are not answered below, please contact our team directly via info@runwhen.com.
How do I know many points on the map I need?
Join the RunWhen Beta in order to go through the Workspace Building process with our team and estimate the number of points needed in your finished Map.
Where can I calculate my RunWhen platform cost?
When you join our Beta, the RunWhen Team will price out your unique environment requirements.
Is RunWhen Local free to use?
Yes, RunWhen Local is a free and open-source tool that provides a tailored troubleshooting cheat sheet for Kubernetes environments.
Do you offer free trial?
Sign up for our Beta to try the RunWhen Platform for yourself. Before purchase, we will give you direct access to our sandbox environment where you can safely tour and troubleshoot our tech stack before setting up your own instance.
Do you limit number of members per subscription account?
The RunWhen Platform is built with collaborative troubleshooting in mind for any team size. To discuss your unique team's requirements, sign up for our Beta!
