Sovereign & Hybrid Cloud — metering you control

What the cloud-native tools cannot see

Half your infrastructure is invisible to a cloud-only tool

Most FinOps tools read a billing export. VMware, Nutanix, OpenStack, and bare metal do not produce one, so the spend that sits on them is never rated, never allocated, and never in the same report as the cloud.

Private infrastructure

VMware and Nutanix clusters, OpenStack, Hyper-V, Oracle VM, Azure Stack. Storage arrays, network, licences, colocation. None of it has a billing export.

The rate nobody set

Public cloud hands you a price. A cluster you bought four years ago does not. The rate has to be derived, and the derivation has to survive an audit.

The migration case

Cost per workload on each side is the business case for moving it. Two tools and a reconciliation cannot produce that number.

Platform by platform

Every platform, with the metric that matters for it

Virtualisation is metered on vCPU, vRAM, storage, and IOPS allocations. Kubernetes on namespaces and labels. Bare metal on Redfish hardware inventory and telemetry, mapped to billable usage by your rules. Public cloud on the bill.

Public cloud

billing exports · effective cost · FOCUS

Hybrid and private platforms

vCPU · vRAM · storage · IOPS allocations

Containers

namespace and label allocation

Bare metal and hardware

Redfish inventory and telemetry, mapped to billable usage by your rules

Redfish

Services, licences, and everything else

REST · SQL · CSV · webhooks

Something not listed? Every integration, and the REST extractor for the rest →

Deployment and data boundary

Runs where the data has to stay.

Sovereignty, defence, public sector, regulated finance and healthcare. If cost and usage data cannot leave the building, Exivity Core comes to the building. Nothing crosses the boundary unless you define an export.

Self-hosted VM or Kubernetes

Exivity Core in your own environment, under your own change control.

Air-gapped

Runs with no outbound connectivity where none is allowed.

No egress by default

Read-only against your platforms. Data leaves only through an export you define and approve.

SAML2, LDAP, RBAC

Your identity provider, your role model, an audit trail.

Then allocate and report

Once the infrastructure is metered, allocation works the same on both sides

Rated output is charged to the team, product, or entity that consumed it. Showback, chargeback, budgets, and unit economics apply to private infrastructure exactly as they do to cloud. Every figure traces back to the measured usage and the rule that priced it.

Deployment follows the data. An air-gapped Exivity Core sends nothing anywhere. Where your policy allows a defined export, approved rated data can feed Hypermeter for wider cost analysis; what crosses that boundary, and when, is your call.

Book a demo

Cloud Governance and Ownership · demo data

Questions

Before you talk to sales

The questions we hear most often, answered directly.

Ask us the rest

Kubecost covers our Kubernetes.

It covers Kubernetes. Exivity covers Kubernetes and everything under it: the hypervisor the nodes run on, the storage array, the licences, and the public cloud next to them, in one rated model.

We are mid-migration.

Both sides in one model is exactly the migration case. Cost per workload on each side, computed the same way, is the business case for moving a workload or for leaving it where it is.

How is a private cloud rate derived?

Cost base divided by the measured driver. The cost base is the hardware, licences, power, and people you assign to it. The driver is what you meter: vCPU hours, GB·months, namespace CPU. The derivation is kept and the rate is versioned, so a closed period re-runs to the same figure.

Can it run fully air-gapped?

Yes. Exivity Core installs on a VM or on Kubernetes in your own environment and runs with no outbound connectivity. Nothing about metering or rating depends on reaching us.

We used vRealize Business for Cloud. Where do we go?

Here. Exivity Core meters VMware at the same depth and adds the rest of the infrastructure and the public cloud next to it. The rate derivation and showback you had carry across as rules, not as a rebuild.

Which Exivity product is this?

Exivity builds two products. Hypermeter is SaaS for cross-source cost allocation, FinOps analysis and unit economics. Exivity Core collects and rates usage and supports billing workflows, and can run in your own environment. You do not have to choose before you talk to us: bring the use case and we will recommend one, the other, or both.

Go deeper