CloudHealth Acquisition and Who Owns VMware Tanzu CloudHealth Now, With the Closest CloudHealth Alternatives

Broadcom does not publish a price for CloudHealth, and we are not going to repeat one. Figures circulate in comparison posts and marketplace listings, they disagree with each other by large multiples, and several originate from vendors selling against it. An invented number is worse than no number because it anchors a negotiation in the wrong place.

What can be stated accurately is the shape of the commercial model. CloudHealth has historically been sold as an annual enterprise agreement scoped to the volume of cloud spend under management, frequently through partners and managed service providers rather than direct, with the partner adding its own service margin. That last detail explains most of the price variance you will read about: two customers quoting wildly different numbers may both be accurate, because one bought direct and one bought through an MSP with a managed FinOps service attached.

The practical questions to put to the quote are therefore about scaling and term, not about the headline. What exactly counts as spend under management, does committed spend count at list or at your negotiated rate, what happens to the fee when the estate grows 40 percent, and is there a floor. A platform priced on managed spend gets more expensive precisely when your cloud bill is already the problem, which is the wrong direction for a cost tool to move.

These three come up together constantly because they are genuine peers: all three are established enterprise cloud financial management platforms, all three cover AWS, Azure, and Google Cloud, and all three do grouping, chargeback, budgets, commitment reporting, and rightsizing recommendations. Feature comparison at the datasheet level will not separate them. Price does, and two of the three publish more than they are given credit for: both CloudHealth and Cloudability list annual contract prices on AWS Marketplace, while Flexera One genuinely publishes nothing.

What does separate them is corporate context, and that is a legitimate buying criterion for a platform you intend to run for five years. Cloudability belongs to IBM through the Apptio acquisition, completed 10 August 2023, and its strategic direction is tied to ApptioOne and the wider technology business management story, which is an advantage if you want cloud cost inside a full IT financial model and overhead if you do not. Flexera One comes from a software asset management heritage and is the strongest of the three when on-premises licensing and cloud spend have to be answered for by the same team. CloudHealth under Broadcom is the one whose roadmap is hardest to read from outside.

Our honest position: if you need enterprise governance at real scale, with perspectives, policy engines, and partner-delivered managed FinOps, all three are credible and you should test them on your own billing data rather than on a feature grid. If what you actually need is one accurate number for cloud and SaaS spend, attributed to teams, without an implementation project, none of the three is a good fit and the cost of finding that out through a procurement cycle is high.

Almost every comparison article in this category states that CloudHealth pricing is available on request. That is not true for the AWS-scoped contracts. The VMware Tanzu CloudHealth listing on AWS Marketplace publishes three 12-month contract dimensions, and we read them there on 31 August 2026.

The striking part is not the absolute numbers, it is the shape. Most enterprise software gives you a volume break and most of this category does too. CloudHealth does not: every published tier lands on exactly 2.50 percent of the AWS spend under management, so the tool gets more expensive in absolute dollars in exact proportion to the bill you hired it to reduce. For comparison, the IBM Cloudability listing runs from 3.00 percent down to 2.21 percent as spend grows, which means CloudHealth is cheaper on a smaller estate and Cloudability is cheaper by around 6 million dollars of annual spend. Each dimension also notes that additional fees apply above the cap, so the tier is a ceiling rather than a starting point.

Two honest caveats. Overage is listed at 0.03 dollars per unit and the listing does not define the unit, so get the increment in writing rather than inferring it. And these are list prices on a public marketplace listing, so a negotiated enterprise agreement will differ. That is precisely why the list matters: it is the anchor you negotiate against, and until now most buyers went into that conversation without one. The full breakdown, including the 12, 24 and 36 month terms and how the shape compares with fixed-subscription vendors, is in CloudHealth pricing explained, and twelve options are sorted by exactly this axis in the AWS cloud cost management tools comparison.

One further ownership note worth recording, checked the same day: the Tanzu CloudHealth documentation URLs now redirect into the Broadcom CA Enterprise Software IT Operations Management portfolio rather than the VMware Tanzu tree, while the AWS Marketplace listing still carries the VMware Tanzu CloudHealth name. The product has moved shelf again. If you are reading vendor documentation, check which portfolio you landed in before trusting its packaging claims.

Two situations where you should stay. First, if a managed service provider is delivering your FinOps practice on top of CloudHealth and doing it well, the platform is not what you are buying and replacing it swaps a working service for a tool with no service around it. Renegotiate the service, not the software. Second, if your governance genuinely depends on policy enforcement at scale across hundreds of accounts, that is the mature half of the product and lighter tools do not replicate it.

The case for leaving is narrower than the internet suggests, and it is mostly about fit rather than quality. Most tenants of any enterprise cost platform use a fraction of it: cost reporting, a handful of perspectives, budget alerts, and commitment tracking. If that describes you, write that list down and price it honestly against the renewal, because the gap between what you use and what you pay for is the entire business case and it does not require the platform to be bad.

If you do move, run both in parallel for one full billing cycle and reconcile to the provider invoice, not to each other. Amortization treatment, credit handling, and refund timing differ between platforms, and a variance you discover in month one is a configuration question while the same variance discovered after cutover is a credibility problem with your CFO.