Kubecost vs. CloudHealth Comparison

Who should you choose and why?

✋ Most important consideration

• If Kubernetes applies to greater than 50% of workloads, you probably want to leverage a solution focused on that, like Kubecost. However, if you’re looking to build an enterprise “Cloud Center of Excellence” (cloud financial management, policies, and governance), CloudHealth is the better fit.

🤔 Strongly consider Kubecost over CloudHealth if

• If Kubernetes insights are of singular importance, we would recommend Kubecost.
• You want better insights for optimizing container utilization. CloudHealth has less mature tools for drilling down to the container level.
• Getting the latest cloud spend data visible in your dashboard sooner is crucial for your engineering team.

🤔 Strongly consider CloudHealth over Kubecost if

• You want a more mature platform for monitoring native services on Azure, Google Cloud Platform, and AWS.
• You want to analyze and manage cloud cost, usage, security, and governance in one place through a cloud management platform (not just “cost management”).
• The Finance department at your company will make heavy use of the tool you chose.
• You want some kind of discount management tool on the same platform.

📝Other Notes

• CloudHealth has powerful dynamic reports called "perspectives" that are really handy for finance teams to get a grip on the spend activity of various business units.
• If one of your mandates is tying infrastructure costs to business processes and metrics (cost per API call, etc.), your team could stitch together Tableau (or a similar BI platform) and CloudHealth to get there.