The team at CloudZero has been awesome to work with, and they've helped us to break our cost down in ways that makes it easier to see not what optimizations will get us significant results, in particular lasting benefits. Also, the slack notifications on anomalies are great for quickly getting attention where it is useful. Review collected by and hosted on G2.com.

I don't have any real complaints at present - I'm looking forward to being able to integrate projections with reporting. Review collected by and hosted on G2.com.

easy menus to filter data and get to exactly what you need to see Review collected by and hosted on G2.com.

Frequency of data update, need realtime. Review collected by and hosted on G2.com.

* Setup and connection to your AWS accounts is really smooth and easy and utilizes least-privilege IAM permissions. The team has done a masterful job on this.

* 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. Review collected by and hosted on G2.com.

* The ML features around untagged/unknown resources, while extremely useful, do not seem intuitive. I feel like there needs to be some sort of guide or wizard that can help you go from "I just connected these accounts" to "hey this thing is finding structure I didn't know about" to "hey I've mastered my tagging strategy and know exactly what's going on". Definitions and examples on the 3 divisions (cost group, feature, product) would also be helpful.

* 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. Review collected by and hosted on G2.com.

Cloudzero has a simple UI with good slack / email integration that lets you get relevant data quickly. Anomaly detection is useful and promising (though it can be somewhat noisy), and when combined with weekly reports can help teams notice cost increases and lets development teams manage the costs of their own infrastructure, which can help find software problems in addition to controlling overhead. Product support from Cloudzero is great, and features keep coming. Review collected by and hosted on G2.com.

There are some limits to reporting timeframes, comparing one year to the prior would be useful. There are a number of manual steps for setup/on-boarding that are not in the UI yet (its on the roadmap), so customer support is needed to get set up and make some changes in cost allocation. Review collected by and hosted on G2.com.

The best feature i like about CloudZero is that i get notified about anomalies in cost for all my resources as it detects it. I've tried other tools and have not found anything that provides the feedback this fast. I also really like how we get weekly on our spend behavior and tracking on the spend. Review collected by and hosted on G2.com.

The only dislikes i have with CloudZero is the UI. It took sometime to get used to and to figure out how view what i needed to view. I also think the UI loads a little slow. Review collected by and hosted on G2.com.

The intuitiveness of the drilldowns and visualizations. I don't think in spreadsheets, so that's very useful for me. Review collected by and hosted on G2.com.

I'm an SRE. Getting all of our AWS resources tagged so that CZ categorized them properly took a really long time. Review collected by and hosted on G2.com.

The anomaly detection and alerting puts it way ahead of their competitors. The UI is straightforward and they're willing to take and respond to input from their customers. Review collected by and hosted on G2.com.

No Google Cloud support. UI is sometimes a little slow but still much faster than the competition. Review collected by and hosted on G2.com.

The responsiveness of the CloudZero team Review collected by and hosted on G2.com.

Some pages can be a bit slow at times, but overall this is not really an issue. Review collected by and hosted on G2.com.

Cloud Zero is great because it lets us define the AWS services we use by business function and see the real time spend for each. This gives us a clear picture on cost of delivery and the implications of product deployment.

The support is excellent with thorough onboarding and quick responses once live. Review collected by and hosted on G2.com.

Nothing to dislike. Does what it promises to and more. Review collected by and hosted on G2.com.

I like that I can drill down. We have different cost targets per SKU, and CloudZero let's see how my team is doing at a high level, then drill into various products and further into the technologies that drive our spend. Review collected by and hosted on G2.com.

It seems to require a lot of behind the scenes customization. I'm not entirely sure how to customize the tool (e.g., update AWS tag mappings), though this is likely just a training issue. Review collected by and hosted on G2.com.