Overall, I would rate the solution an eight out of ten because now I expect to be able to have maybe something that is less expensive or reduce the number of features to benefit the main features and maybe pay later for all this.
Technical Lead at a financial services firm with 1,001-5,000 employees
Real User
Top 20
2024-04-22T15:51:00Z
Apr 22, 2024
Some dashboards are directly reported to management and cover all the applications we have on the cloud. Each application should have specific dashboards focusing on spending and resource utilization, and most should have these features. For example, you can compare spending in a single cloud environment using Microsoft's Azure portal insights. From the tenant portal, you get detailed information that can be fed into Power BI to create custom dashboards. However, if you use a multi-cloud environment with AWS, Google Cloud, and Azure, it's more challenging to consolidate these insights. Cloudability is beneficial as it provides a unified view of spending and resource utilization across the entire organization, helping management track expenditures. Cloudability is particularly useful for large organizations wanting to understand where they are spending more and make decisions about continuing with specific cloud providers. However, they need to consider the cost of Cloudability and whether they already have an in-house data platform. If they do, building similar capabilities internally might be more cost-effective. Cloudability also provides insights about rightsizing resources, which is valuable at the organization or department level. However, it doesn't predict future scaling of data volumes; that knowledge lies with the application owners. If the data volumes are expected to remain stable, Cloudability's recommendations can be beneficial. CloudOps with Cloudability is relatively straightforward and has an easy-to-use interface. It is more user-friendly than the Azure portal, making it easier to find relevant data. Users need to understand the cloud-specific terms and attributes to apply the correct filters. Cloudability remains valuable, especially for teams or organizations not wanting to delve deeply into data engineering. It's an organization's go-to product, provided they have the budget. On the other hand, organizations committed to a single cloud setup with established data platforms and engineering capabilities might prefer building in-house solutions rather than using Cloudability, which might not offer all the customized features they need. Overall, I rate the solution a seven out of ten.
Principal Consultant at a tech consulting company with 501-1,000 employees
Consultant
Top 10
2024-03-15T13:58:00Z
Mar 15, 2024
I have recommended Cloudability to others, as it played a significant role in my success as a FinOps practitioner. Although Cloudability may be one of the higher-priced options, it's worth the investment. Overall, I would rate it a nine out of ten. It would get a ten if it would have let me choose my graph colors ;-)
There are multiple features coming up in the dashboards provided by Azure for cost analysis. People can also consider other options like CloudHealth and CloudZero. I think that some features related to security are missing in Cloudability. I rate the overall tool an eight out of ten.
Works at a manufacturing company with 10,001+ employees
Real User
2021-01-22T22:06:07Z
Jan 22, 2021
We're just customers. We aren't partners of Cloudability. We're using the latest version of the solution, as far as I know. We're still in the initial phase, however, we're finding, overall that it works well. If you're looking into multi-cloud functionality, definitely go for it. If you're sticking with the one cloud, for example, if your organization is just using Azure, it may be better to use a tool dedicated to that. Cloudability would also work fine in that instance, however. If your organization isn't too complex, you may be able to piece together everything with what's there. I would rate the solution at a six out of ten. The reason is mainly due to my own limited knowledge or exposure to the product so far. As I said, the process is manual. I don't have a tool for it. It is maybe how we've addressed it so far. Once we dig deep into it, we'll come to know a bit more about if maybe Cloudability can grab the data directly from Azure. We need not move beyond this manual processing. Maybe the reason is due to the complexity of our own organization. Once that is addressed, the tool is going to work really well.
The product is probably not valuable until you are over a certain threshold in compute power. While I don't know what the actual cost is, if you were to say, "We could save you X amount and that would offset the cost of their product, then it is probably starting to be in the realm of being worth it." We only use the AWS version.
It is a standalone product, but it does integrate for identity with our other directory. This is pretty straightforward, and it works. AWS doesn't have a version of this product. Cloudability is a billing and reporting tool. AWS does have capability to provide billing data, but the report and analytics portion of it is not provided by AWS. AWS just provides the data and cloud ability to ingest the data and do the reports. If you are heavy on automation, then this might not be a good product because the API is not very well-documented. If you need accuracy in your data at the moment, there is some discrepancy in the billing data. So, you should factor that into in your decision.
I would recommend Cloudability to other people. If you are looking for a seamless, simple to use, and in-depth, cloud, building analysis tooll, Cloudablity serves all these purposes. It manages all my needs. We are using the AWS SaaS version.
Infrastructure Engineer at a computer software company with 11-50 employees
Real User
2018-12-11T08:30:00Z
Dec 11, 2018
The product is quite interesting. Where we receive a benefit from Cloudability, we now see it more with the AWS offering. They have AWS Cost Explorer, along with the features we like having comprehensive support through AWS. Therefore, Cloudability needs to stay one step ahead of the curve. However, there are a few different parts of Cloudability that we are not fully utilizing yet which we will be utilizing in the future. This means that we are picking up a few more of their features and user adoption in our company will be much greater. Define what you really want out of your AWS Cost Explorer, then evaluate all the different options. So, evaluate AWS Cost Explorer first, then determine if you want to use Cloudability. We use the AWS version of the product. I'm quite happy with most of the product.
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,...
Overall, I would rate the solution an eight out of ten because now I expect to be able to have maybe something that is less expensive or reduce the number of features to benefit the main features and maybe pay later for all this.
Some dashboards are directly reported to management and cover all the applications we have on the cloud. Each application should have specific dashboards focusing on spending and resource utilization, and most should have these features. For example, you can compare spending in a single cloud environment using Microsoft's Azure portal insights. From the tenant portal, you get detailed information that can be fed into Power BI to create custom dashboards. However, if you use a multi-cloud environment with AWS, Google Cloud, and Azure, it's more challenging to consolidate these insights. Cloudability is beneficial as it provides a unified view of spending and resource utilization across the entire organization, helping management track expenditures. Cloudability is particularly useful for large organizations wanting to understand where they are spending more and make decisions about continuing with specific cloud providers. However, they need to consider the cost of Cloudability and whether they already have an in-house data platform. If they do, building similar capabilities internally might be more cost-effective. Cloudability also provides insights about rightsizing resources, which is valuable at the organization or department level. However, it doesn't predict future scaling of data volumes; that knowledge lies with the application owners. If the data volumes are expected to remain stable, Cloudability's recommendations can be beneficial. CloudOps with Cloudability is relatively straightforward and has an easy-to-use interface. It is more user-friendly than the Azure portal, making it easier to find relevant data. Users need to understand the cloud-specific terms and attributes to apply the correct filters. Cloudability remains valuable, especially for teams or organizations not wanting to delve deeply into data engineering. It's an organization's go-to product, provided they have the budget. On the other hand, organizations committed to a single cloud setup with established data platforms and engineering capabilities might prefer building in-house solutions rather than using Cloudability, which might not offer all the customized features they need. Overall, I rate the solution a seven out of ten.
I have recommended Cloudability to others, as it played a significant role in my success as a FinOps practitioner. Although Cloudability may be one of the higher-priced options, it's worth the investment. Overall, I would rate it a nine out of ten. It would get a ten if it would have let me choose my graph colors ;-)
You need to maintain contact with the company so they can guide you on using the product. I rate it a nine out of ten.
There are multiple features coming up in the dashboards provided by Azure for cost analysis. People can also consider other options like CloudHealth and CloudZero. I think that some features related to security are missing in Cloudability. I rate the overall tool an eight out of ten.
I rate the product a seven out of ten. It gives you granular details.
We're just customers. We aren't partners of Cloudability. We're using the latest version of the solution, as far as I know. We're still in the initial phase, however, we're finding, overall that it works well. If you're looking into multi-cloud functionality, definitely go for it. If you're sticking with the one cloud, for example, if your organization is just using Azure, it may be better to use a tool dedicated to that. Cloudability would also work fine in that instance, however. If your organization isn't too complex, you may be able to piece together everything with what's there. I would rate the solution at a six out of ten. The reason is mainly due to my own limited knowledge or exposure to the product so far. As I said, the process is manual. I don't have a tool for it. It is maybe how we've addressed it so far. Once we dig deep into it, we'll come to know a bit more about if maybe Cloudability can grab the data directly from Azure. We need not move beyond this manual processing. Maybe the reason is due to the complexity of our own organization. Once that is addressed, the tool is going to work really well.
I rate it a nine out of ten, as it provides a holistic view of financials and is an enabling technology.
The product is probably not valuable until you are over a certain threshold in compute power. While I don't know what the actual cost is, if you were to say, "We could save you X amount and that would offset the cost of their product, then it is probably starting to be in the realm of being worth it." We only use the AWS version.
It is a standalone product, but it does integrate for identity with our other directory. This is pretty straightforward, and it works. AWS doesn't have a version of this product. Cloudability is a billing and reporting tool. AWS does have capability to provide billing data, but the report and analytics portion of it is not provided by AWS. AWS just provides the data and cloud ability to ingest the data and do the reports. If you are heavy on automation, then this might not be a good product because the API is not very well-documented. If you need accuracy in your data at the moment, there is some discrepancy in the billing data. So, you should factor that into in your decision.
I would recommend Cloudability to other people. If you are looking for a seamless, simple to use, and in-depth, cloud, building analysis tooll, Cloudablity serves all these purposes. It manages all my needs. We are using the AWS SaaS version.
The product is quite interesting. Where we receive a benefit from Cloudability, we now see it more with the AWS offering. They have AWS Cost Explorer, along with the features we like having comprehensive support through AWS. Therefore, Cloudability needs to stay one step ahead of the curve. However, there are a few different parts of Cloudability that we are not fully utilizing yet which we will be utilizing in the future. This means that we are picking up a few more of their features and user adoption in our company will be much greater. Define what you really want out of your AWS Cost Explorer, then evaluate all the different options. So, evaluate AWS Cost Explorer first, then determine if you want to use Cloudability. We use the AWS version of the product. I'm quite happy with most of the product.