At this moment, I don't have specific opinions on how Cloudability could be improved or enhanced. I'm using it as a major source of information for my team, but I'm not the right person to suggest enhancements. I believe that automating all manual processes in Cloudability would be beneficial, providing a proactive prescriptive analysis on what needs to be done to lower costs; however, this might also keep us out of business. Enhancements could be made in the user interface and customization, and leveraging GenAI would be an area for improvement in Cloudability.
The first one is, how to help users, especially practitioners, stick to their commitment plan. For example, how can I use Cloudability to help me optimize my selling plan and my residential plan? The second feature I'd like to see is a combination of cost visualization and a sustainability approach. I want to see how much cost I consume in the cloud and what my CO2 footprint is. So, cost visualization and a sustainability approach are the two things I would like. I would improve the integration, or the preparation of the integration, for a complex environment. I think that we usually assume, "Well, this is easy to integrate." In a very complex optimization, this can become very complex. This is where I think we need to be much more prepared, with up-to-date points, to evaluate the complexity of the landing zone or the account to connect. We also need to make sure that we put all the requirements in front of the customer to make sure that we don't fail in the integration.
Technical Lead at a financial services firm with 1,001-5,000 employees
Real User
Top 10
Apr 22, 2024
There are also some limitations with the dashboards and data representation in Cloudability. For example, if you choose Power BI, you have many options for data representation that are not necessarily available in Cloudability.
Principal Consultant at a tech consulting company with 501-1,000 employees
Consultant
Top 5
Mar 15, 2024
I wish there had been a way to temporarily remove certain recommendations from the list for teams that couldn't implement them immediately. Cloudability could have offered more automation functionality and enhanced the cost allocation modeling, although I understand it is there now!
Architect- Cloud/Automation at a consultancy with 1,001-5,000 employees
Real User
Nov 15, 2023
I don't exactly remember the problem with Cloudability. I can say that in my previous company, we could not efficiently make appropriate changes to the tags or resources in Cloudability, so we had to go for another solution, the name of which I can't remember, to help us get the aforementioned functionality. There was an area related to some cost implications that we couldn't work on with Cloudability in my previous company. In general, I feel Cloudability wasn't able to support many resources.
Works at a manufacturing company with 10,001+ employees
Real User
Jan 22, 2021
The only problem with Cloudability we are running is, we have the consultants here who implemented and now their contract is going to end. It already actually ended in December. They are rolling out the knowledge transfer to our teams internally. The way they did it, we are involved now, and it's more like manual work, which we don't like. Cloudability is an external tool, a third-party tool. We would like it to work as a connection to Azure itself and get all the data. Right now, what we're doing is we are manually putting the data in it, which is something which we don't like about Cloudability. When we talked to the consultant himself, he said, "It's due to how our company's way of working and doing the chargeback." It's complicated and we have to do this manual process. That's the only reason, I was looking for other options. There might be a tool that can provide everything without doing manual work. I'm not sure if any features are missing per se as we are just really starting to use the solution and we need to dig in deeper to take in all of its functionality.
Cloud Architect, Oracle ACE, Oracle DBA at Pythian
MSP
Top 20
Jan 14, 2019
More documentation with more use case scenarios would be nice. Also, the dashboard needs to include more graphs per team to show what individual teams are spending in a given time period.
The sizing recommendations should be done in longer than two week windows. They should be looking at a whole year's worth of information because we get spikes, and once you are out of that window, it doesn't account for it. It will say that you can save money, but the reality is that it wasn't estimated with a longer running cycle and time slice. Also, if you were able to have a year long look at it, then it would be able to do some type of a linear regression model along with some predictive analytics, and say, "You spent this much this year, so we estimate with your growth rate that this is where you will need to be next year without any new features. Right now, I don't think that they do good predictions at all. Some of their competitor's do offer these predictions, so this is an area for improvement. Therefore, we would like them to have a linear regression, so we can be predictive for budgets, allocations, and the year's follow ups. We also want to have a longer window of analytics with better certainty that our workload will fit the model, not just in a two week window. With containers, corporate doesn't look at a container level to charge adequately, because things get masked.
Solutions Architect at a financial services firm with 10,001+ employees
Real User
Dec 11, 2018
The API is not well-documented. It is not straightforward and difficult to use. This needs to be improved, as it is very difficult for our developers to develop automation around it. They need to improve their billing data. It seems that sometimes it is not accurate. We have had customers complain that the data they see on the AWS billing dashboard is not reflected (or is very different) from the data that they see in the product. So, there is some discrepancy in the billing reports. I don't know why, but that is one complaint that we see.
Cloud Architect at a financial services firm with 10,001+ employees
Real User
Dec 11, 2018
There is always room for improvement in education and training. We are not that mature in terms of our automation. It could help us identify where we could optimize in terms of build.
Infrastructure Engineer at a computer software company with 11-50 employees
Real User
Dec 11, 2018
Cloudability needs to be simplified a bit. It can be quite difficult and daunting when some of my colleagues login for the first time. It is difficult to get their particular reports or dashboards set up. It would be interesting if they sort of expanded their rightsizing model. It's doing a good job at the moment, but it doesn't necessarily take into account a lot of edge cases. Thus, if they spent more time on the development of the rightsizing, it would be quite useful.
Cloudability is a financial management tool for monitoring and analyzing every cloud expense across any organization. It brings transparency to how and where organizations spend money on cloud resources, giving them the power to reap the most value from cloud usage possible. It aggregates expenditures into accessible and comprehensive reports, helps identify new opportunities for reducing spend and increasing cloud efficiency, offers budget alerts and recommendations via SMS and email,...
It would be beneficial if we could use resource tags to provide more fine-grained visibility.
At this moment, I don't have specific opinions on how Cloudability could be improved or enhanced. I'm using it as a major source of information for my team, but I'm not the right person to suggest enhancements. I believe that automating all manual processes in Cloudability would be beneficial, providing a proactive prescriptive analysis on what needs to be done to lower costs; however, this might also keep us out of business. Enhancements could be made in the user interface and customization, and leveraging GenAI would be an area for improvement in Cloudability.
The first one is, how to help users, especially practitioners, stick to their commitment plan. For example, how can I use Cloudability to help me optimize my selling plan and my residential plan? The second feature I'd like to see is a combination of cost visualization and a sustainability approach. I want to see how much cost I consume in the cloud and what my CO2 footprint is. So, cost visualization and a sustainability approach are the two things I would like. I would improve the integration, or the preparation of the integration, for a complex environment. I think that we usually assume, "Well, this is easy to integrate." In a very complex optimization, this can become very complex. This is where I think we need to be much more prepared, with up-to-date points, to evaluate the complexity of the landing zone or the account to connect. We also need to make sure that we put all the requirements in front of the customer to make sure that we don't fail in the integration.
There are also some limitations with the dashboards and data representation in Cloudability. For example, if you choose Power BI, you have many options for data representation that are not necessarily available in Cloudability.
I wish there had been a way to temporarily remove certain recommendations from the list for teams that couldn't implement them immediately. Cloudability could have offered more automation functionality and enhanced the cost allocation modeling, although I understand it is there now!
Cloudability needs to improve on data collection from cloud sources.
I don't exactly remember the problem with Cloudability. I can say that in my previous company, we could not efficiently make appropriate changes to the tags or resources in Cloudability, so we had to go for another solution, the name of which I can't remember, to help us get the aforementioned functionality. There was an area related to some cost implications that we couldn't work on with Cloudability in my previous company. In general, I feel Cloudability wasn't able to support many resources.
Cloudability needs to focus on more cloud providers.
The only problem with Cloudability we are running is, we have the consultants here who implemented and now their contract is going to end. It already actually ended in December. They are rolling out the knowledge transfer to our teams internally. The way they did it, we are involved now, and it's more like manual work, which we don't like. Cloudability is an external tool, a third-party tool. We would like it to work as a connection to Azure itself and get all the data. Right now, what we're doing is we are manually putting the data in it, which is something which we don't like about Cloudability. When we talked to the consultant himself, he said, "It's due to how our company's way of working and doing the chargeback." It's complicated and we have to do this manual process. That's the only reason, I was looking for other options. There might be a tool that can provide everything without doing manual work. I'm not sure if any features are missing per se as we are just really starting to use the solution and we need to dig in deeper to take in all of its functionality.
More documentation with more use case scenarios would be nice. Also, the dashboard needs to include more graphs per team to show what individual teams are spending in a given time period.
The sizing recommendations should be done in longer than two week windows. They should be looking at a whole year's worth of information because we get spikes, and once you are out of that window, it doesn't account for it. It will say that you can save money, but the reality is that it wasn't estimated with a longer running cycle and time slice. Also, if you were able to have a year long look at it, then it would be able to do some type of a linear regression model along with some predictive analytics, and say, "You spent this much this year, so we estimate with your growth rate that this is where you will need to be next year without any new features. Right now, I don't think that they do good predictions at all. Some of their competitor's do offer these predictions, so this is an area for improvement. Therefore, we would like them to have a linear regression, so we can be predictive for budgets, allocations, and the year's follow ups. We also want to have a longer window of analytics with better certainty that our workload will fit the model, not just in a two week window. With containers, corporate doesn't look at a container level to charge adequately, because things get masked.
The API is not well-documented. It is not straightforward and difficult to use. This needs to be improved, as it is very difficult for our developers to develop automation around it. They need to improve their billing data. It seems that sometimes it is not accurate. We have had customers complain that the data they see on the AWS billing dashboard is not reflected (or is very different) from the data that they see in the product. So, there is some discrepancy in the billing reports. I don't know why, but that is one complaint that we see.
There is always room for improvement in education and training. We are not that mature in terms of our automation. It could help us identify where we could optimize in terms of build.
Cloudability needs to be simplified a bit. It can be quite difficult and daunting when some of my colleagues login for the first time. It is difficult to get their particular reports or dashboards set up. It would be interesting if they sort of expanded their rightsizing model. It's doing a good job at the moment, but it doesn't necessarily take into account a lot of edge cases. Thus, if they spent more time on the development of the rightsizing, it would be quite useful.