Ownership
The map from cloud resources to owning teams and services, including automated inference sweeps that assign untagged resources by pattern.
At a glance
| Route | /ownership |
| Group | Govern |
| Page permission | ownership |
What it is
The map from cloud resources to the teams and services that own them — including automated inference sweeps that assign untagged resources by pattern, rather than requiring every resource to be tagged by hand.
Who it is for
Platform teams establishing accountability, and FinOps practitioners who have discovered that a significant share of the estate has no identifiable owner.
How it works
Teams and services are defined as first-class objects, and resources are assigned to services individually or in bulk.
Where resources are unassigned — the normal state in any estate of meaningful age — inference rules assign them automatically based on naming conventions, account structure, tags, or network placement.
An inference sweep applies those rules across the estate at once. An unassigned summary reports what remains unattributable, and a service graph visualises the resulting structure.
Features
- Team definition, editing, and deletion
- Service definition with per-service resource lists
- Individual and bulk resource assignment
- Inference rule creation and management
- Inference sweep applying rules across the estate
- Unassigned summary quantifying what remains unowned
- Service ownership graph
- Workspace context view
How to use it
Define the team structure to mirror the real organisation
Not the org chart's aspiration. Ownership that does not match reality routes work to the wrong people.
Review the unassigned summary
To understand the scale of the attribution gap before trying to close it.
Author inference rules for the patterns that exist
Naming conventions and account boundaries are usually the most reliable signals.
Run a sweep and review before accepting
Check the assignments the sweep produced rather than accepting them blind.
Iterate
Refine rules, re-sweep, and drive the unassigned figure down. This is a loop, not a one-off.
Confirm the structure is coherent
Using the service graph.
Keep ownership current as teams reorganise
Stale ownership is worse than none, because it routes work to the wrong people with apparent authority.
Why it matters
Every cost recommendation eventually needs an owner to act on it — and in most estates a large share of resources cannot be traced to anyone.
Inference sweeps solve this at a scale hand-tagging never reaches. And ownership is what turns a finding from an observation into an assignable task.
Connects to
- Feeds Cost Allocation, Unit Economics, and finding assignment in Opportunity Queue
- Complements Tag Governance
- Team allocation is a FinOps Maturity dimension
- Apex has a dedicated ownership capability — see Apex