Cast AI Reviews & Product Details

The automation is genuinely impressive - once Cast AI is connected to our clusters, it handles the scaling decisions that used to eat up hours of our engineers' time each week. The cost savings kicked in pretty quickly after setup, and the visibility into where our cloud spend is going has been really useful. We had a multi-cluster setup and Cast AI handled it better than I expected. The recommendations are solid and the UI makes it easy to see what's happening without digging through logs. Review collected by and hosted on G2.com.

The initial setup and onboarding documentation could be a bit clearer - there were a few gotchas around IAM permissions that took us longer to figure out than it should have. The alerting options feel a bit limited compared to what we're used to with other tools. Nothing that's been a dealbreaker, but there's room to improve on those fronts. Review collected by and hosted on G2.com.

The automated rebalancing and Spot Instance management are game-changers. Unlike other FinOps tools that just give you a list of suggestions to fix manually, CAST AI actually executes the changes in real-time. The Autoscaler is incredibly aggressive (in a good way) at bin-packing pods, which allowed us to shrink our cluster footprint significantly without any downtime. Also, their Spot fallback mechanism gives us the confidence to run production workloads on Spot instances because we know it will move them to On-Demand instantly if capacity drops. Review collected by and hosted on G2.com.

While the onboarding is fast, there is a slight learning curve when it comes to fine-tuning policies for very complex stateful workloads. I also noticed that the Workload and Node autoscalers sometimes feel like they are operating on two different planes—it would be great to see even tighter coordination between the two so that resource requests and node provisioning are perfectly synced 100% of the time. Lastly, the pricing can feel a bit steep for very small, static clusters where there isn't much to optimize. Review collected by and hosted on G2.com.

What stood out to me most was the automation. Once it was set up, CastAI continuously analyzed our workloads and adjusted resources in real time. We saw noticeable reductions in wasted compute, especially around underutilized nodes. The platform’s ability to automatically leverage Spot instances without compromising stability was a big win for us. It handled the complexity in the background, which gave our team more time to focus on product work instead of infrastructure tuning.

The visibility into costs has also been valuable. Being able to break down spending by cluster and workload helped us understand exactly where our cloud budget was going. That transparency made it much easier to have productive conversations internally about optimization and accountability. Review collected by and hosted on G2.com.

I seldom observed wrongful recommendations applied to some workloads where CastAI applied resources higher than the maximum available capacity on our EKS cluster which lead to some services staying in pending state without any way to control it. Review collected by and hosted on G2.com.

I’m genuinely impressed with the way CAST AI presents its user interface. The layout feels clean, intuitive, and thoughtfully designed, which makes it incredibly easy to navigate and understand without needing extensive documentation or onboarding. This intuitive experience allows me to make data‑driven decisions with confidence and quickly follow through with corrective actions whenever necessary.

Since adopting CAST AI, I’ve seen an almost 80% reduction in the manual effort previously required for continuous monitoring. Tasks that once demanded constant attention have now become streamlined and largely automated.

One feature I especially appreciate is the clear visibility into cost analytics. CAST AI distinctly highlights the actual cost versus the optimized effective cost, making it simple to understand the financial impact of its automation. The platform also provides transparent insights into savings achieved through right‑sizing and resource allocation based on real usage patterns. This level of clarity significantly helps me with planning, forecasting, and overall execution.

Additionally, the initial setup process was remarkably quick and hassle‑free, allowing me to start leveraging its capabilities almost immediately. Review collected by and hosted on G2.com.

I’ve noticed that during the initial pod initialization, CAST AI doesn’t really catch up with the metrics, Following are details

Key Observations About Pod Initialization Metrics in CAST AI

Initial pod‑startup metrics are not fully captured

During the very first phase of pod initialization, CAST AI appears to miss short‑lived spikes in resource demand. This leads to incomplete or inaccurate metric collection for that specific window.

Short bursts of CPU requirements go unreported

If a pod briefly requires a full 1 core at startup—even for a fraction of a second—CAST AI currently does not record this spike. As a result, the platform overlooks an important requirement needed for successful initialization.

Reported CPU utilization does not reflect real startup needs

When the pod’s average CPU usage settles around, say, 300 millicores, CAST AI reports only that average. It does not reflect that the pod initially needed 1 full core to boot successfully.

This leads to misleading CPU insights

Since CAST AI displays only the averaged metrics, it suggests that the pod’s CPU requirement is consistently low. However, operationally the pod still cannot start without that initial 1‑core burst.

Practical implication: startup failures despite “adequate” reported CPU

Even though the dashboard may show that 300 millicores is sufficient, the absence of a guaranteed 1‑core burst at initialization can cause pod startup delays or failures—none of which the current reporting highlights.

Overall effect on capacity planning and rightsizing

This gap in visibility can cause confusion during rightsizing exercises, as CAST AI does not reflect the full picture. Teams might allocate too little CPU based on averaged metrics, unaware of the critical startup requirement. Review collected by and hosted on G2.com.

The centralization of Kubernetes metrics in an intuitive user interface, along with the configuration of nodes and workload autoscalers, facilitates resource optimization. Review collected by and hosted on G2.com.

What complicates the use of the tool for us a bit is the installation through Helm, since we deploy it with Terraform using manifests. In that context, some components, such as the evictor, cause us issues when managing them without the user interface. Review collected by and hosted on G2.com.

The best thing and the best feature of Cast AI is beautiful mapping of

1. nodes scaling

2. horizontal scaling

3. provides read only view so LLMs can learn and optimise the strategy instead of just implementing directly to our environment and learns itself 0 downtime strategies.

4. Their customer support is too good, For P0 issues Chandani from castAI is available on prompt basis

5. We can implement castAI just by providing the enough IAM permissions, and easily installing castAI into our EKS environment within 30 mins.

6. Our infra cost is reduced to 30% by using castAI for just like 40-50 days. Review collected by and hosted on G2.com.

There is nothing to dislike, but there can be one improvement

We can have correct mapping if we are using nginx-ingress, as we have to map target groups of nginx ingress in castAI console. Review collected by and hosted on G2.com.

What I like best about Cast AI is how effectively it combines cost optimization with operational simplicity. It continuously analyzes our Kubernetes workloads and automatically right-sizes nodes, scales clusters, and leverages spot instances without requiring constant manual tuning from our DevOps team. The visibility into resource utilization and savings is clear and actionable, which makes it easier to justify infrastructure decisions internally. Beyond the cost savings, the real value is the time saved and the confidence that the cluster is always running in an optimized state without daily intervention. Review collected by and hosted on G2.com.

One downside is that some of the more advanced configuration and optimization features require a deeper understanding of Kubernetes and cloud infrastructure to fully leverage. While the basics are easy to set up, fine tuning policies and understanding the impact of certain automation decisions can take time. In addition, more granular cost reporting and forecasting capabilities would be helpful for organizations that need detailed financial breakdowns across teams or projects. Review collected by and hosted on G2.com.

Its ability to automatically optimize Kubernetes costs without sacrificing performance stands out. The automation around workload rightsizing and intelligent autoscaling saves a significant amount of time and greatly reduces manual effort. I also appreciate the clear visibility into cluster performance and cost metrics, which makes it easier to make informed decisions and stay on top of usage. Overall, the platform is user-friendly, integrates smoothly with existing cloud environments, and delivers measurable cost savings quickly. setup was guided by the support team and we are frequenlty using this to create nodegroups etc Review collected by and hosted on G2.com.

One downside of Cast AI is that the initial setup and fine-tuning can take some time, particularly in more complex Kubernetes environments. Although the automation is powerful, it can take a while to fully understand and configure all of the optimization features, and there may be a learning curve for teams that are new to Kubernetes cost management. In addition, having deeper customization options and more detailed reporting in certain areas would make the platform even stronger overall. Review collected by and hosted on G2.com.

It helps us optimize our K8 clusters and reduce costs. The UI is great and clearly shows how much we’ve saved so far, as well as what can still be improved within our cluster. The workload optimizer is also a really useful feature. Review collected by and hosted on G2.com.

It’s hard to find logs for certain things, and it’s also hard to understand why something isn’t working when an issue comes up. For example, recently my scheduled rebalancing wasn’t working correctly, and even the support team couldn’t figure out why at first. After a lot of digging, we found it was because one machine was stuck in a weird state after a previous rebalancing. It wasn’t easy to track down what caused this, and it seemed like support wasn’t able to identify the issue right away either. Review collected by and hosted on G2.com.

I use CAST AI to optimize Kubernetes infrastructure cost and resource utilization across both production and non-production environments. CAST AI helps us automate node scaling, workload right-sizing, and instance type selection, which is a huge help. I also appreciate the dashboard view, which makes it easy to see all namespace workloads and identify usage patterns to reduce resources. CAST AI effectively solves challenges related to Kubernetes cost management, scalability, and operations across multiple cloud provider clusters. The cost management is fantastic, as CAST AI chooses the best instance types based on workloads and automatically provisions the right size of nodes, CPUs, and memory, which saves costs. The initial setup was quite good, and it helped us learn more about cost optimization. Overall, I would definitely recommend CAST AI. Review collected by and hosted on G2.com.

I would say CAST AI can improve by automatically picking the pod usage and changing the resources without any downtime of production workloads. Basically, right sizing is shown in the dashboard but we have to do it manually. It would be better if it could solve this automatically to spin up new pods and reduce the workloads. Review collected by and hosted on G2.com.