opencost

opencost: Monitor Kubernetes and Cloud Costs

OpenCost helps platform, FinOps, and engineering teams see how Kubernetes workloads and cloud services use and incur costs. It provides cost allocation, cloud cost visibility, and Prometheus metrics for Kubernetes environments.

View on GitHub Compare
Stars
6.8k
Forks
896
Stars, last 30 days
+46

Our take

Health score

68/100

How it is scored
Activity
65
Community
90
Issues
60
Pull requests
55

+46 stars in the last 30 days

  • More contributors than 78% of the projects we track
  • Merges more pull requests than 76% of the projects we track

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

6,823

Forks

929

Change since Nov 15, 2026: +2 stars·+1 forks

Overview

OpenCost is a cost monitoring system for Kubernetes and cloud infrastructure. It helps teams connect infrastructure spending to clusters, namespaces, workloads, and other Kubernetes resources, making it easier to understand where costs come from and how resources are allocated.

It is suited to organizations that need shared cost visibility across teams or cloud providers, including Kubernetes operators and FinOps practitioners. The project provides a Go implementation and cost specification; its web UI is maintained in the separate opencost/opencost-ui repository.

Key Features

  • Break down Kubernetes costs by cluster, node, namespace, controller, service, or pod.
  • Monitor cloud costs across AWS, Azure, and GCP.
  • Use cloud billing integrations for dynamic pricing, or supply custom CSV pricing for on-premises clusters.
  • Track in-cluster resource costs, including CPU, GPU, memory, and persistent volumes.
  • Export pricing and cost data through a Prometheus metrics endpoint.
  • Attribute carbon costs for cloud resources and track inference costs for compatible vLLM deployments.
  • Query allocation, asset, cloud cost, and efficiency data through APIs and an opt-in MCP server.

Use Cases

  • FinOps teams can allocate Kubernetes and cloud spend to teams, services, or workloads when investigating budgets or cost ownership.
  • Platform engineers can monitor resource allocation across clusters and expose cost metrics to existing Prometheus-based monitoring.
  • Organizations operating across AWS, Azure, or GCP can review cloud costs alongside Kubernetes workload costs.
  • Operators of on-premises Kubernetes can model resource costs using custom pricing data.
  • Teams running supported vLLM deployments can examine inference costs, including input and output token costs.

Getting Started

OpenCost requires a Kubernetes 1.20+ cluster. The README directs users to install and manage it with the official Helm chart:

helm repo add opencost https://opencost.github.io/opencost-helm-chart
helm repo update
helm install opencost opencost/opencost

See the README and installation documentation for configuration and integration details.

Considerations

  • A Kubernetes cluster is required for the documented installation, and OpenCost is managed through the official Helm chart. Standalone Kubernetes manifests have been removed.
  • Cloud pricing integrations require provider billing configuration; on-premises clusters can instead use custom CSV pricing.
  • In sharded Prometheus setups, the README advises configuring a global query endpoint such as Thanos Query, Cortex, or Mimir to avoid incomplete or intermittent exports.
  • The MCP server is disabled by default and must be explicitly enabled if needed.
  • The repository provides the implementation and specification, while its web UI lives in a separate repository.

Found this useful?

Share it with someone who would like opencost.