No brainer spend on finops observability
What do you like best about the product?
Over the last twelve months we’ve made use of CloudZero to make huge savings to our cloud spend, make sustainable, meaningful changes to our engineering-spend culture, and to enhance our SaaS unit economics.
CloudZero is by far the best value software I buy here. Over the course of 12 months it’s almost inevitable that we break even with the savings we make against our subscription costs.
Finally, the team at CloudZero are a huge asset to us, it’s like having another team member keeping tabs on things. I have a fortnightly call with Mark Banz who always finds something I’ve missed, and Matt Manger was instrumental in gearing us up for success.
CloudZero is by far the best value software I buy here. Over the course of 12 months it’s almost inevitable that we break even with the savings we make against our subscription costs.
Finally, the team at CloudZero are a huge asset to us, it’s like having another team member keeping tabs on things. I have a fortnightly call with Mark Banz who always finds something I’ve missed, and Matt Manger was instrumental in gearing us up for success.
What do you dislike about the product?
It's a hard one. They replatformed from using quicksight to looker internally which broke a few bookmarks I had. The configuration yaml could be more intuitive but they provide great tooling and usually the AM is doing that anyway
What problems is the product solving and how is that benefiting you?
- Quickly identify accidental spend (bugs) and rectify before the damage becomes too big. At Elliptic we process huge (TODO - how much) volumes of data on a daily basis, and our exposure to risk here is large.
- Identify opportunities for cost saving. To take a recent example, our compute spend has gone up, which we expect, but our compute savings plan is now constantly at 100%, which means we’re fully exposed to paying on demand prices for compute. Time to consider bolstering that savings plan.
- Put spend data directly into the hands of the engineers making real decisions on the ground, “shifting left” on cost culture and meaning we have less bugs, and less opportunities for saving, as we are more deliberate about spend up-front
- Identify opportunities for cost saving. To take a recent example, our compute spend has gone up, which we expect, but our compute savings plan is now constantly at 100%, which means we’re fully exposed to paying on demand prices for compute. Time to consider bolstering that savings plan.
- Put spend data directly into the hands of the engineers making real decisions on the ground, “shifting left” on cost culture and meaning we have less bugs, and less opportunities for saving, as we are more deliberate about spend up-front
There are no comments to display