What is your primary use case for Cloudability?

My main use case for Apptio Cloudability is performing ad-hoc reports and monthly and quarterly reporting in Apptio BI, which help us to do number presentations with our large customers in our company. I have some experience building dashboards. A specific example of a report I built using Apptio Cloudability is in Apptio BI, where dashboard functionality allows users to create dashboards that show monthly and month-to-date numbers based on usage and services, as well as how much savings we get from savings plans and RIs. Recently, I also built a report to look at one service in a certain region for a customer, and that service was some kind of compute service. Regarding my use case and experience building dashboards and reports in Apptio Cloudability, it provides standard AWS features. I quite like it for building dashboards and doing ad-hoc reports. It is amazing to be able to track AWS or whatever cloud spending down to the penny and know where it is going. In many ways, we underutilize it at Southwest because we do not have unit economics set up yet, so it can help with those types of detailed reporting. Apptio Cloudability is a very powerful tool and very impressive.

My main use case for Apptio Cloudability is optimization, cloud cost management, and container management. I have a cloud environment that hosts containers, and I use information around the CPU requests and limits and memory requests and limits to size my infrastructure correctly. Cloud optimization is very key for me, and I am using that to embed into my cloud cost optimization recommendations process which I send out to my engineers, and I track against the implementation of those recommendations.

My main use case for Apptio Cloudability was for a project called Project Apollo that had a target of saving a million Australian dollars by April 2026. It had a lot to do with contract renewals, and we needed to save a certain amount of money for the budget so that we could get a better negotiation price on our contract renewals. We were able to achieve this through the use of detection of rogue spending through Apptio Cloudability. There was a lot of rogue spending we detected through Apptio Cloudability. We found out there were multiple Direct Connects that we were using and we did not need as many. We were able to find those through Apptio Cloudability and rationalize those Direct Connects, which saved us a lot of money. We also found wasted, very old EBS snapshots that were costing us a lot of money. They could be anywhere between seven to ten years old and had never been cleaned up before. They were costing us a lot of money. Additionally, we identified opportunities for EC2 right-sizing, RDS right-sizing, and OpenShift right-sizing. Right-sizing across all the different platforms was something we were able to utilize and detect through Apptio Cloudability to find out what the cost efficiencies were and the savings going forward. These were the harder projects to complete and take to fruition because there was a lot of communication needed with application owners. There was also a lot of agreement needed on timings and windows when these things could be done. Nonetheless, we were able to keep pushing the project, keep on top of it, and continue following up. The hardest part was keeping the communications open and ensuring that the people involved understood why we were doing what we were doing and why it needed to be done. If it ain't broke, do not fix it is very much a mantra across industry and life in general. Many of these production loads were not broken, but they were costing us a fortune. Communication was absolutely one of the biggest things here.

I use Cloudability to track costs across a multi-cloud infrastructure estate, including Google Cloud, AWS Cloud, and Microsoft Azure. Everything from reports and dashboards to anomaly alerts and right-sizing is managed through Cloudability. I regularly use the reporting feature in Cloudability. If I'm trying to figure out how much cost is attributed to a specific account, I'd create a report based on the account name. That allows for historical tracking of how the costs have maybe increased or decreased over time, and that's quite useful. In addition to my main use case, I use the dashboards feature regularly as well. If I want to have a higher view level of what cloud costs are within the estate, I would use the dashboards because I can look at multiple cloud accounts at once.

My main use case for Cloudability is cost visibility. For cost visibility, I look at the utilization of various resources across different AWS accounts, get recommendations for cost optimization, and utilize and view the graphs and trends for cost utilization.

I usually work with Cloudability for cost optimization, cost analysis, reporting, and resource and cost management, mostly focusing on the FinOps side.

Usually, it is used by large companies with a high amount of cloud spend. Something like more than 5 million dollars a year. And, usually, we face multi-cloud challenges.

We had a multi-cloud environment using both AWS and Azure to keep track of costs in one place. We used Cloudability to understand and manage the spending across both clouds effectively.

We used Cloudability for cloud cost and usage management. It normalized data and gave us custom cost metrics that enhanced the dashboards and reports to answer the real questions we needed to answer to run the FinOps practice. The software also facilitated yearly forecasting by allowing us to analyze historical data trends spanning six years. We could model future business projections to refine forecasts and integrate budgets with actuals directly into Cloudability for ten high-spending teams.

We use the product to see the cloud costs. It helps our business, financial, and technology teams.

In my previous company, we used Cloudability for a lot of purposes, including reports related to cloud costs and reports based on resources. The solution was also useful for driving through the management groups to find what the cost is for each account, so the main use of Cloudability was related to costs and tagging purposes. In my previous company, we used to check if the resources were tagged so that they would appear in Cloudability, which helped us with the creation of the cost reports accurately.

We use the product to get a detailed level of transparency on the cloud strengths.

We are just using it for Azure and Google, as we might have different Cloud vendors and what we're trying to do here is right-sizing so that it can send us reports for all the subscriptions, for example, in Azure. We'd like it to tag the information and all the costs related to the information. That way, we can do the right sizing report from there, and we can rate it.

Our client wanted a transparent and visible view of financials in the cloud and that's why we opted for Cloudability Optimization Platform. We are using the solution on AWS.

We mostly use it to see stack utilization. Corporate uses it for its break down of teams, who is being charged what, but there are a lot of holes in this. For the most part, it is used to determine if the machine is using the rightsizing, etc.

* Cost optimization * Billing reports

The primary use is for billing management software. It not only provides detailed billing of everything, but it also provides insight into how to optimize our infrastructure. It tells us where the overruns are and where there are places for optimization.

Cloudability helps us with analyzing a lot of our AWS costs, then seeing those different costs with types of business costs. This helps us get a full understanding of where we are spending our money. It also helps us with reserved instances along with recommendations on them.