IBM Vies for Positioning as the de Facto FinOps Solution

IBM recently announced its acquisition of Kubernetes cost management solution Kubecost. This acquisition follows a series of FinOps-focused companies in recent years with Apptio (TBM/FinOps), Turbonomic (FinOps/resource automation), Nordcloud (FinOps services), and Instana (observability).

Answers to your top questions about the Kubecost acquisition

What should I know?

Kubecost enhances an already market-leading solution. In The Forrester Wave™: Cloud Cost Management And Optimization Solutions, Q3 2024, IBM was named the leading solution in cloud cost management. The Kubecost acquisition strengthens an increasingly commoditized feature, container cost allocation and optimization. By joining the IBM FinOps portfolio, IBM will have the most complete cloud cost management solution in this market, especially as CloudHealth innovation is deprioritized under Broadcom.

Despite having the broadest range of cloud cost management and optimization (CCMO) functionality, IBM isn’t generating thought-leading innovation in this space. Instead, we see these in mostly newcomer vendors such as Ternary for anomaly detection, Finout for virtual tagging and open platform cost ingestion, Vantage for network costing, Harness for autostopping, and CAST AI for Kubernetes pod spec optimization. These vendors are pushing what is possible in the cloud cost management space.

But perhaps IBM doesn’t need to fill that role. As the most complete CCMO solution on the market, IBM addresses the cloud cost needs of most major enterprises that need a stalwart multicloud management and optimization solution — the typical IBM clientele. Its capabilities enhance its consulting services in major enterprise accounts, and when needed, IBM can always enhance its services with these leading-edge point products.

What’s the impact on new and existing IBM/Apptio customers?

Although the company is working on different pricing models geared toward different payer levels, it raises the question of whether Kubecost will increase an already high price tag. It also raises questions about IBM’s ability to integrate the separate products in its CCMO portfolio. IBM Apptio’s present work already involves the momentous task of merging Cloudability’s and Turbonomic’s codebases. Questions remain about whether Kubecost’s codebase will factor into this merging. Or will it simply be an API integration or sold as a stand-alone solution? Given its diminished market share, a stand-alone solution seems the least attractive option. If IBM seamlessly integrates its multiple acquisitions into one solution, it could be the market's de facto FinOps solution. But many questions remain on whether that is a realistic possibility. Whatever the outcome, IBM has a lot of work ahead.

Why was Kubecost looking to be acquired?

Simply put, Kubecost needed an exit plan after some momentum losses. After ceding leadership as the only Kubernetes cost management player in the space, the acquisition was the only path forward. Major partnerships with Amazon Web Services to build out its Elastic Kubernetes Service cost monitoring capability and with Azure for its Azure Kubernetes Service cost visibility generated excitement but were short-lived. Its open-source project, OpenCost, launched with fanfare but had limited momentum. As new and arguably stronger solutions like Finout, Vantage, CAST AI, and Harness came onto the scene, Kubecost failed to compete in market share. It was time to get acquired — and it did.

The original article is here.

The views and opinions expressed in this article are those of the author and do not necessarily reflect those of CDOTrends. Image credit: iStockphoto/ArtemisDiana