OCI splits spend two complementary ways. Compartments give a structural split, grouping resources by team or environment, and they are governed by design. Defined tags give a flexible, cross cutting split, such as application or cost centre, that can span compartments. For chargeback, use defined tags rather than free form ones: defined tags live in a tag namespace with controlled keys and permissions, so they stay consistent, while free form tags are ad hoc pairs anyone can set and whose keys drift until they are useless for allocation. The two facts that govern an OCI tagging program mirror every cloud. First, mark tags as cost tracking so they appear in Cost Analysis and the cost and usage report. Second, enforce at creation with tag defaults so resources born in a compartment receive their required tags automatically, because coverage is a creation time problem. Pair a small mandatory tag set with compartments and the result is a bill you can report by structure and by business dimension at once, with little left unallocated.
Here is the scheme, how it pairs with compartments, and the enforcement that makes it hold.
Defined tags or free form tags?
Use defined tags for anything that touches money. A defined tag belongs to a tag namespace, has a controlled key, and is governed by permissions, so the key cannot quietly fork into three spellings across teams. Free form tags are convenient for engineer notes but unreliable for cost work because nothing keeps them consistent. Mark the defined tags you allocate on as cost tracking tags, which is what makes them selectable as a grouping in Cost Analysis and present as columns in the cost and usage report. Without cost tracking, a tag still organises resources but does not slice the bill.
Which tags are worth standardising?
Pick the smallest mandatory set that answers what finance and engineering ask, and let compartments carry the structural split so tags carry the business one.
| Tag (namespace.key) | What it answers | Example values |
|---|---|---|
| finance.owner | Which team is accountable | payments, logistics, data |
| finance.environment | Production versus non production | production, staging, dev |
| finance.application | Which service or product | billing, portal, etl |
| finance.cost_centre | Where the cost charges back | cc_5102, cc_4417 |
Four cost tracking defined tags, applied consistently, allocate the large majority of spend. Resist adding more until these reach full coverage, because each extra mandatory tag lowers the rate at which resources get fully tagged.
How do you keep unallocated spend low?
Allocation is a coverage problem, so enforce at creation and measure the gap. Set tag defaults on each compartment so any resource created there automatically inherits the required tags, which closes the most common leak, new resources born untagged. Apply the same defaults through infrastructure as code so programmatic deployments comply too. Then build one report from the cost and usage report that splits monthly spend into tagged and untagged by compartment, and review it on a cadence, chasing the untagged remainder down. The number to watch is the unallocated share. Driving it from a fifth of spend toward a small remainder is usually worth more than any single rightsizing, because allocation is what turns every later optimization into someone's responsibility.
A worked example
A European SaaS company running on OCI had compartments by team but no consistent tags, so cross cutting questions, what does the billing application cost across environments, could not be answered, and roughly a third of spend was effectively unallocated. We created a finance tag namespace with four mandatory cost tracking tags, set tag defaults on every compartment so new resources inherited them, and applied the same defaults in Terraform. Within two billing cycles the untagged share fell into the low single digits, and finance could finally split cost by application and cost centre across the whole tenancy. Once each team saw its own number, idle volumes and oversized shapes started disappearing without a central mandate. Figures are verified against billing data and anonymised.
Frequently asked questions
What is the difference between defined tags and free form tags on OCI?
How do compartments and tags work together on OCI?
How do you enforce tagging on OCI?
Make every dollar accountable
We design and enforce OCI tagging schemes that pair with compartments to allocate spend to owners, then use the allocation to find waste, as an independent advisory that takes zero provider commissions and answers only to you. Our guarantee: we reduce your cloud spend or we reimburse our service fee, on a Fixed Fee or a no risk Gainshare basis. Download the OCI Universal Credits guide, read the deeper OCI cost optimization guide, and start with reading your OCI bill line by line.
Put a defensible number on your cloud spend.
No provider in the room, no published price list. Tell us your footprint and we will scope the savings against your billing data — we reduce your cloud spend or we reimburse our service fee.
The Cloud Spend Navigator: what changed in cloud pricing, commitments, and FinOps — no vendor spin.