Kafka FinOps: How to Do Chargeback Reporting

If you run Kafka as shared infrastructure, you've probably faced this question at some point: who is responsible for this topic, and what does it cost us? This is the core problem that Kafka FinOps tries to solve. In this post I'll explain what chargeback reporting means in a Kafka context, why it's hard, and how we implemented it in PartitionPilot . What Is Chargeback Reporting? Chargeback is a practice borrowed from cloud FinOps: instead of treating infrastructure costs as a single shared line item, you break them down by team, service, or product — and charge each one for what they actually use. In AWS or GCP this is relatively straightforward. Cloud providers give you cost allocation tags. But Kafka has no native cost model. It doesn't know about teams, budgets, or ownership. That's where chargeback reporting for Kafka comes in. The Two Cost Drivers in Kafka Before you can do chargeback, you need to understand what actually costs money in Kafka: Storage — every message written to a