Hybrid and multi-cloud
One view across every cloud and data center
Clusters on EKS, AKS, GKE, OpenShift and bare metal, priced from each provider's billing export or your own rates, and reported in one place with the same owners and policies.
What UnitVane brings to this job
Every cloud bill in one format, loaded once
Data sources
Reads AWS Data Exports, Azure Cost Management exports, Google Cloud billing in BigQuery and any FOCUS file, converts AWS CUR 2.0 to FOCUS, and replaces a billing month whole when the provider restates it, so nothing is counted twice.
Explore Data sources
Every bill in one place, grouped the way your business is
Cost explorer
Pick a period, group by business unit, team, service, account or any promoted tag, filter, and read amortized, billed or list cost. Save the view and send it by email every week or month.
Explore Cost explorerThe cloud bill and the clusters in one view
Cloud costs
Read AWS CUR 2.0, Azure cost exports, Google Cloud billing export or any FOCUS file, net of Savings Plans, reservations and credits. See what share of the bill runs on Kubernetes and what does not.
Explore Cloud costsEvery pod, namespace and team, priced from the invoice
Cost allocation
Node cost is split across pods on max(request, usage) and reconciled to the billed cost of each cluster. Group by up to 5 dimensions plus any label, and drill from cluster to pod.
Explore Cost allocationThe problem
Why it is hard today
Every cloud and your data centers in one view
A tool per cloud:
Each provider's console shows its own slice, with its own definitions.On-prem has no price:
Data center clusters are paid for up front and never reach team budgets.Different labels everywhere:
Every platform names teams and environments differently.
How UnitVane handles it
What you get
Five billing sources
AWS, Azure, Google Cloud, Oracle and FOCUS.
Data center pricing
Rate cards or amortized hardware cost.
One owner model
Labels from every platform resolve to the same keys.
Cross-cloud allocation
Group by provider, cluster, team or label in one view.
Same policies everywhere
Idle and shared rules apply to every cluster.
One agent
The same chart on every Kubernetes.
Outcomes
What changes for your team
One report for leadership
Cloud and on-prem spend by team in a single statement.
Fair comparisons
Workloads priced consistently wherever they run.
Your first weeks
What you see, and when
From the first agent run to findings that need a full usage history.
01
Within the first hour
The cluster, its nodes, namespaces and workloads appear in Diagnostics. Allocated cost per namespace, team and label follows as soon as billing data is in.02
Once billing data is in
180 days of history are read and allocated, plus 30 days of per-pod split cost history where AWS split cost allocation data exists. A brand-new AWS export can take up to a day to deliver its first file. The allocated history is kept; the raw billing rows leave the hub after 90 days.03
Within 30 minutes of the first allocation
Savings are computed, starting with findings that need no usage history, such as released volumes that still bill. Change proposals follow at the next daily regeneration.04
After 7 days of usage
Container requests are right-sized from p95 usage over 7 days of hourly samples.05
After 14 days
Node group sizing and abandoned workloads, which each need 14 days of data, and over-provisioned volumes, which also need Prometheus volume usage.
UnitVane works with your technology
Every major cloud, any Kubernetes, and the tools and model providers your teams already use.
Clouds and Kubernetes: AWS, Microsoft Azure, Google Cloud, Oracle Cloud, Kubernetes, Red Hat OpenShift, Rancher, VMware Tanzu, k3s
Your tools and model providers: Helm, Terraform, Argo CD, Flux, Prometheus, OpenTelemetry, Okta, Slack, Microsoft Teams, OpenAI, Anthropic, Mistral AI
Your questions answered
Keep reading
Expert guides and related solutions
Ready to see it on your own data?
A 30-minute walkthrough on your own billing data, for your clouds, your clusters and your model providers.