Best chargeback tools for hybrid cloud
Chargeback creates a counterparty with a financial reason to dispute your numbers, which raises the bar from roughly right to defensible line by line. Hybrid cloud raises it again, because private infrastructure arrives without a price. This guide ranks eight tools on the five things a hybrid chargeback programme needs, and is honest about which are showback tools wearing a chargeback label.
Exivity is an independent EU company with no investors outside the EU; no cloud provider, hyperscaler or reseller owns it. Hosted entirely within the EU or run in your own environment, it is built to meet SEAL-3 (digital resilience) of the EU Cloud Sovereignty Framework.How sovereign deployment works →
Claims about the tools named here were checked against their public documentation on 2026-08-26. If something has changed, tell us and we will correct it.
Who this guide is for
Enterprise IT finance, FinOps and platform teams that have to charge cloud and datacenter cost back to the business units that caused it, and whose environment is not all in one public cloud. If you bill external customers, read the MSP guide instead; that is a billing job, not a chargeback job.
Showback reports cost to the team that caused it. Chargeback moves the budget. The moment money moves, the team on the other side has an incentive to find the line that is wrong, and most of them will. A tool that produces a plausible chart is enough for showback. Chargeback needs the method, the reconciliation and the dispute path. The chargeback vs showback guide covers the difference in depth.
How we evaluated
Five criteria, in the order a dispute exposes them:
Shared-cost method. How platform teams, reserved capacity, support and licences are split, and whether the method is a stated rule or a black box.
Reconciliation to source. Whether the allocated total ties back to what was billed, to the cent, and what happens to the remainder.
On-prem and virtualisation coverage. Whether the tool can cost a VMware or Nutanix cluster at all, and whether it meters consumption or models a total.
Showback-to-chargeback path. Whether you can run showback first, agree the method, and switch to chargeback without rebuilding.
Defensibility. When a team disputes a charge, can you show the usage line, the weight and the source it came from?
One Exivity product appears, placed where the criteria put it. Claims about other vendors are from their public material, checked on the date above.
The ranking
1. IBM Apptio Cloudability
What it is. The enterprise FinOps platform inside IBM Apptio’s technology business management portfolio.
Best for. Large enterprises that want the analyst-leading platform, six personas served from one allocated dataset, and a portfolio that stretches to total IT cost.
Strengths. Business Mapping rules and Cost Sharing for shared spend, container cost allocation, unit economics, budgets and forecasts, and the strongest analyst standing in the category. Showback and chargeback are named solution areas. For on-prem, Apptio’s IT financial management products model total cost from finance data.
Limits. Cloudability itself reads cloud bills; private infrastructure is costed in the ITFM suite as a modelled total, not metered consumption. Allocation rules are configured in the product; ask how a disputed share is traced to its weights and whether the allocated total reconciles to the invoice. Implementation weight is real.
Pricing. Essentials, Standard and Premium tiers, no public numbers, free trial.
2. Hypermeter
What it is. Hypermeter, built by Exivity, is a SaaS platform for cross-source cost allocation, FinOps analysis and unit economics. It brings cost and usage data together, applies the allocation rules you define, and shows the result by team, product or customer, with every figure traceable to its sources.
Best for. Organisations where the number will be challenged, where part of the environment is private infrastructure, and where the allocation method has to be readable rather than trusted.
Strengths. Meets all five criteria, and the fifth is what it is built for. Shared cost is allocated by measured demand with floored shares and deterministic tie-breaks; the allocated total reconciles to the source; the weights and source identifiers are retained as evidence; and cost that genuinely has no driver goes on an explicit unallocated line with its provenance rather than being spread to make the chart complete. Every calculation is SQL in your own pipeline, versioned and rerunnable. Showback and chargeback read from the same model, so the switch is a policy change, not a rebuild. For organizations that need metering at the source, or an actual internal invoice, Exivity Core, the metering and billing engine, sits beside it and derives a rate for VMware, Nutanix, OpenStack and bare metal from capital, facilities and support.
Limits. Batch, not real-time. No commitment automation, no rightsizing, no write access to anything. Reporting is composed from the vocabulary the model declares, not free-form SQL, so some ad-hoc questions belong elsewhere. Not on the analyst quadrants.
Pricing. See pricing.
3. Flexera One
What it is. A hybrid IT management suite covering IT asset management, SaaS management, FinOps and AI cost management.
Best for. Enterprises that need chargeback as one discipline in a programme that also covers licences and SaaS, with a normalised inventory of the whole environment.
Strengths. Genuine hybrid reach: on-prem inventory and entitlement through Technopedia, cloud cost optimisation with rate and usage levers, and the industry’s most-cited cloud research. The only suite in this set credible on licences and cloud at once.
Limits. On-prem is inventoried, not metered into a consumption rate. Allocation runs on the suite’s model. No published pricing, tiers or trial. Heavy for a team that only needs chargeback.
Pricing. Not published.
4. VMware Cloud Foundation Operations (formerly Aria and vRealize costing)
What it is. The cost and chargeback capability inside VMware’s private cloud platform, with Cloud Director Chargeback for VMware cloud providers.
Best for. Organizations that are VMware end to end and want the cost engine inside the hypervisor platform.
Strengths. The most detailed private cloud cost model on the market, with a reference cost database and a published cost-driver breakdown, discovered automatically with no agent or export. Now aligned to FOCUS, so private cloud cost can be shaped like a public cloud bill. Serves internal showback and provider billing from one engine.
Limits. It costs VMware and effectively nothing else, which is narrower than “hybrid” implies. Public cloud, Nutanix, bare metal and SaaS need another tool. Post-acquisition licensing is bundled and negotiated. Cost driver customisation needs a higher edition.
Pricing. Not published; edition-gated.
5. Nutanix Cloud Manager Cost Governance
What it is. Nutanix’s on-prem cost metering and chargeback for Nutanix clusters, now operating entirely inside the datacenter.
Best for. Nutanix organizations, especially dark-site and air-gapped ones.
Strengths. Real-time cost metering built into the platform, a total-cost-of-ownership model covering hardware, software, facilities, people, services and telecom, departmental chargeback, and user-defined unit rates for provider use. Nothing leaves the perimeter.
Limits. Nutanix only. The moat is the cage: nothing else in the environment is covered.
Pricing. Not published; 90-day trial referenced.
6. Finout
What it is. A FinOps platform for cloud, Kubernetes, SaaS and AI spend with virtual tags over a unified data layer.
Best for. Cloud-native organizations that want full allocation without a tagging project and a fast first view.
Strengths. Virtual tags, shared cost redistributed to reach 100% allocation, a stated 48-hour time to first view, and agents that route findings into Jira and Slack. Showback is a named use case.
Limits. No on-prem source. Allocation is completed by redistribution rather than reconciled with a visible remainder; ask what happens to a late credit or a rounding difference. Built for showback more than for a disputed chargeback.
Pricing. Tier names and per-integration uplifts published; tier prices not.
7. CloudZero
What it is. A cloud cost platform, now positioned around AI ROI, that allocates 100% of spend without tagging and reports unit cost.
Best for. Cloud-native SaaS businesses that want cost per customer and engineer-facing visibility.
Strengths. Allocation without tagging, hourly granularity, streaming ingestion, a deep customer proof library, and unit economics as the point.
Limits. No on-prem or virtualisation source. The allocation engine is proprietary. Chargeback across a hybrid organisation is not what it was built for.
Pricing. Single subscription, everything included, no public numbers.
8. Kubecost
What it is. In-cluster Kubernetes cost allocation, now part of IBM’s Apptio portfolio.
Best for. Chargeback across namespaces inside a Kubernetes environment.
Strengths. Real-time allocation by namespace, deployment and label from live cluster metrics, custom pricing for on-prem nodes, a generous free tier. Runs wherever Kubernetes runs.
Limits. Kubernetes only. Chargeback across an organisation, with rate cards and shared cost outside the cluster, needs another tool; the intended path is Cloudability.
Pricing. Free up to 250 cores; Enterprise tiers not published.
Side by side
Tool | Shared-cost method | Reconciles to source | On-prem coverage | Showback to chargeback | Defensibility |
|---|---|---|---|---|---|
Cloudability | Rules-based, configured in product | Ask | Modelled via ITFM | Yes | Rules visible in product |
Hypermeter | Weighted by measured demand, stated | Yes, with explicit unallocated line | Metered via Exivity Core | Same model, policy switch | SQL, versioned, evidence retained |
Flexera One | Suite model | Ask | Inventoried | Yes | Ask |
VMware VCF Operations | Cost drivers, published | Within VMware | VMware only, metered | Yes | Reference database |
Nutanix Cost Governance | TCO model | Within Nutanix | Nutanix only, metered | Yes | On-box |
Finout | Redistribution to 100% | Ask | None | Showback-led | Virtual tags |
CloudZero | Proprietary | Ask | None | Showback-led | Proprietary |
Kubecost | Within cluster | To cloud bill | Kubernetes on-prem, custom price | Within cluster | Live metrics |
“Ask” means the vendor’s public material does not state it either way; it is the question to put to them.
How to choose
Start from the dispute. Picture the platform team’s lead reading their charge and finding the line they disagree with. Ask each vendor to show you, on their product, the usage record, the weight, the method and the source total behind that line. The tools that can do it in the demo are the ones that can do it in the meeting.
Decide where on-prem cost comes from. Modelled from finance data (Apptio ITFM, Flexera), metered natively inside one vendor’s stack (VMware, Nutanix), or metered across platforms into a derived rate (Exivity Core). The first is fine for showback; the last two are what a chargeback survives.
Run showback first. Most organisations should not attach money in year one. Choose a tool where the switch to chargeback is a policy change on the same model, not a second implementation.
Be honest about the environment. A VMware-only shop should look hard at VCF Operations. A Kubernetes-only team should install Kubecost. Hybrid means neither is enough.
Insist on a visible unallocated line. Any tool can reach 100%. Ask how, and whether the remainder is shown or spread.
Frequently asked questions
The questions buyers ask when they are choosing between these tools, in the words they use.
Ask us about your use caseWhat is the difference between showback and chargeback tools?
Any allocation tool can produce a showback report. A chargeback tool additionally needs a documented shared-cost method, reconciliation to the invoice, rate cards, stable definitions and a dispute path, because the recipient has a financial reason to challenge the number.
Can cloud FinOps tools charge back on-prem cost?
Most cannot, because a private cluster does not produce a billing export. Cloudability and Flexera model it; VMware and Nutanix meter their own stacks; Exivity Core meters across platforms into a rate that Hypermeter then charges back.
Which Exivity product is this guide about?
Hypermeter, the FinOps platform, is the ranked entry. Exivity Core, the metering and billing engine, is what you add when on-prem consumption has to be metered at the source or when the chargeback has to become an actual internal invoice.
How do you charge back a VMware cluster?
Decide what a vCPU-hour costs by amortising capital and apportioning facilities and support, choose between allocated and consumed capacity, decide what to do with reserved-but-idle, and reconcile the result to the cluster's real cost. The [chargeback vs showback guide](/learn/chargeback-vs-showback) has a worked rate build-up.
What should the unallocated percentage be?
Lower than last quarter. An explicit unallocated line with provenance is a work queue; a hidden one is a spread that will be found. The [cost allocation guide](/learn/cost-allocation) covers remainder handling.
Which is cheapest?
Kubecost has a free tier for a single cluster. Nobody else in this set publishes enterprise prices. Price on your sources and your organization.
Not sure which one fits?
A demo scoped to your question, run by an engineer. Bring one cost source and leave with a recommendation.