IBM Cloudability

We use IBM Cloudability to provide transparency around our cost spend and how to optimize it.

Good for users who have AWS as their main CSP as all features are available and targeted for these clients. Less features or there is a lag for Azure and other CSP users.

In our organization, We use mete data overlay to clean data and recharge costs per BU (business unit).

If asked, I think I am likely to tell a colleague that, in our experience, with IBM Cloudability it is Simple to see our costs using dimensions

In our organization, we use IBM Cloudability To support cloud cost reporting and optimisation as part of finops.

If asked about IBM Cloudability, I think I am likely to tell a colleague that I think IBM Cloudability is a Great product but may not meet their need based on source or reporting requirements.

In our organization, we use IBM Cloudability as our centralized FinOps and cloud financial management platform. It serves as the "single source of truth" that bridges the gap between our Engineering, Finance, and Leadership teams. Instead of relying on disjointed native tools from AWS, Azure, or Google Cloud, we ingest billing data from all our providers into IBM Cloudability to create a unified operational view.

Well suited for the difficulties and instances especially with the public sector and the public care. Especially in line with our procurement.

Primary use is a visibility tool. We also use it to highlight optimisation opportunities and to share those with teams. Our problems are mainly in addressing the high costs of a DC migration exit, where we have higher than anticipated cloud costs that we want to optimise as soon as possible.

It is good at top down finops. It gives visibility to senior management and enables them to see things without needing AWS access. It gives good summaries. It can be improved by being better at the bottom-up stuff, and getting users to take action rather than just suggesting things that often are lower priority.

We use Cloudability for cost data management for our Azure cloud services. Product provides high visibility of the cloud costs as well we utilize the cost sharing feature for the cost allocation which is a cool feature. Also we use the rightsizing and optimisations features within Cloudability.

IBM Cloudability will be the best tool for Cost transparency and optimisations for cloud costs but when it comes to FinOps for AI, its unable to map easily a specific team the costs as we get the overall token costs but not the API request came from which team or which team used more tokens kind of an information, so would be great , if there is such a feature where the tokens can be mapped to the right teams and instead of sharing across teams, if teams can pay the costs based on the tokens they used would be great.

In our organization, we use IBM Cloudability For FinOps and monitoring AWS Costs

If asked, I think I am likely to tell a colleague that, in my experience, IBM Cloudability Needs to be a bit more flexible

Visibility of cloud costs and identification of optimisation opportunities

Great tool but with lots of caveats, if those are understood and accepted then consumers are less disappointed with their experience

Multi Cloud Visualization of Cloud Costs, drivers behind those costs, trends, spikes and opportunities to optimise.

Great at visulation across Multi Cloud.
Recommendations heavily AWS focused so not as valueable for Azure

I use Cloudability as a FinOps lead or sme within my company, it enables me to pull Azure cost data and build some basic reports. The scope goes from using the product to build monthly cost reports to getting technical change recommendations

it is user friendly and the support teams are very good