Exivity Core turns consumption into a charge your billing process can use. Hypermeter turns cost into a number you can defend.
Both products apply rates, so rating is not the difference. The difference is what comes out of the end: an invoice versus an answer.
If you need to…
| If you need to… | Which product | Why |
|---|---|---|
| Invoice an external customer | Exivity Core | The output has to be a document somebody receives and pays, at the rates their contract states. |
| Charge back internally | Hypermeter or Exivity Core | Both support internal chargeback. Hypermeter leads when the cost spans many sources; Exivity Core leads when the charges come from usage it already meters and rates. |
| Meter VMware, Nutanix, Hyper-V or OpenStack | Exivity Core | Private infrastructure is metered at source, and that is where the Exivity Core extractors run. |
| Keep cost and usage data in your own building | Exivity Core | Self-hosted, including air-gapped. Hypermeter is multi-tenant SaaS and is not offered self-hosted. |
| Allocate shared platform or reserved capacity | Hypermeter | Attribution by measured demand, with deterministic remainders and totals that reconcile to source. |
| Report cost per customer, product or feature | Hypermeter | Cost per customer or per feature needs the data modelled at that level first, and that modelling is Hypermeter’s job. |
| Model AI agent economics | Hypermeter, with Exivity Core if you also bill for the tokens | Relating cost to outcome needs the data modelled down to the agent run. Add Exivity Core when the token consumption also has to appear on somebody’s invoice. |
| Replace the spreadsheet that assembles the monthly invoice | Exivity Core | Rates, tiers, commitments and credits become rules the system applies, instead of a person’s job on the third working day. |
| Replace the spreadsheet that allocates last month’s cost | Hypermeter | Allocation becomes a modelled rule that reconciles, rather than a formula one person understands. |
| Forecast next quarter and defend the forecast | Hypermeter | Stated method, training window, assumptions and error history: the things a finance director will ask about. |
How data moves between them
- 01Sources
Cloud bills, hypervisors, clusters, databases, tickets, licences, model providers.
- 02Exivity CoreMeter and rate
Consumption measured at source, contract terms applied, rated charge records produced.
- 03HypermeterModel and allocate
Cost attributed to the team, product or customer that drove it, at a declared grain.
- 04Invoices and decisions
A document somebody pays, or an answer somebody acts on. Usually both, for different audiences.
Exivity Core is not a prerequisite
Hypermeter ingests directly from HTTP APIs, databases, object stores and files. It can read a cloud billing export without Exivity Core being anywhere in the picture, and a Hypermeter-only setup runs exactly that way.
Where Exivity Core earns its place as a source is private infrastructure that public-cloud exports cannot see, and consumption that has already been rated against a contract before anyone tries to allocate it.
The interface, stated plainly
Today the connection between the two products is data, not a plugin. Exivity Core exposes rated charge records over its REST API and as scheduled exports; Hypermeter reads HTTP APIs, databases, object stores and files. Where your data policy allows the export, you point the second at the first. An air-gapped Core sends nothing anywhere.
This is straightforward to verify in an evaluation. If your architecture needs a tighter integration, tell us.
Three ways to run it
Start from the job you have. Add the other product when a job only it can do turns up.
Hypermeter only
An enterprise with cloud-first spend and no external billing requirement. Cost arrives from the providers, gets attributed to the teams, products and customers that drove it, and turns into showback, chargeback and unit economics. No invoice is ever produced, because nobody outside the company is being billed.
Read about Hypermeter Customer billing, or isolated meteringExivity Core only
A service provider whose need is billing and whose customers expect charges at contracted rates, or an organisation whose usage data cannot leave its own environment. Consumption is metered across the platforms they sell, contract terms are applied, and invoice-ready charges go to the billing process. This is how Tele2 runs: multi-platform infrastructure billed from one engine.
Read the Tele2 case study Hybrid metering plus wider economicsBoth
A service provider that bills customers with Exivity Core and runs its own internal unit economics and AI cost modelling in Hypermeter, so margin per customer stops being a quarterly spreadsheet exercise. Or an enterprise that meters on-premises infrastructure with Exivity Core and, where policy allows, feeds approved rated data to Hypermeter alongside its cloud spend.
Talk through your caseFor existing Exivity Core customers
Exivity Core is actively developed and fully supported. It prepares invoice-ready output and runs self-hosted, including air-gapped. Hypermeter does not replace it, and existing deployments are unaffected. Your deployment, contract, support arrangement and upgrade path are unchanged.
Hypermeter is a separately licensed addition: allocation of shared platforms, cost per customer and per service alongside revenue, and forecasts with their method shown — on the rated data Core already produces.
What does not change
- Your deployment and its version
- Your licence and contract terms
- Your extractors and rate cards
- Your support route
- The product name on your invoice
Which product should a new customer start with?
Start from the job. If you need to bill external customers, or to meter infrastructure inside your own environment, start with Exivity Core. If you need cross-source cost allocation, FinOps analysis or unit economics, start with Hypermeter. Bring the use case to a call and we will recommend one, the other, or both.
Do I need both Exivity Core and Hypermeter?
Not necessarily; each works on its own. You need Exivity Core if you bill external customers or meter infrastructure that cannot leave your own building. You need Hypermeter if you attribute cost across many sources, run cross-source chargeback, or report cost per customer, product or unit. Both together is the pattern for a service provider that bills customers and also runs its own internal unit economics.
Does Hypermeter replace Exivity Core?
No. Exivity Core is a current, actively developed product and Hypermeter is additive to it, not a successor. They do different jobs: one produces charges an external customer pays, the other produces answers an internal audience acts on. Existing Exivity Core deployments, contracts and support arrangements are unaffected by Hypermeter existing.
Can Hypermeter run self-hosted or air-gapped?
No. Hypermeter is multi-tenant SaaS with per-organisation isolation, and is not offered as a self-hosted or air-gapped deployment. Where cost and usage data cannot leave your environment at all, Exivity Core is the product that runs there: on a VM, on Kubernetes, or fully air-gapped.
Can Exivity Core do unit economics?
Exivity Core rates consumption and produces charges, and those charges can be reported on. What it does not do is the modelling that unit economics needs: declaring the grain of each fact, relating agent runs to the cases they served, or recognising revenue at the level where it actually occurs. That modelling is Hypermeter’s job, which is why the two exist as separate products.
Does Hypermeter require Exivity Core as a data source?
No. Hypermeter ingests directly from HTTP APIs, databases, object stores and files, so it can read cloud billing exports and other sources without Exivity Core being involved. Exivity Core is one useful source among several, particularly for private infrastructure and for consumption that has already been rated against a contract.
One demo, both products
Tell us what you are trying to do and the session covers whichever of the two answers it, or both.
Demos are 30 minutes, scoped to your question. We reply within 24 hours.