Search for a command to run...
Why we renamed kube-opex-analytics to reflect our focus on accurate ledger-based accounting
Ph.D. in Cloud Computing & Founder @ RealOps Labs. Expert in OpenShift Ecosystem & Multi-Cloud Kubernetes. Polyglot Engineer (Go/C++/Python). Building open-source observability tools.
No comments yet. Be the first to comment.
A reading of the State of FinOps 2026 report, and what it means for the next layer of cloud-native cost intelligence.
Most Kubernetes teams track pod CPU and memory. Almost none track what the cluster actually costs to run. We decided to change that. For the past 6 months, we have been running KubeLedger on our own O
A lightweight, open-source tool for tracking Kubernetes resource usage and costs breakdown per namespace
Enabling Prometheus Metrics in kube-opex-analytics
We are thrilled to announce a major milestone in our journey: kube-opex-analytics is now KubeLedger.
This is more than just a new logo. It represents a maturation of the project and a sharpened focus on what we do best: Kubernetes Resource Accounting.
When Rodrigue Chakode first architected this tool, the goal was to bring High-Performance Computing (HPC) rigor to Kubernetes efficiency. The mission was to track resources with extreme precision without the "heaviness" of standard observability stacks.
Over time, we realized that our users weren't just using us for "analytics" (looking at graphs). They were using us as a Ledger—a System of Record to allocate costs, charge back to namespaces, and hold teams accountable for their usage.
The name KubeLedger reflects this reality. We are the accountant for your cluster, designed to reveal the 30-50% of costs often hidden in unused resources and non-allocatable overhead.
The project has moved to a dedicated GitHub organization backed by RealOps Labs: github.com/realopslabs/kubeledger. This ensures long-term stability, enterprise-grade focus, and continuous innovation for the community.
To ensure the long-term sustainability of KubeLedger in an era where open source projects are often commoditized by large platforms without contribution, we are adopting the Business Source License (BSL 1.1).
What does this mean for you?
For Users & Companies: Nothing changes. You can use, modify, and deploy KubeLedger internally for free, just as before.
For Contributors: The source code remains fully available. Pull requests and community contributions are welcome.
For Cloud Vendors: You cannot sell KubeLedger as a managed service (e.g. SaaS, PaaS).
Our Commitment to Openness: We believe in the open ecosystem. That is why our license includes a strict Change Date. After 4 years, every version of KubeLedger automatically converts to the permissive Apache 2.0 License, guaranteed. This model protects our ability to innovate today while ensuring the software eventually belongs to the public domain.
We are standardizing our environment variables from KOA_ to KL_. (Don't worry, the old variables will continue to work for the next 6 months to ensure a smooth transition).
The Efficiency. We still believe that a cost monitoring tool shouldn't cost you a fortune to run. KubeLedger remains:
Lightweight: < 100MB memory footprint.
Maintenance-Free: No database management required (thanks to RRDtool).
Long-Term: 12 months of history out of the box.
Moving to KubeLedger is straightforward. We have prepared a detailed Migration Guide to help you switch your Docker images and update your manifests.
We are cloud specialists passionate about efficiency. By bringing HPC strategies to Cloud Native environments, we aim to eliminate waste and "guesswork" in capacity planning.
Thank you for trusting us with your cluster metrics. We are excited to build the future of Kubernetes Accounting with you.
— The RealOps Labs Team