FinTech Startup
FinanceHow SquareOps Helped a FinTech Startup Reduce AWS Spend After a Cost Spike
See how SquareOps helped a fast-scaling FinTech startup cut AWS costs by ~30% in 3 months—without downtime or performance impact.
CloudHealth starts from governance for finance and FinOps. SpendZero starts from the waste an engineer can remove this week.
CloudHealth, now CloudHealth by Broadcom and formerly VMware Tanzu CloudHealth, is one of the original enterprise FinOps platforms. Its strength is governance at scale across AWS, Azure and Google Cloud: perspectives, policies with approvals, showback and chargeback.
SpendZero is built for the engineer who makes the change: it finds waste across AWS, Google Cloud, Azure and Kubernetes, puts a monthly saving on every finding, and fixes AWS findings in one click once you grant write access. The first scan is free.
Teams looking for a CloudHealth alternative are rarely short of reports. They want to know which resources to remove, what each one saves, and to make the change without a project. That is the job SpendZero is built for.
The checks run as soon as you connect, with no policies to write first. Each finding names the resource, says why it is waste and what it costs per month, so the team can sort by saving and work down the list.
On AWS, once you grant write access, SpendZero stops, deletes or resizes the resource after someone approves it, from the finding itself, and logs who did what. There is no policy to write first. Applied recommendations and what they saved are tracked.
SpendZero sizes CPU at the 95th percentile of daily peaks and memory at the 99th, plus a 15% buffer, over a 7, 14 or 30-day window. It never cuts memory for a container that was OOM-killed or CPU for one that is throttled, and it recommends node-group instance types on EKS, GKE and AKS.
Each row shows who leads: CloudHealth's genuine wins and SpendZero's. Rows where both do the job well carry no badge.
CloudHealth's wins are real: governance, chargeback and commitment management built for FinOps teams, and both tools now cover AWS, Azure and Google Cloud and allocate Kubernetes cost. SpendZero's case is speed to a saving: checks with no setup, a fix one approval away and safer Kubernetes recommendations.
It depends on scope, and on who you want running the platform.
If a FinOps team runs governance, chargeback and commitments across business units, CloudHealth is the stronger choice. If engineers own the bill and want to find, approve and remove waste across AWS, Google Cloud and Azure, with safe Kubernetes recommendations, SpendZero gets there faster and can replace it. Some teams keep CloudHealth for finance and add SpendZero for engineers.
Start free scanMost of what engineers use CloudHealth for carries over. The finance side works differently, so check who depends on it before your renewal.
Rather not make the changes yourself? SquareOps engineers use SpendZero on client clusters every week and take its recommendations through to production.
Not covered? An engineer replies within one business day.
consult@squareops.comCloudHealth is an enterprise FinOps platform built for governance: perspectives that group spend by business unit, a policy engine with automated actions and approvers, showback and chargeback, and commitment discount management across AWS, Azure and Google Cloud. SpendZero is a cost optimization tool built for engineers: it finds waste across AWS, Google Cloud and Azure, puts a monthly saving on every finding, fixes AWS findings in one click after approval once you grant write access, and gives Kubernetes request recommendations with safety guards. CloudHealth is stronger on governance; SpendZero gets an engineering team to its first saving faster.
Broadcom. CloudHealth began as CloudHealth Technologies, at cloudhealthtech.com, and was bought by VMware in 2018, where it became VMware Tanzu CloudHealth. Broadcom acquired VMware in November 2023, and the product is now sold as CloudHealth by Broadcom, with Arrow Electronics as its sole global provider since May 2024. Broadcom released a new CloudHealth experience with an AI assistant in June 2025.
Yes, for teams where engineers own the cloud bill. SpendZero covers AWS, Google Cloud and Azure, finds waste without policies to set up, fixes AWS findings once approved and sizes Kubernetes workloads on EKS, GKE and AKS, and you can start with a free scan. It is not the right replacement if a FinOps team relies on CloudHealth's perspectives, policy engine, chargeback with shared-cost rules or commitment management.
The usual shortlist is Apptio Cloudability, now part of IBM, and Flexera One for enterprise FinOps and chargeback; CloudZero for unit cost, such as cost per customer or feature; Kubecost or OpenCost for Kubernetes allocation; and the native tools, AWS Cost Explorer, Azure Cost Management and Google Cloud billing reports, which are free. SpendZero fits teams that want waste found and fixed across AWS, Google Cloud and Azure and their Kubernetes clusters.
CloudHealth, Apptio Cloudability and Flexera One all support showback and chargeback across business units, including rules for sharing costs that no single team owns. For Kubernetes, Kubecost and CloudHealth's collector can distribute shared cluster cost by namespace or label. SpendZero shows cost per account, service, team, namespace and label, which covers showback, but it has no shared-cost rules for formal chargeback.
CloudHealth does not publish a rate card. It is sold through Arrow on 12 to 36-month terms, and third-party sources describe the price as a percentage of the cloud spend it manages, with annual minimums. A free trial is available on request. SpendZero has a free first scan with no sales call, and paid plans for ongoing monitoring and fixes.
Yes. CloudHealth's automated actions can start, stop, reboot or delete EC2 instances and start or stop Azure virtual machines, on their own or triggered by policies, with approvers whose sign-off is required. They are switched on per account. SpendZero fixes AWS findings in one click from the finding, after a person approves, and records every action in an audit log.
Yes. A CloudHealth collector installed with Helm in each cluster gathers usage, and cluster cost can be allocated by request, by actual usage or both, then shown back or charged back by namespace or label. It also recommends CPU and memory requests. SpendZero uses a read-only agent installed with Helm on EKS, GKE and AKS, shows cost per namespace, controller, pod and label, and recommends requests with OOM and throttling guards plus node-group instance types, which your team applies. One-click Kubernetes rightsizing, including a GitOps mode that opens a pull request instead of changing the cluster, is on the way.
Yes. SpendZero scans AWS, Google Cloud and Azure accounts, and its Kubernetes cost works on EKS, GKE and AKS. CloudHealth also covers all three clouds, with longer history on multi-cloud governance.
No. CloudHealth is still sold and developed under Broadcom, which released a new user experience with AI features in June 2025. What changed after the VMware acquisition is how it is sold: through Arrow as sole provider. Some teams use their renewal to compare alternatives, and SpendZero's free scan makes that comparison cheap to run.
Kubernetes cost allocation compared with waste checks inside and around the cluster.
Spot instance automation compared with waste detection across storage, databases and network.
A billing-partner discount compared with removing the waste under it.
A hands-on comparison of the FinOps tools teams shortlist today.
Cost per namespace, workload rightsizing and node-group recommendations on EKS, GKE and AKS.
Finds the waste across AWS, Google Cloud and Azure, with one-click fixes.