What is our primary use case?
Our main use case for CloudVerse AI is cloud cost optimization and FinOps. We use it to track cloud spend across teams, detect anomalies, and figure out where resources are being overprovisioned. We also started using it for AI inference cost tracking recently. A specific, real-world use case would be that we had an issue where one staging Kubernetes cluster was running oversized nodes during weekends when traffic was almost zero. CloudVerse AI flagged the inefficiency, and we adjusted scaling policies. That alone helped cut unnecessary spend without impacting performance.
We also use CloudVerse AI for chargeback reporting between teams. Finance wanted clearer visibility into which engineering teams were driving cloud spend, and CloudVerse AI helped clean up that reporting process.
What is most valuable?
The best features CloudVerse AI offers include anomaly detection, which is probably my favorite feature. The multi-cloud visibility dashboard is also helpful because we do not want separate dashboards for AWS and GCP.
The anomaly detection feature in CloudVerse AI is invaluable because it moves us from reactive troubleshooting to proactive cost management. It uses machine learning to establish a baseline for our typical spend, so it alerts us the moment we see a spike that deviates from that pattern, rather than waiting for the end-of-month bill. Recently, it caught an unoptimized development environment that was left running over a weekend.
CloudVerse AI helps track our cloud expenses effectively.
What needs improvement?
Regarding the impact of CloudVerse AI, finance and engineering teams collaborate better now because everyone is looking at the same data. Earlier, there used to be blame games around cloud costs. In terms of how CloudVerse AI can be improved, the UI can feel a little crowded when you are looking at very large environments. There is a lot of data, and new users may feel overwhelmed initially.
I would appreciate more implementation examples for Kubernetes-heavy environments. The documentation is decent, but more practical deployment examples would help.
For how long have I used the solution?
I have been working in my current field for the last two years.
What do I think about the stability of the solution?
CloudVerse AI is pretty stable overall. We have not had major downtime issues.
What do I think about the scalability of the solution?
CloudVerse AI handles scalability very well for larger environments. We manage multiple accounts and services, and it handled that very well.
How are customer service and support?
My experience with CloudVerse AI's customer support is that they were responsive when we had integration questions. They were not instant, but helpful enough.
I would rate customer support around eight out of ten.
Which solution did I use previously and why did I switch?
Before CloudVerse AI, we mainly used native AWS Cost Explorer plus spreadsheets. That worked at a smaller scale, but it became messy once we added more teams and cloud providers.
How was the initial setup?
Initially, there is a bit of a learning curve, but our core team got used to it, and it was good to go. We got up and running within two weeks. We started with a pilot phase for a single service, which allowed us to build out internal documentation and best practices before a full-scale rollout. After some time, our core team got up and running within those two weeks.
The experience with pricing, setup cost, and licensing felt fairly straightforward, mainly connecting billing accounts and configuring permissions. Pricing felt reasonable compared to building internal tooling.
What about the implementation team?
CloudVerse AI integrates with our existing tech stack quite seamlessly. We have connected it directly into our Jenkins pipeline for automated triggers, and we use the native webhooks to feed metrics into our DataDog dashboard. The API is robust enough that we did not face any significant friction during the initial setup.
What was our ROI?
The return on investment mainly comes from preventing waste before it becomes expensive. It also reduces manual work for both engineering and finance teams.
What's my experience with pricing, setup cost, and licensing?
The experience with pricing, setup cost, and licensing felt fairly straightforward, mainly connecting billing accounts and configuring permissions. Pricing felt reasonable compared to building internal tooling.
Which other solutions did I evaluate?
Before choosing CloudVerse AI, we looked at CloudHealth, AWS native tools, and a few Kubernetes cost tools. CloudVerse AI felt more focused on automation instead of just reporting.
What other advice do I have?
The AI GPU cost optimization feature stands out as well.
The advice I would give to others looking into using CloudVerse AI is to clean up your tagging strategy before implementing it. If your cloud resources are poorly tagged, even good FinOps tools become harder to use.
CloudVerse AI makes the most sense for companies where cloud spend is growing quickly and teams want more automation around cost control. For smaller startups, it might be more than you need.
I would rate this product eight out of ten overall.
