Show HN: I built a service to help companies save on their AWS bills
We help companies drive down AWS costs. Why? Because the way it's done now is a pain. Stakeholders, especially engineers, are required to spend unnecessary time manually finding underutilized or overly expensive EC2s. We believe the optimization process should be done automatically through a series of sophisticated algorithms. At the moment, there are over 70,000 AWS EC2 prices - doing that manually just won't scale at most organizations. My background is in software engineering.
Previous to founding Usage, I worked on high-performance computing research at JP Morgan Chase and as a software engineer at a number of smaller startups.
Here's how it works: We are typically hired by the head of engineering. Usage makes its initial analysis of your organization's AWS usage, then it's passed to a human that manually verifies each recommendation for correctness. The human in the loop may reach out to if they are unsure about a particular recommendation.
We make money off of a monthly subscription to manage all of your organization's AWS spend management. Our fee is based on your organization's size and ranges from $2.5k-$10k/month. Happy to chat directly [email protected]
Have you experienced any issues with managing your company or organization's AWS expenses? We'd love to hear your feedback and ideas!
The top comment is great. Two easy wins:
* Putting an S3 endpoint in your VPC gives any traffic to S3 its own internal route, so it's not billed like public traffic. (It's curious that this isn't the default.)
* Auto-shutdown your test servers overnight and on the weekends
[0] https://news.ycombinator.com/item?id=15587627
I started using Finala a couple of months ago out of experimentation, it works well, but you need to tweak the configuration a lot to help the tool understand your infrastructure, spending habits and normal usage. My colleagues are very happy with the results, we started saving ±1.8k per month, which is pocket change for our scale but is still money that we can spend on other things.
I'd say the biggest difference is that we handle everything (so that engineers can focus on actual product dev) and also offer white-glove service to all of our customers. For midsized and up, we offer 24/7/365 access to an engineer for any questions or problems with the Usage dashboard.
Of course, a company's usage will change over time, but I don't see how that's worth the monthly fees advertised.
> optimization process should be done automatically through a series of sophisticated algorithms
> ...then it's passed to a human that manually verifies each recommendation for correctness
So how much of the heavy lifting is actually done by the algorithms?
But usually it's also about visibility. Services like CloudHealth give you much better billing overview than what AWS gives you. Without that data you may have a lot of blind spots and budget management is much harder. I think the long term value is billing visibility even for companies with good AWS experts.
I think the math behind saving algorithms isn't too complicated. It's just hard to get it around your head specially when you have too many resources. So it's not practical to do it without these tools.
You will be surprised how much inefficiency developers can produce. Especially with infrastructure as code it's just too easy to create oversized resources and forget about them.
Many companies also have a lot of inefficiency with their architecture. So it makes sense to outsource savings on EC2 instances to a service like this and let your internal talents to focus on architecture optimizations where you can probably even save more money.
Every recommendation is first produced by a model. Then for a recommendation, we add a human to the cycle that understands the client's infrastructure and adjusts the confidence score accordingly. The savings are then shown on a user's dashboard - alongside an analysis report.
When we onboard a new customer, we spend time understanding their infrastructure plans. Then we keep that information for our human-in-the-loop.
> why wouldn't a company hire a contractor to do the same thing you do for a one-off fee? I just don't see why this is a subscription model
This is something I am curious about as well.
1. Annual recommendations (Reserved Instances, Savings Plans) Sure, if a company only wants these recommendations - they can bring on a contractor once per year to do these changes. This is the one-off fee type contractor the poster is talking about
2. Continuous recommendations (Rightsizing, Spot Management) These recommendations are typically not something you could do once and be done. Rightsizing (which includes zombie instance detection) can happen through time. Spot Fleet management is also a continuous play - spot prices fluctuate and Usage's strategy works hard to maximize savings while minimizing downtime.
You might ask, how does this compare to hiring a contractor full time?
If you're a midsized company, Usage charges $5k/month (or $60k/year). A fulltime contractor in SV would likely be at least $100k/year and that doesn't factor in the number of billable hours (through interviewing) it would take to find someone who knows 50%+ of all of AWS' features.
Additionally, our growth and enterprise plans all have guaranteed savings. 3x and 5x, respectively.
For instance, if you chose the growth plan ($5k/month) and saved less than $180k after 12 months, we'd give you a 100% refund.
Similarly, if you chose the enterprise plan ($10k/month) and saved less than $600k after 12 months, we'd give you a 100% refund.
Good question!
With Usage, every enterprise customer gets their own fine-tuned model. AWS compute optimizer throws the same standardized model to all of their users. I can't compare our models to the ones AWS compute optimizer uses - but I can tell you that we've never had a complaint about a customer taking a recommendation and regretting it later on.
Additionally, we have humans look over every recommendation to ensure quality. Typically we have an understanding of a customer's cloud infrastructure before they sign up for Usage - and the human in the loop uses that information to grade recommendations produced by Usage's models.
Interesting project! This product can unlock a lot of customer savings, and wishing you all the best.
I have a couple of questions:
- Are you focusing on EC2 compute costs or are you focusing on other AWS offerings as well? Curious to see how the savings compare to EC2 compute optimizer [1].
- How is your churn rate? What is the value of your product once a customer optimized their AWS bill?
- Do you have a screencast of your product?
[1] https://aws.amazon.com/compute-optimizer/
2. Rightsizing and spot fleet management keep our users coming back - but our customers get the most value the first month. Almost all of our customers have renewed their subscriptions after the first month so far.
3. I don't know how well the computer optimizer model performs, but we haven't had a customer take a recommendation and regret it later on. For our enterprise plan, we fine-tune our models to a company's historical usage (rather than throw a standardized model at all of our users).
Happy to share a screencast! Feel free to email me if you'd like.
I do cost optimisations for living and though there are a lot of tools, most of them are niche and doesn't scale well. For generic purpose I tend to use CloudHealth, but still we write a lot of scripts to do some custom managment.
I would be interested in hearing about your experience with cost optimization. My email is [email protected] if you'd like to reach out.
I work at a company that started from cost optimization but now offers a platform to manage the customers cloud operations and i only have 1 suggestion - be very upfront about the permissions/data needed for Usage to do it's job. you don't want to start a demo with a big/enterprise client only to find out your permission needs are way beyond what is allowed in that company for outside services
We're more than just RIs. We also offer Savings Plans, Rightsizing, and Spot Fleet management.
Our permissions include CPU, network, and memory logs. We can scale permissions back on a customer-by-customer basis, though (as we have in the past).
Related:
https://segment.com/blog/the-10m-engineering-problem/
https://i.imgur.com/Lp8B62n.png
I’m not saying their pricing is not confusing, but the account managers and sales engineers I’ve worked with always did a good job navigating us through it - and being honest when something can be achieved a lot cheaper.
Better have a customer optimize their usage, pay less, be happy, and stick with AWS than switching to a different platform.
Full disclosure: I work at AWS. Not on CloudEndure or anything relating to pricing. But come on.