Skip to main content
Ownership is available on Professional and above. Everyone can view it. Only organisation admins can create or change teams.

​
Make every dollar someone’s

Create teams, then tell CostOptix what each one owns. Spend is split by team across the app, in budgets, and on a sealed monthly bill. Anything no team owns shows as Unclaimed until someone takes it, so gaps are visible instead of quietly spread around. Open Ownership from the navigation. It has three tabs: The header shows how much of your spend is owned, how much is unclaimed, and the latest sealed bill.

​
What a team can own

Every item has one owner. If you try to claim something another team already owns, CostOptix tells you which team holds it, so totals never double count.

​
How cloud claims work

Cloud spend can be claimed three ways. When claims overlap, the most specific wins:
  1. Tag value, such as team=payments. Tagged spend across accounts.
  2. Service or resource group, such as one service in an AWS account or one resource group in an Azure subscription.
  3. Whole account. The team gets everything in the account that no tag, service or resource group claim takes.
Two rules keep the numbers exact:
  • One team tag key per cloud. Pick the key once per provider (for example team on AWS and owner on Azure). Every team on that cloud uses the same key, so one dollar can never match two tag values.
  • One split per account. An account is split either by service or by resource group, not both. Resource groups are Azure only.
Tag values come from your synced tags. If none show up, run a tag sync on the Tag Explorer page.

​
Unclaimed spend

The Unclaimed tab lists everything no team owns this month: Kubernetes namespaces, host units and cloud accounts, with the top resources in each account. Click any group to assign it to an existing team or a new one. Idle capacity that no team can share (because no team has direct cost on that cluster or machine) is also shown here as unallocated.

​
How each team’s cost is worked out

  • Direct cost is what the team’s own claims cost.
  • Idle cost on clusters and machines (capacity paid for but not used) is split across claiming teams in proportion to their direct cost.
  • Unclaimed cost and unallocated idle go to an Unclaimed line, so the bill covers every dollar.
Cloud accounts that also contain linked clusters or machines are scaled down so that spend is counted once, inside Kubernetes or Hosts.

​
Monthly bills

Each month closes into a bill. Once sealed, it never changes: later changes to ownership affect future months only.
  • Kubernetes lines are scaled to the real invoice when the cluster has a billing link, so reservations, savings plans, spot and negotiated discounts are included. The bill shows how much those discounts saved, and the reconciliation factor for each cluster. Clusters without a working link use estimated rates and are labelled.
  • Hosts lines come from each machine’s cost basis, with the share of hours the agents covered.
  • Cloud lines come from your cloud billing data.
Bills seal a few days after month end, once cloud billing data has settled. If a cluster’s billing link needs attention, it falls back to estimated rates so the bill still seals within about ten days. Until then, the Teams tab shows the live month to date. Use Export bill to download the sealed bill.

​
Where team spend shows up

  • Overview shows spend by team across cloud, Kubernetes and hosts.
  • Budgets can target a team.
  • The AI assistant can answer questions about a team’s spend.
AI coding tool usage is tagged with your own team names when you set them up (see AI coding tools), but it is not part of team bills yet.