CloudHealth by VMware

Name: CloudHealth by VMware
Brand: CloudHealth by VMware
Rating: 4.1 (46 reviews)

CloudHealth by VMware is a multi-cloud FinOps platform that consolidates billing and usage data across public clouds, produces cost allocation and reporting, generates optimization recommendations (rightsizing and commitment guidance), and enforces governance via policy-driven automation.

Est 1998|Valuation $62.1B|Raised $7.3B|31 Ref Customers

LinkedIn 2.0M|Web traffic 2K|FTEs 16,459

MarketsCloud-Native Application Protection Platform (CNAPP)Cloud Management & FinOps Cloud Cost Management

Published Oct 24, 2026

01Common complaints

- Small or early-stage organizations: Marketplace pricing and community feedback indicate the product may be cost-prohibitive and operationally heavy for small cloud footprints. - When specialized, high-depth GCP support at massive scale is a primary requirement: some enterprise-scale reports indicate weaker GCP support relative to AWS in certain deployments. - When UI performance and responsiveness are a primary constraint: multiple reviews reference lag and occasional freezing; validate performance in a trial or proof-of-concept (POC). - When highly explainable, auditable recommendation methodology is required without additional validation: community skepticism about rightsizing accuracy suggests validating recommendation methodology and comparing outputs against cloud-provider tools and internal metrics. - When an organization requires minimal disruption from vendor transitions: public discussion indicates support and portal changes following corporate transitions; clarify support processes and responsibilities in contractual terms.

Deal disqualifiers (poor fit)

Small cloud spend where platform overhead and minimum pricing are disproportionate
Teams that require specialized Kubernetes-only optimization or niche provider support
Environments that require validated parity across all clouds without tolerance for reduced depth on a specific cloud (e.g., large-scale GCP-first requirements)

Known limitations mentioned by vendor

Vendor documentation noted specific reporting template compliance constraints in one FOCUS reporting blog post; templates existed but required alignment with particular timing rules.

Commonly reported limitations (reviews/community)

UI performance lag and occasional freezing.
Export/reporting format limitations (requests for Office-format exports were common).
Integration gaps in certain environments and configuration complexity.
Support workflow confusion reported following the vendor transition; verify current support channels and SLAs.

Roadmap / new experience migration

Vendor communications in 2025 referenced ongoing updates to a new experience, including partner-level anomaly detection and reporting parity work. Buyers should request a current roadmap and details on feature parity for critical capabilities.

02Why they buy

Unique selling points supported by evidence and recurring user feedback: - Flexible customizable reporting (FlexReports) is frequently cited in reviews as a notable capability. - Chargeback/showback features and allocation capabilities are commonly referenced as useful for finance and FinOps workflows. - Long presence in the FinOps category and references in analyst-related summaries indicate market maturity. Where competitors may have advantages: - Lower barrier to entry / freemium options: some competitors provide free tiers suitable for smaller organizations. - Combined ITAM and FinOps functionality: certain competitors integrate licensing and asset management tightly with cost optimization. - Specialized commitment optimization: some focused tools emphasize deeper automation for RIs and Savings Plans.

Why customers chose CloudHealth (inferred from reviews)

Common reasons cited in reviews and community posts include:

strong out-of-the-box reporting and dashboards,
allocation/showback/chargeback capabilities,
policies and governance automation,
a centralized view for cloud finance stakeholders.

03Field reports

Below are verbatim quotes from review and community sources. Spelling/grammar reflect original reviewers.

Review platforms (G2 / AWS Marketplace external reviews)

Positive themes reported in reviews include reporting, visualizations, policy capabilities, trend identification, and cost visibility. - G2 reviewer: - Like: “operations have been streamlined and automated… easily create custom policies… detailed and accurate visibility…” - Dislike: “screen periodically lags… stalled… network and performance issues.” - G2 reviewer: - Like: “reports… provide a very good visual for the trends in cloud usage… suggestions… for improving resource efficency!” - Dislike: “option for exporting the graphical reports… as Microsoft Office files… notifications icon and settings hard to manipulate.” - AWS Marketplace review: - Like: “amazing tool about generating infrastructure reports… security feature… cost effective solution… budget reporting…” - Dislike: “not linked with any other application like Web apps… work on PaaS… issues in reporting which are complex to manage and run.” Common criticism signals from these review examples include performance lag, UI friction, export limitations, and integration gaps.

Capterra

Capterra shows the product as well rated on the platform overall, while customer service metrics on the listing fall into a lower sentiment band. Interpretation caution: The Capterra listing may combine experiences across multiple Tanzu products and may not be limited to the CloudHealth product.

Community / social (Reddit)

Community feedback is mixed and frequently focuses on support transitions, naming/packaging changes, multi-cloud parity, and data accuracy concerns. - Support access frustration (r/vmware): - “the option [to open a case] no longer exists… ‘Support’ link just directs me to Broadcom Support site… chaotic…” - Naming/packaging churn complaints (r/vmware): - “disconnect between the names and past documentation… from a technical standpoint it hurts supportability.” - Another user: “I’ve moved on… name changes… start to change around SKUs/purchase pricing/combos.” - Data accuracy skepticism (r/aws): - “I’ve had significant issues with CloudHealth and data accuracy so I’m inclined to not listen to them.” - FinOps community summary (r/FinOps): - “Multi-cloud reporting is not that great… Flex Reports… favourite part… after [the vendor transition] their support is not that great… relatively expensive.” - Enterprise-scale multi-cloud report (r/FinOps) (single poster’s view): - “CloudHealth: Great on AWS, OK on Azure, but GCP feels neglected. Chokes on our data volume.”

Why some customers left / considered leaving (from community signals)

Reported reasons include:

Support experience concerns after the vendor transition,
Confusing product naming and SKU changes,
Data accuracy concerns related to recommendations,
Perceived weaker depth on specific clouds (notably GCP in some reports),
Perception of high cost and enterprise orientation.

Vendor case study style claims

Vendor-authored case studies and blog posts describe customer outcomes such as sustainability tracking and cost reductions. These narratives typically do not disclose experimental design, baseline vs. control comparisons, or independently audited ROI.
Some vendor materials reference features in preview/beta (e.g., sustainability/carbon features described as beta), suggesting feature maturity may vary.

Analyst recognition claims

Vendor announcements reference inclusion in analyst reports. These references are summaries of vendor interpretations; buyers should obtain the original analyst reports to review evaluation criteria and scoring context.

Critical evaluation: vendor-authored narratives and vendor blog announcements should be validated through independent analyst reports, direct customer references, or trial verification when possible.

04Best fit

Company sizes

Mid-market to enterprise organizations with significant cloud spend, or
Managed service providers managing multiple customer tenants who require consolidated reporting and billing constructs.

Industries / verticals

SaaS and internet businesses
Financial services (fintech)
Enterprises with multi-cloud footprints and complex account structures

Roles and personas

FinOps lead / cloud financial manager
Cloud platform engineering
Cloud center of excellence (CCoE)
Finance/FP&A stakeholders consuming showback/chargeback reports
CIO / IT leadership responsible for governance

Pain points it addresses

Difficulty assigning cost ownership and allocating shared spend
Lack of standardized reporting across AWS/Azure/GCP
Management of commitments and savings plans
Enforcement of governance policies (budgets, anomaly detection, automated actions)

Qualification criteria (good fit)

Readiness to invest in tagging strategy and organizational mapping
Need for advanced reporting for enterprise stakeholders and multiple stakeholder views
Multi-account complexity and desire for centralized governance

05The pitch

What the product does (objective core value proposition)

CloudHealth by VMware (also referred to as VMware Tanzu CloudHealth and historically associated with VMware Aria naming) is a multi-cloud FinOps / cloud financial management platform that: - consolidates billing and usage data across public clouds, - produces cost allocation (showback/chargeback) and reporting, - generates optimization recommendations (rightsizing, commitments such as RIs/Savings Plans), and - supports governance through policy enforcement (budgets, anomaly detection, automated actions). An AWS Marketplace listing describes the product as providing visibility into multi-cloud spend, configuration-based recommendations, and a policy engine for governance automation.

Target market and positioning

Primary buyers are mid-market to enterprise organizations and managed service providers (MSPs) with substantial multi-cloud expenditure that require cost allocation, governance, and optimization workflows.

Positioning themes referenced in vendor materials include providing a centralized view for multi-cloud cost and governance, support for partner/MSP tenant constructs, and capabilities intended to support FinOps maturity (inform/optimize/operate).

Get a comprehensive analysis of CloudHealth by VMware including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Oct 24, 2026

01Common complaints

Small or early-stage organizations: Marketplace pricing and community feedback indicate the product may be cost-prohibitive and operationally heavy for small cloud footprints.
When specialized, high-depth GCP support at massive scale is a primary requirement: some enterprise-scale reports indicate weaker GCP support relative to AWS in certain deployments.
When UI performance and responsiveness are a primary constraint: multiple reviews reference lag and occasional freezing; validate performance in a trial or proof-of-concept (POC).
When highly explainable, auditable recommendation methodology is required without additional validation: community skepticism about rightsizing accuracy suggests validating recommendation methodology and comparing outputs against cloud-provider tools and internal metrics.
When an organization requires minimal disruption from vendor transitions: public discussion indicates support and portal changes following corporate transitions; clarify support processes and responsibilities in contractual terms.

Deal disqualifiers (poor fit)

Small cloud spend where platform overhead and minimum pricing are disproportionate
Teams that require specialized Kubernetes-only optimization or niche provider support
Environments that require validated parity across all clouds without tolerance for reduced depth on a specific cloud (e.g., large-scale GCP-first requirements)

Known limitations mentioned by vendor

Vendor documentation noted specific reporting template compliance constraints in one FOCUS reporting blog post; templates existed but required alignment with particular timing rules.

Commonly reported limitations (reviews/community)

UI performance lag and occasional freezing.
Export/reporting format limitations (requests for Office-format exports were common).
Integration gaps in certain environments and configuration complexity.
Support workflow confusion reported following the vendor transition; verify current support channels and SLAs.

Roadmap / new experience migration

02Why they buy

Unique selling points supported by evidence and recurring user feedback:

Flexible customizable reporting (FlexReports) is frequently cited in reviews as a notable capability.
Chargeback/showback features and allocation capabilities are commonly referenced as useful for finance and FinOps workflows.
Long presence in the FinOps category and references in analyst-related summaries indicate market maturity.

Where competitors may have advantages:

Lower barrier to entry / freemium options: some competitors provide free tiers suitable for smaller organizations.
Combined ITAM and FinOps functionality: certain competitors integrate licensing and asset management tightly with cost optimization.
Specialized commitment optimization: some focused tools emphasize deeper automation for RIs and Savings Plans.

Why customers chose CloudHealth (inferred from reviews)

Common reasons cited in reviews and community posts include:

strong out-of-the-box reporting and dashboards,
allocation/showback/chargeback capabilities,
policies and governance automation,
a centralized view for cloud finance stakeholders.

03Field reports

Below are verbatim quotes from review and community sources. Spelling/grammar reflect original reviewers.

Review platforms (G2 / AWS Marketplace external reviews)

Positive themes reported in reviews include reporting, visualizations, policy capabilities, trend identification, and cost visibility.

G2 reviewer:
- Like: “operations have been streamlined and automated… easily create custom policies… detailed and accurate visibility…”
- Dislike: “screen periodically lags… stalled… network and performance issues.”
G2 reviewer:
- Like: “reports… provide a very good visual for the trends in cloud usage… suggestions… for improving resource efficency!”
- Dislike: “option for exporting the graphical reports… as Microsoft Office files… notifications icon and settings hard to manipulate.”
AWS Marketplace review:
- Like: “amazing tool about generating infrastructure reports… security feature… cost effective solution… budget reporting…”
- Dislike: “not linked with any other application like Web apps… work on PaaS… issues in reporting which are complex to manage and run.”

Common criticism signals from these review examples include performance lag, UI friction, export limitations, and integration gaps.

Capterra

Community / social (Reddit)

Community feedback is mixed and frequently focuses on support transitions, naming/packaging changes, multi-cloud parity, and data accuracy concerns.

Support access frustration (r/vmware):
- “the option [to open a case] no longer exists… ‘Support’ link just directs me to Broadcom Support site… chaotic…”
Naming/packaging churn complaints (r/vmware):
- “disconnect between the names and past documentation… from a technical standpoint it hurts supportability.”
- Another user: “I’ve moved on… name changes… start to change around SKUs/purchase pricing/combos.”
Data accuracy skepticism (r/aws):
- “I’ve had significant issues with CloudHealth and data accuracy so I’m inclined to not listen to them.”
FinOps community summary (r/FinOps):
- “Multi-cloud reporting is not that great… Flex Reports… favourite part… after [the vendor transition] their support is not that great… relatively expensive.”
Enterprise-scale multi-cloud report (r/FinOps) (single poster’s view):
- “CloudHealth: Great on AWS, OK on Azure, but GCP feels neglected. Chokes on our data volume.”

Why some customers left / considered leaving (from community signals)

Reported reasons include:

Support experience concerns after the vendor transition,
Confusing product naming and SKU changes,
Data accuracy concerns related to recommendations,
Perceived weaker depth on specific clouds (notably GCP in some reports),
Perception of high cost and enterprise orientation.

Vendor case study style claims

Vendor-authored case studies and blog posts describe customer outcomes such as sustainability tracking and cost reductions. These narratives typically do not disclose experimental design, baseline vs. control comparisons, or independently audited ROI.
Some vendor materials reference features in preview/beta (e.g., sustainability/carbon features described as beta), suggesting feature maturity may vary.

Analyst recognition claims

Vendor announcements reference inclusion in analyst reports. These references are summaries of vendor interpretations; buyers should obtain the original analyst reports to review evaluation criteria and scoring context.

Critical evaluation: vendor-authored narratives and vendor blog announcements should be validated through independent analyst reports, direct customer references, or trial verification when possible.

04Best fit

Company sizes

Mid-market to enterprise organizations with significant cloud spend, or
Managed service providers managing multiple customer tenants who require consolidated reporting and billing constructs.

Industries / verticals

SaaS and internet businesses
Financial services (fintech)
Enterprises with multi-cloud footprints and complex account structures

Roles and personas

FinOps lead / cloud financial manager
Cloud platform engineering
Cloud center of excellence (CCoE)
Finance/FP&A stakeholders consuming showback/chargeback reports
CIO / IT leadership responsible for governance

Pain points it addresses

Difficulty assigning cost ownership and allocating shared spend
Lack of standardized reporting across AWS/Azure/GCP
Management of commitments and savings plans
Enforcement of governance policies (budgets, anomaly detection, automated actions)

Qualification criteria (good fit)

Readiness to invest in tagging strategy and organizational mapping
Need for advanced reporting for enterprise stakeholders and multiple stakeholder views
Multi-account complexity and desire for centralized governance

05The pitch

What the product does (objective core value proposition)

CloudHealth by VMware (also referred to as VMware Tanzu CloudHealth and historically associated with VMware Aria naming) is a multi-cloud FinOps / cloud financial management platform that:

consolidates billing and usage data across public clouds,
produces cost allocation (showback/chargeback) and reporting,
generates optimization recommendations (rightsizing, commitments such as RIs/Savings Plans), and
supports governance through policy enforcement (budgets, anomaly detection, automated actions).

An AWS Marketplace listing describes the product as providing visibility into multi-cloud spend, configuration-based recommendations, and a policy engine for governance automation.

Target market and positioning

Get a comprehensive analysis of CloudHealth by VMware including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →