The solution is highly-scalable. It can work with large datasets. I rate it a nine out of ten. We have five users for the solution in our organization.

I rate Cloudability's scalability a seven out of ten. 

The solution is still relatively new to us, and, as we've only really started to implement it, we have not tried to scale it just yet. Therefore, I can't speak to its scalability just yet.

There might be 15 to 20 users so far right now. However, this number will increase. We are still in the initial phase. It's only the direct people, our admins, who are trying to make this work or try to make sense of it. Then we can lend it to the users. However, the access control is easy. You can give out admin access or user access to the reports.

The scalability is good. 

Scalability was excellent, and I never experienced issues.

I rate the tool's scalability an eight out of ten. 

Scalability-wise, I rate the solution a seven and a half out of ten.

There are many features that Cloudability does not support. If I look at a tool like Azure Resource Health, which I know offers a dashboard for cost analysis since I currently work with Azure, I see that it offers a wide range of features. The area related to security is not supported in Cloudability, but I am not sure if it was later deployed or not. Another problem with Cloudability stemmed from the fact that in my previous company, we had to deploy multiple things or features in the product by ourselves. There should be some room in Cloudability for the support of resources, indicating how many resource types it supports. Another area of concern in Cloudability is related to its ability to directly trigger action since its users couldn't directly trigger actions from Cloudability, though I am unsure if the latest version of the tool has that feature.

Only eight to ten people in my previous organization were using Cloudability, and later, we tried to get everyone in the company to use it. When we saw that we had to share the product's links and passwords with multiple users in my previous company, we decided that only the cloud governance team and managers should use Cloudability.

The scalability is average. It is not terrible, but it is not great. Sometimes things take a while to load, but any analytics that haven't ran in a while need to reboot all their stuff.

We are very big. I don't even know how many EC2 types that we have. As an example, they want us to save $12 million USD a year on budget, and I don't even know what that computes to in compute power.

We have hundreds upon hundreds of accounts, and it is able to handle that. 

We don't have any performance issues. Its scalability is fine. I don't have an issue with it.

It is a SaaS product. So, we don't have any issues with how it can scale.

We are in three different regions. We have two environments: sound and production. We have 120,000 monthly active users.

We're using a SaaS environment. The SaaS environment has an SLA which automatically scales up depending on our needs, so we don't have to worry about scalability.

As it's in the cloud, scalability is not an issue at all. The environment consists of dozens of VMs.