Like all startups, we spend a LOT of time talking to potential customers, trying to understand their pain points around infrastructure provisioning, spend and performance.

He can’t open his AWS bill because the file is too large for his laptop to handle

Many of our conversations with the C-suite came back to the difficulty they have rationalizing their cloud compute bill and connecting that spend directly to customer activity or revenue. During one of those meetings I had an eye opening moment when the customer confided he can’t open his AWS bill because the file is too large for his laptop to handle.

The Cloud Promise: Scale and Reduce Cost

The original promises of cloud computing were that it would scale easily, it would reduce capital expenditures and it would save money. The ability to instantly provision resources and scale has revolutionized IT in the era of DevOps. The reduction in capital expenditure requirements has helped spawn a new wave of lean startups and altered IT budgets and corporate balance sheets around the world.

Saving money has proven to be more ephemeral. It’s not that renting compute from Amazon, Microsoft, Google or IBM is necessarily more expensive than buying computers and putting them in a data center. The issue is that creating an infinite supply of compute that can be provisioned by anyone in your organization with a few expert strokes of a keyboard means that cost controls have been stripped away.

You wind up with a process that is so complex that a whole new industry called cloud cost monitoring sprang up for the sole purpose of helping make sense of your cloud bill.

No reasonable CTO is going to micromanage the decisions of their teams about what instance to choose or how to configure it. No annual review is going to ding someone for over provisioning a microservice or having too many VMs running – even when these decisions add up to millions of dollars. At the same time, few if any developers, members of the DevOps team or even their managers know how much is spent on compute or how much is spent by the code they deploy. Many devs will choose the largest available VM “just in case”, never even thinking about right sizing.

Add the complexity of most cloud pricing models and the excruciating detail included in a cloud bill and you wind up with a process that is so complex that a whole new industry called cloud cost monitoring sprang up for the sole purpose of helping make sense of your cloud bill.

Cloud Cost Optimization

A bill that is too large to open isn’t just a great metaphor and a decent pun. It is a clear, obvious and screamingly loud pain point. Rationalizing your AWS bill is not what Opsani chose to address. We realized that the underlying issue is much deeper.

It’s nearly impossible to balance cloud cost and cloud performance using conventional optimization.

Modern application architecture, development processes and DevOps bypass institutional cost controls while obscuring costs in a deluge of granular data. They create and reinforce a system where cost control rarely gets priority and is almost never rewarded. Setting aside the tremendous technical challenges for optimizing cloud infrastructure, saving 20% of compute costs per user session isn’t nearly as sexy in a standup meeting or an annual review as a 20% improvement in performance. To make matters worse, cost and performance are often owned by separate departments with different budgets.  This model makes it institutionally unlikely for companies to be able to optimize application performance while controlling costs.

Cost and service performance are two fundamental, deeply related KPIs presenting real pain to enterprises large and small. They are nearly impossible to balance with conventional optimization. THAT is the problem Optune was born to solve.

Continuous Optimization

Optune is AI for Continuous Optimization of cloud application performance. It reduces latency, increases throughput and controls cloud runtime costs automatically. Current beta users have found gains in performance between 15% and 200% while maintaining or lowering cloud costs. We’ve also seen Optune quickly find a 30% reduction in cloud costs while maintaining the current performance levels. What if you could flip a switch to dial back cloud costs while maintaining user satisfaction?

Give Optune 30 minutes for a demo and see if we can save you a couple of seconds… millions of times a day.