Spot.io Contract

My main use case for CloudCheckr  is checking the Azure  cloud costs of my SaaS service. A specific example of how I use CloudCheckr  to check those Azure  cloud costs with my SaaS service is that my Azure service provider has blocked my access to the Azure billing center. The only way I have to see the costs is via CloudCheckr.

There are certain aspects of the reports or data visualization in CloudCheckr that I find especially useful for this task. CloudCheckr lets you break down costs by tags, resource group, subscriptions, departments, and if you buy through a partner, CloudCheckr reflects all the exact agreed rates, discounts, commitments, and licenses.

In addition to that, CloudCheckr has optimization and identification of inefficiencies. It tells you when a virtual machine is oversized or undersized, it scans whether you have any orphaned resources, if there is any hard disk not assigned to any machine, and if there is any unassigned public IP. CloudCheckr also suggests reservations and savings plans. Unlike other cloud tools, CloudCheckr has an important governance service since it is compatible with other clouds, such as AWS  and Google, and it would provide a unified view of all costs. In my case, I only apply it to Azure.

The most important part is how CloudCheckr positively impacts my organization. It notifies us which machines need downsizing or upsizing, that is, which are oversized or undersized. It tells you if you have any orphaned resources so that you can delete them and eliminate costs, and it suggests certain reservations and savings you can sign up for in order to save costs.

The interface could be improved because it is too dense and overloaded with too many charts and too much information on each screen. Latency is also something important to take into account. The data does not work in real time; rather, it takes between one and three days to show you the usage. In terms of optimization of PaaS, Platform as a Service, CloudCheckr is a bit weak. It works much better on Virtual Machines with all the resources they must have, such as IP, virtual networks, disks, and other components.

I give CloudCheckr a rating of seven because of the interface, because it is too dense, and that is why it would not get a higher score. I also consider the data ingestion, which in the end is a bit slow, as we end up with almost three days' delay in having real-time data. I give it a seven because it has many good features such as suggestions for reservation plans and savings plans.

I have been using CloudCheckr for eight years.

CloudCheckr is very stable in its operation.

CloudCheckr's scalability is good because it adapts quite well. In addition, it allows us to group the different cloud providers within the same platform. If tomorrow I were to contract AWS  or Google Cloud  Services, I could manage them from the same place.

I used to use the Microsoft Azure cost center and AZ CLI, but I did not decide to switch. It was a decision imposed by my partner since they cut off our control center and gave us this tool.

The only metric I can offer as relevant regarding a return on investment with CloudCheckr is that when it suggests that I commit a virtual machine for three years, I get a fifty percent cost saving on that machine.

A specific case where CloudCheckr has helped me reduce expenses or optimize resources is when we have machines that are well sized. CloudCheckr automatically suggests that we make a three-year reservation. By making a three-year reservation, the cost in Azure goes down to fifty percent.

My advice to other people who are considering using CloudCheckr is that you can define or configure your own metrics within the platform. You should ignore the preconfigured panels or dashboards and always look for the information you need, configuring it to your needs, creating panels, and saving them as favorites. I give CloudCheckr an overall rating of seven out of ten.

A quick, specific example of how I use CloudCheckr  in my workflow is that first thing every morning, I check the cost anomaly alerts. CloudCheckr  flags anything that looks out of the ordinary overnight. For instance, if a service that normally costs $50 suddenly spikes to $500, I want to know about that immediately. Those anomaly alerts are really useful because they break down what moved and why across all our accounts. That's usually where I catch things such as someone leaving a test environment running over the weekend or a new service getting deployed without any cost controls.

My main use cases include the security checks I review weekly rather than daily. CloudCheckr runs over 550 best practice checks and flags misconfigurations. I go through those with the security team on a Friday.

In my opinion, the best features CloudCheckr offers include cost anomaly detection, which is probably what I'd miss most if it disappeared tomorrow. It's always on and always watching. I don't have to remember to check things because it tells me when something needs my attention. The advanced grouping is also really powerful. You can slice costs by team, by service, by tag, or whatever you need. That's what makes the monthly chargeback report actually useful rather than just a wall of numbers.

Regarding advanced grouping, we group primarily by tag first. Every resource at Freshworks is supposed to be tagged with a team name and a project name. I'll set up a grouping that says show me all costs grouped by team tag, then within each team break it down by service.

CloudCheckr has positively impacted our organization as we've cut AWS  spend by around 25% over two years. Some of that came from reserved instance recommendations, some from right-sizing, and some from cleaning up resources that should have been deleted long ago. I'd put that at roughly $400,000 in savings over that period.

The impact was measured through CloudCheckr's reports, as it actually has a built-in savings tracking feature which makes this straightforward. Every time it surfaces a recommendation, whether that's a right-sizing suggestion or another optimization, the savings are tracked and attributed.

CloudCheckr could enhance its Azure  support, as it honestly feels an afterthought. We have some workloads on Azure  and the experience compared to AWS  is noticeably worse.

Additionally, there's a lot going on in the interface and it takes a while to figure out where things live.

I've been using CloudCheckr for two years now. I brought it in myself and was the one who pushed for it after I spent an embarrassing amount of time manually trying to figure out why our AWS bill jumped one month.

CloudCheckr is stable and rock solid. Over two years, there has been minimal downtime. Data comes through reliably. The only thing I would flag is that sometimes dashboards load slowly if I'm querying a big date range across many accounts, but that's a minor issue.

There are no issues with CloudCheckr's scalability.

I previously used AWS Cost Explorer , which is fine for basic use cases, but once you're managing multiple accounts with dozens of teams, it just doesn't cut it.

I've seen a return on investment, as the savings are concrete, measurable, and they show up directly in the AWS bill.

My experience with pricing, setup cost, and licensing reflects that it uses custom pricing based on your cloud spend, which is pretty standard for this category. I won't pretend it's cheap, but we've saved multiples of what we pay for it, so the conversation with finance is straightforward.

Before choosing CloudCheckr, I evaluated other options and looked at Apptio Cloudability  and IBM Turbonomic . Cloudability  was decent, but CloudCheckr had better security and compliance checks bundled in, which meant we weren't buying a separate tool for that.

CloudCheckr is deployed in my organization as pure SaaS. You connect it to your AWS accounts through IAM  roles and it begins ingesting data.

The cloud provider I use with CloudCheckr is AWS primarily. That's where about 90% of our infrastructure lives.

I did not purchase CloudCheckr through the AWS Marketplace . We went direct and didn't come through the marketplace.

On a scale of one to ten, I would rate CloudCheckr a seven. The AWS cost management side is probably a nine honestly. However, the Azure limitations drag it down and I think there are a few areas where it hasn't kept pace with how fast the cloud space evolves. It's still the best tool I've used for this job, though it's not perfect. I rate this review a seven overall.

My main use cases for CloudCheckr  include cloud cost visibility and optimization, identifying idle resources, right-sizing, and cost trends. I also use it from a cloud governance perspective, for security and compliance monitoring, and as a managed service provider for reporting to end customers.

One example of how I use CloudCheckr  is through our managed services provider operations where we manage public cloud environments for many end customers. One of the most impressive features is the MSP reporting, which allows us to see how much each customer is spending on the public cloud, obtain a holistic view, generate customer invoicing, create specific dashboards for individual customers based on their use case and requirements, and provide customized chargeback.

Another important aspect of my use case for CloudCheckr is identifying idle resources. We leverage CloudCheckr to identify idle resources, assist with right-sizing and over-provisioned resources, and reduce the cloud cost bill for many of our end customers and our own environment.

The best features CloudCheckr offers include out-of-the-box security and compliance check features that provide over 35 different types of compliance checks at no cost, best practice checks, and alerts. Another valuable feature is the multi-cloud overview, providing unified reporting across AWS  and Azure  while allowing us to create different types of dashboards based on who logs into the platform. Additionally, from an MSP standpoint, there is good ease of deployment, especially the billing and chargeback functionality for a reseller or managed services provider.

CloudCheckr has positively impacted my organization by helping us manage multiple customers and tens of thousands of resources while retaining performance and visibility due to its multi-cloud support. We do not have to worry about jumping from one platform to another, and the better MSP support is beneficial from a billing and chargeback automation standpoint. The integration in compliance helps identify missing areas within our customer environments and improves them. On average, it has helped us provide approximately 15 to 20% savings through right-sizing or idle resource elimination. These are some of the immediate cost savings our customers have experienced after implementing recommendations from the tool.

Areas where CloudCheckr can be improved include simplifying the user experience, as some areas seem complex to my teammates, who felt overwhelmed by the many dashboards available. Another area is drift analysis; there have been complaints about tracking optimization opportunities, such as how to track opportunities identified in January and whether they were resolved in February. We also noticed performance issues with very large data sets, and from an integration standpoint, more integration with third-party tools would be beneficial to the platform.

I have been using CloudCheckr for approximately five to six years.

CloudCheckr is decently stable.

CloudCheckr's scalability is impressive. It scales well for MSPs and large enterprises, allowing for management of hundreds of accounts and tens of thousands of resources while retaining performance and visibility.

I was not satisfied with the customer support from CloudCheckr. I did have some good support from a dedicated account manager or technical account manager. However, additional support took a couple of days and involved back-and-forth communication that did not yield the technical input we needed. The additional support ended up taking longer than expected, with responses that did not meet our need for detailed and technical assistance.

Before CloudCheckr, we were using native cloud consoles and cost tools such as AWS Cost Explorer  and Azure Cost Management . We switched to CloudCheckr because it is a more holistic, centralized cost reporting platform across multiple public cloud providers, offers better MSP support from a billing and chargeback standpoint, and includes substantial automation to generate customer invoicing. The security and compliance feature within the platform was also extremely beneficial.

The setup process is quick and straightforward. In many use cases, integration of cloud accounts is done in under two hours, which is quite good. Initial client creation can take one or two hours with guided setup. Some scenarios, such as creating policies or custom dashboards, take longer, but overall, the setup process is straightforward.

I have seen a return on investment of 100%, with significant cost avoidance and measurable savings within the first few months of deployment. There were fewer resources needed to monitor and manage the customer environment from a costing standpoint. We could implement many end customers, and with the automated customer invoicing feature, we significantly reduced the burden related to Excel sheets and pricing.

Pricing is feature-tiered under the MSP licensing, and I would say the pricing was quite competitive and fair. It was neither inexpensive nor too costly compared to competition, yet it provides good value.

The features of CloudCheckr I have not mentioned yet include the cost-saving recommendations, which are quite actionable.

For a specific example of a customer where CloudCheckr's recommendations led to 15 to 20% savings, we recently onboarded a customer from a managed services standpoint who had multiple accounts in different cloud providers, AWS  and Azure , accumulated over the years due to various acquisitions. There was initially no oversight of who was provisioning resources, what it cost each business unit, or where resources were deployed. Once we leveraged CloudCheckr and connected it to those different customer environments, we created a single dashboard to obtain a holistic view of their spending across AWS and Azure, allowing our team to save time and effort by reducing the need to go through each individual account. For the end customer, we identified idle and unused resources, categorizing those not used for the last 60 days. We identified all those resources, including public IPs, virtual machines, and storage. We also found many over-provisioned resources being utilized at only 30 to 40%. By leveraging the right-sizing recommendation, we successfully right-sized those resources, and the customer ended up saving roughly 20 to 25% using the platform.

My advice for others looking into using CloudCheckr includes configuring tags and the chargeback mechanism early during onboarding to the platform, creating automated alerts for budget increases, aligning with security posture checks and compliance frameworks, and ensuring custom dashboards are created for different stakeholders accessing the platform. I would rate CloudCheckr a seven on a scale of one to ten.