Business mappings
Every line of every bill, with an owner
Business mappings turn provider bills into business costs. Ordered rules on any FOCUS field or tag set business unit, cost center, team, application and environment. Shared costs are split by the policy you choose, Kubernetes clusters by namespace, and each month is reconciled to the invoice.
Tags never cover the whole bill
Missing and misspelled tags:
Team, team and TeamName mean the same owner, and a share of resources carry none of them.Shared costs nobody claims:
Support plans, networking and security tooling serve everyone and appear on no team's report.Clusters are one line:
A Kubernetes cluster arrives as compute and storage lines, not as the namespaces and teams that use it.Allocations drift from the invoice:
Spreadsheet allocations add up to something close to the bill, and close is where trust ends.
Ordered rules
Rules on any field, applied in priority order
Each dimension has its own rule set. A rule matches on any FOCUS field or tag, such as account, subscription, service, region or a tag value, and sets the dimension to a fixed value or to the value of a tag. Rules run in priority order with a live preview of what they match, and a re-run applies them to past months.
- Business unit, cost center, team, application, environment
- Match on any FOCUS field or tag
- Live preview before you save
Kubernetes
The billed cluster cost, split by namespace
UnitVane takes each cluster's billed cost from the cloud bill and splits it across namespaces using OpenCost weights, with idle capacity as its own line. Because the split starts from the billed cost, the namespaces always add up to what the cloud charged.
- Starts from the billed cluster cost
- OpenCost weights per namespace
- Rules map namespaces to teams
Why cloud bills need owners
of organizations call managing cloud spend their top cloud challenge
Flexera, State of the Cloud 2025in open savings found at our sample company
Sample company, not a customer result
Reconciliation
Each month checked against the invoice
After every allocation run, the allocated total is compared with the billed total per source and month.
| Bucket | What it contains |
|---|---|
| Direct | Lines a rule assigned to an owner |
| Kubernetes | Cluster cost split by namespace, then mapped to owners |
| Shared | Pooled costs split by their policy |
| Unallocated | Lines no rule claimed, listed so you can write the next rule |
The four buckets add up to the bill. Unallocated spend is never dropped or spread silently.
Allocation the finance team can sign off
Hierarchy
Business unit, cost center, team, application.
Shared pools
Four split policies, visible in every report.
Kubernetes split
Billed cluster cost by namespace and idle.
Reconciliation
Allocated against billed, every month.
Re-run
Apply changed rules to past months.
Audit log
Every rule change recorded with who made it.
Business mappings: your questions answered
UnitVane
Keep exploring
Evaluate business mappings with your team
Bring your platform and FinOps priorities. We will walk through the data, controls and evidence for your evaluation.