Overview

Product video
Operating in the cloud enables developers to make better applications faster, which creates better customer experiences and ultimately drives more revenue for your company. But this speed and agility come at a cost; Businesses are challenged with loss of control over resources and constantly climbing cloud bills.
VMware Tanzu CloudHealth gives businesses complete visibility into their multi-cloud spend, tailored recommendations for optimizing costs and resources, and a dynamic policy engine for governing their environment.
Make Sense of Your Cloud Data: Get visibility into a rich set of data for managing your multi-cloud environment. Analyze your infrastructure by dynamic business groups and benefit from reporting that is fully custom in nature.
Optimize and Control Your Cloud Spend: Improve resource utilization and realize cost savings with tailored recommendations. Drive continuous optimization with governance policies and automated actions that execute changes in your cloud environment.
Enhance Your Cloud Management Practices: Grow your cloud expertise with a proven framework to progress through your cloud management maturity journey.
Highlights
- Cost Visibility: Report multi-cloud spend by unique business grouping and drive adherence to budgets with accurate chargeback/showback.
- Resource Optimization: Rightsize your cloud infrastructure to eliminate wasted spending, and get sophisticated recommendations for purchasing and managing AWS Reserved Instances and AWS Savings Plans.
- Cloud Governance: Implement policies and automation to keep your environment continuously optimized. Terminate unnecessary resources, adhere to budgets, detect anomalies, and reduce business risk.
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Buyer guide

Financing for AWS Marketplace purchases
Pricing
Dimension | Description | Cost/12 months |
|---|---|---|
CH150K | Manage up to $150K of monthly AWS spend. Addl fees above $150K/mo. | $45,000.00 |
CH300K | Manage up to $300K of monthly AWS spend. Addl fees above $300K/mo. | $90,000.00 |
CH500K | Manage up to $500K of monthly AWS spend. Addl fees above $500K/mo. | $150,000.00 |
The following dimensions are not included in the contract terms, which will be charged based on your usage.
Dimension | Cost/unit |
|---|---|
Overage Over Contractual Amount | $0.03 |
Vendor refund policy
Please refer to the seller's website for any refund policy.
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
Software as a Service (SaaS)
SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.
Support
Vendor support
Purchased with onboarding support from our highly-rated customer success teams to help drive value and adoption of CloudHealth and CloudHeath Secure State.
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Standard contract
Customer reviews
Powerful Multi-Cloud FinOps Governance, but Sync Lag and Complex UI Slow You Down
The feature I depend on most is Perspectives. It allows us to dynamically allocate cloud infrastructure spend directly to specific engineering teams, projects, or cost centers. As a result, it removes much of the usual guesswork from internal chargeback reporting and helps create real financial accountability across the organization.
On top of that, the web client interface has grown increasingly complex and harder to navigate over time. Finding advanced reporting configurations, or even adjusting simple notification profiles, can mean hunting through deeply buried sub-menus, which really hurts efficiency during routine auditing tasks.
The most direct benefit to my day-to-day workflow is stronger financial accountability. With custom Perspectives, we can automatically map specific tag data and infrastructure costs directly to the business units, developers, or projects responsible for them. That removes the guesswork from internal chargebacks and helps prevent teams from overspending without realizing it.
Great Cloud Visibility, But the Dashboards Take Time to Learn
High availability has protected revenue, but integration and support still need improvement
What is our primary use case?
VMWare Tanzu CloudHealth is used for our complete e-commerce platform. We predominantly use VMWare Tanzu CloudHealth for high availability systems. We do not use it for cost considerations because we operate as a private cloud where cost remains constant.
How has it helped my organization?
Availability has been one of the biggest improvements. We run it in our private cloud and are able to manage it cost effectively.
For us, daily active users and abandonment rate are critical metrics. If the daily active user numbers are very high, we perform well. The second factor is our abandonment rates. If a customer gets disconnected during a shopping experience, that represents a revenue loss for us. We see that at a very low level, but these are factors where whatever drops happen that are beyond VMWare Tanzu CloudHealth.
What is most valuable?
When you look at it, there is no significant difference between upstream Kubernetes and VMWare Tanzu CloudHealth. However, the support provided is very good when it comes to systems. All the peripheral services that they provide is something we value greatly.
Since we operate in a very regulated industry, security becomes very important for us. I have not seen significant slippage from a security standpoint.
There are two fundamental things. Availability and reporting have become standard. There are two major reasons we are very interested in VMWare Tanzu CloudHealth. First, the observability we can build into VMWare Tanzu CloudHealth allows us to determine what is happening before any service fails, and we are positioned to fix things preventively. We are able to maintain availability in terms that if one of the node clusters goes down, we can quickly respin another cluster so our sessions do not fail and we do not have a revenue loss.
VMWare Tanzu CloudHealth provides value, but we do not look at it very objectively to be precise. What we have done is built something over VMWare Tanzu CloudHealth which does monitoring and everything for us. If you look at VMWare Tanzu CloudHealth, it is useful but not exactly in the terms we are interested in.
What needs improvement?
One of the things we struggle with today is the integration between VMWare and our operating systems. That is where the flaws happen. We are a Red Hat shop. The integration between both needs to be much stronger. Not just Red Hat, but any operating system, they need to get it right. The second thing is that the NSX layer needs to become stronger.
For how long have I used the solution?
I started working with VMWare Tanzu CloudHealth about seven years ago.
What do I think about the stability of the solution?
I would rate stability at nine and a half.
What do I think about the scalability of the solution?
I would rate scalability at nine.
How are customer service and support?
I would give customer service a rating of eight and a half.
Support can always improve. For them, it is a ticket. For us, it is a lifeline. That boundary they need to visualize and provide support to that extent.
How was the initial setup?
VMWare Tanzu CloudHealth is pretty easy to install. Configuration takes a little time, but installation is much easier.
Every business has different logic. Let me give you an example. When we are having very high demand during festive seasons for a few hours, when our e-commerce platform gives special offers, the queues build up very fast. At this moment, VMWare Tanzu CloudHealth needs to be configured so that new sessions are automatically handed to a new set of worker nodes rather than waiting for human intervention. Building that logic is very important. At the same time, when you see sessions getting dropped after the sales, we cannot just kill the infrastructure instantaneously. That requires a set of rules to be built and models that need to be developed so that we are protected and our infrastructure does not fail.
What was our ROI?
We are able to see value. What would eventually happen is we run two versions: one is VMWare Tanzu CloudHealth, and we also run upstream Kubernetes. The moment we are able to stabilize that platform, I do not see a reason we will be paying heavily to VMWare.
What's my experience with pricing, setup cost, and licensing?
Setup costs are very expensive.
Which other solutions did I evaluate?
At this moment, VMWare is running ahead of other competitors, but I see the gap closing very fast.
What other advice do I have?
I used to do both. I used to be a partner of VMWare, selling VMWare, and I also used to consume VMWare.
I currently do not work extensively in that space. I mostly have moved into AI, but we use VMWare Tanzu CloudHealth as a foundation.
I am a consumer of VMWare. I use vRealize and I use VMWare Tanzu CloudHealth. I would give an overall rating of seven to my experience.