IBM Cloudability Reviews & Product Details

What I like most about IBM Cloudability is the visibility it provides into cloud costs and usage across accounts, services, and teams. It makes it easier to identify cost drivers, track spending trends, and connect cloud usage with business or team ownership. The dashboards and reporting are particularly useful for FinOps and management reviews, while the ability to analyze optimization opportunities helps us make more informed decisions about cloud resources and ROI. Review collected by and hosted on G2.com.

The main limitation is that Cloudability can take some time to configure and tailor to your organization, especially around cost allocation, tagging, and account structures. Some reports and dashboards can also require additional customization to match specific internal requirements. For teams managing complex or rapidly changing cloud environments, it would be helpful to have more straightforward configuration and more granular, real-time insights without relying heavily on customization. Review collected by and hosted on G2.com.

What I like best about IBM Cloudability is that it gives me a clearer view of cloud spending. As a network administrator, that helps me connect infrastructure usage with costs and gives me useful information to discuss with other teams. I also appreciate being able to review the cost data in one place instead of piecing it together from different sources. Review collected by and hosted on G2.com.

One thing I’d like to improve is how easy it is for new users to find and understand the information they need. Some reports and settings can take time to learn, so a simpler interface and clearer guidance would make it easier to get started. Review collected by and hosted on G2.com.

Cloud cost visibility

Shows where money is being spent by cloud, account, application, team, project, etc. Review collected by and hosted on G2.com.

Complex setup: Getting accurate cost allocation across accounts, subscriptions, tags, teams, and applications can take significant effort Review collected by and hosted on G2.com.

What I like most is the visibility it provides into cloud spending. It makes it easier to track where the money is going, understand usage patterns, and identify areas where we can optimize costs. The reporting and dashboards are also useful for presenting cost information to different teams. Review collected by and hosted on G2.com.

The learning curve can be a little steep at first, especially when exploring the different reports and cost-management features. It also takes some time to get everything configured and aligned with your organization’s cloud environment. Once set up, though, it becomes easier to work with. Review collected by and hosted on G2.com.

I like the clear and detailed cost visibility that IBM Cloudability provides, making it easy to understand spending across cloud platforms. Its ability to quickly identify cost-saving opportunities, like idle resources, is very effective. I also appreciate the user-friendly dashboard and reports that aid in better decision-making. Budget tracking and forecasting simplify financial planning significantly. Additionally, Cloudability provides useful insights that help improve cost efficiency and brings better financial control over cloud infrastructure. Review collected by and hosted on G2.com.

Some reports can feel complex initially and require time to fully understand. Real-time cost updates are slightly delayed, which impacts immediate decision-making. Customization of dashboard and reports could be more flexible. Integration and setup for multiple cloud platforms like Azure can be a bit time-consuming. Review collected by and hosted on G2.com.

I like the level of granular visibility IBM Cloudability provides into cloud costs. It's quite easy to use, and we can do reporting very easily. I appreciate how instead of looking at a single total bill, we can drill down into costs by team, environment, service, or even specific resources. It's also helpful that we can generate clear, structured reports without much manual effort and share them with respective stakeholders. Together, these features save time, cost, and improve transparency. Review collected by and hosted on G2.com.

Sometimes it becomes complex, especially when we need deeper analysis and advanced reporting. Another challenge we faced during the initial setup and configuration that could be improved. We faced some issues while initial setup, mainly tagging strategy and cost allocation rules took some time. Review collected by and hosted on G2.com.

1. Strong chargeback/showback capabilities: Tag- and account-based allocation makes it easier to attribute spend to applications and teams, improving accountability and accelerating cost conversations.

2. Flexible reporting and drill-down: The ability to pivot by service, account, region, and time—and drill from a high-level view into specific cost drivers—supports both executive summaries and engineer-level troubleshooting. Review collected by and hosted on G2.com.

1. Better Kubernetes (EKS) cost attribution and optimization: More accurate split of node/pod costs (including system/daemonset overhead), idle capacity, and actionable recommendations such as cluster autoscaler tuning, bin-packing opportunities, and identifying over-requested CPU/memory at namespace/workload level.

2. Coverage-aware recommendations (RI/SP + discounts): When suggesting rightsizing or shutdown, automatically factor in Savings Plans/Reserved Instances, tiered pricing, and enterprise discounts so the “net savings” reflects what will actually change on the bill (and flags when a change might strand commitments).

3. Anomaly detection with root-cause hints: Stronger proactive alerts that not only detect spikes, but also suggest likely drivers (new tag/app, new account, specific service/API usage, data transfer path) and link directly to the underlying resources and change window.

4. Automation capability: Enable automation capabilities to implement rightsizing recommendations automatically. Review collected by and hosted on G2.com.

What I like best about IBM Cloudability is the level of visibility and control it provides across multi-cloud environments. It enables clear cost allocation, accurate showback/chargeback, and helps identify optimization opportunities such as rightsizing and eliminating underutilized resources. The insights are actionable and support better financial governance aligned with FinOps practices. Review collected by and hosted on G2.com.

One area for improvement in IBM Cloudability is that it works best when there is a well-defined tagging and governance model in place, which can take some time to mature. Additionally, new users may need a bit of time to fully explore all features and reports. However, once properly configured, the platform provides strong value and insights. Review collected by and hosted on G2.com.

I really appreciate the advanced Kubernetes and container cost allocation features of IBM Cloudability. They help in breaking open the financial black box of Kubernetes clusters, making it easier to know who has spent what amount of money within shared servers. I find it very beneficial that Cloudability combines actual hardware utilization data with cloud billing data, accurately assigning costs down to individual workloads and showing no mystery costs. This is really important for assigning dollar figures and understanding resource usage. It's also a very helpful resource for solving container spending issues and reconciling real-time telemetry with actual cloud bills, giving a bill-accurate dollar figure, which helps immensely with budget accuracy and accountability within the team. Additionally, the setup was really easy, which I appreciate. Review collected by and hosted on G2.com.

So, there's some of the things which I really look into while I'm working with IBM Cloudability. So some of them are, like, the action gap. Cloudability tells you what is wrong, but it rarely says it for you. I think it should be improved with deeper native write-back integration that allows users to execute optimizations directly from the Cloudability interface with a single click. Also, the steep learning curve and initial sort of setup is, like, really hard. We should have better out-of-the-box templates for common organizational structures and smarter AI-driven auto-tagging recommendations to clean up automatically. Also, the governance should be improved by a completely overall unified work frame that allows seamless enterprise-wide role-based access. Review collected by and hosted on G2.com.

I used Clouddability when I was working on an AWS project for my client. Where I need show him the complete costing of - how their infra will look and cost them. There Cloudability helped in presenting the number as well as optimising the resources.

I remember we were able to reduce the cost by 20-25% just following the recommendation. Review collected by and hosted on G2.com.

I like the platform, it's very clean and easy to use and understand. But as some tools CloudZero or AWS Cost Analyser Intelligence dashboard. They are having LLM Capability which is missing for IBM Cloudability. It can improve the customer experience more. Review collected by and hosted on G2.com.