Kubecost is now best described as an IBM Apptio / Cloudability product surface for Kubernetes cost visibility, allocation, and optimization, while OpenCost remains the vendor-neutral open-source allocation project behind much of the ecosystem. The buyer-facing value is mapping cloud and infrastructure spend to Kubernetes concepts such as namespaces, deployments, pods, labels, teams, and shared services so engineering and FinOps teams can reason about cost ownership.
OpenCost’s current public site supports the source-safe core: it is a vendor-neutral open-source project for measuring and allocating cloud infrastructure and container costs in real time, integrates with AWS, Azure, and GCP billing APIs, supports on-prem custom pricing, exports pricing data to Prometheus, and is described as forever free and open source. The `opencost/opencost` repository is Apache-2.0 and active, with 6.6K+ GitHub stars at write time.
The commercial Kubecost layer should be evaluated through current IBM/Kubecost documentation and sales materials because plan names, retention limits, enterprise features, and savings claims can change. Teams should avoid treating old exact savings percentages or free-tier phrases as evergreen; instead, verify current multi-cluster, budget alerting, recommendation, retention, and support features against the plan they intend to buy.
