External reviews
External reviews are not included in the AWS star rating for the product.
Allows many users to build new dashboards and integrate more data compared to other BI dashboards
What is our primary use case?
What is most valuable?
The best part of CloudZero is the UI for creating dashboards. It allows many users to build new dashboards and integrate more data compared to other BI dashboards. Users can create custom settings for budget forecasting and make their own backend configurations independently without involving CloudZero's team.
What needs improvement?
There is a need for UI improvements. We are in discussions to provide feedback for changes and enhance the dashboard to match our requirements.
For how long have I used the solution?
Our company has been using CloudZero for around four to five months. It is a new product for us.
What do I think about the stability of the solution?
The stability is pretty good if you have some coding experience. However, certain unique keywords need to be studied initially.
How are customer service and support?
The support team is quite good. We are directly connected with the officers since we are making a complete configuration from scratch. Currently, there is no dedicated support team; we connect directly with the engineering team and officers.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Before CloudZero, we were using Cloudability.
How was the initial setup?
The initial setup is straightforward and quite easy for us because we have good support and a finance account manager connecting with us.
What's my experience with pricing, setup cost, and licensing?
I'm not sure about the exact pricing since we have an enterprise segment. It is quite cost-friendly compared to other platforms.
What other advice do I have?
I would not recommend it to small setups. It is preferable for larger enterprises with significant financial needs on cloud platforms.
I'd rate the solution eight out of ten.
CloudZero: Centralized Cost Optimization Platform to review our cloud resource expenditures
* All access privileges given to CloudZero are minimal, so no customer compliance is compromised.
* We can easily integrate our Slack channel into our CloudZero account to get real-time billing alerts.
* Any incident ticket raised regarding technical challenges is addressed immediately by its support team.
* By enabling its resources tagging feature, CloudZero generates periodic reports on the usage of that particular resource group & it helps us track our expenses regularly.
* CloudZero Dimension is an interactive utility inside its platform where we can effectively drill down our cost explorer & detect anomalies.
* It also unifies all our monthly costs in a custom data format which is helpful during presentations with our clients.
* Categorizing our cloud cost allocation is also straightforward, as we can group them based on value, insight or demands.
* Monthly assessment report is beneficial to highlight where we can optimize our cloud expenses & prevent overspending on unused/underused resources in our cloud environments.
I’m really like this application. Works perfect for me.
CloudZero review
Useful solution that enables us to drilldown into AWS expense and also identify increases, etc
CloudZero team is great to work with. Special shout out to MattM
Good product that puts a handle on AWS costs
Finally - Cost as an Operational Metric
* The ability to slice and dice your cost data by so many different dimensions is a killer feature, especially the tag support. It's pretty easy to start to see immediate insights even without a reasonable tagging strategy or naming conventions. With a solid organizational strategy is where you find the biggest benefits - rolling up costs for teams/services/features or attributing cost per customer. CloudZero gives you insight into your cloud spend, but it also indirectly guides you towards building better products where such analysis is possible.
* The ability to see untagged resources in context via extrapolated metadata and related resources is a big help in cleaning up messes like old unmanaged AWS accounts and abandoned experiments.
* The performance and UX of the platform is quite good given the volume of billing data, screens are uncluttered and the information is easy to consume.
* The "resource diff" feature, while rudimentary at present, is a useful data point that can help you figure out why a cost anomaly might have occurred.
* The ability to change "cost views", e.g. real cost, billed cost, is supremely useful for communicating with different audiences. The unmodified AWS bill is terribly difficult to interpret if you're a developer trying to figure out why your service is suddenly costing more.
* Cost anomaly detection has saved my bacon on a number of occasions, especially when doing serverless work. Even with EC2-based systems it's useful - helping me find suddenly-overprovisioned clusters or instances left running.
* Seeing relationships for a resource you're analyzing is very useful when trying to solve a billing mystery. Often, a resource might have an incomprehensible name, but when seen in context with other related resources it becomes far more obvious what it is.
* The monthly trends, slack alerts, and document downloads are all great features. Each one helps you see your spend from a different angle.
* I like very much that CloudZero is branching out from EC2 and serverless into other areas like kubernetes and snowflake. Cost analysis is useful everywhere.
* The focus on unit economics applied to your cloud spend is highly welcome and a trend I'd like to see continue. It's a mark of organizational maturity to perform this analysis; I'd like it to be on the minds of every executive I work with. The fact that CloudZero says "yes, we value this philosophy and will help you with answering these questions" is a big reason why I chose CloudZero, and why I will continue to do so.
* There are no in-app definitions and examples for the different cost options (real cost, billed cost). I know them from talking with their team a lot and the views work fine, but this was not immediately clear. How credits, discounts, and support factors in is also unclear (though I understand this is being addressed)
* I use KMS keys a lot, but given their cryptic names I feel I need more context. Unlike many other resources, keys do not seem to have the context like relationships that I would need to identify what they are supporting. There are occasionally resources like this that are hard to track down.
* AWS is notorious for doing weird things with resource names, like putting instance name in a tag and key aliases in a separate resource. CloudZero could probably benefit from navigating some of these rules and showing the friendliest name possible for a resource. This would be especially helpful for things like large fleets of instances. Right now, the cost explorer contains a mix of easy-to-identify resources with incomprehensible ones and that makes discovery somewhat difficult. However it's still a lot better than using other tools!
* Relationship links are not bidirectional when you are drilled-down into a resource. This leads to potential blind spots where you can only see what's connected to what if you pick the right resource to look at.
* There's only a limited ability to drill into the cost explorer and uncover what's behind a "long tail". In a lot of cases I will see the top 5 taking up 20% of the total cost, with 80% being "other". Really unpacking what "other" contains is a bit more work than it needs to be IMO. There are no "negation" filters, where I could say "show me everything except these things I already know about"
* CloudZero has limited options for integration with your auth provider. Would be nice if it supported GSuite. There are also occasional glitches with signin - nothing a page refresh can't fix, but somewhat annoying.
* Getting a legacy AWS account under control. You all know these accounts - full of dead experiments, overprovisioned untagged instances, mystery buckets. CloudZero helps you inventory and trim the fat.
* Identifying and managing elastic infrastructure, from serverless to auto-scaling groups and everything in between. This has helped us manage multiple environments supporting 20+ engineers and hundreds of customers.