Multi compartment cost reporting on OCI rests on three pieces working together. Compartments are logical containers that already structure resources for access control, and because the cost analysis console and cost reports group by compartment, a compartment per team, environment, or project gives an immediate allocation axis with no tagging at all. Defined tags add a second, cross cutting axis, application, cost centre, or environment, so you can slice the same spend the other way, which matters because one compartment holds many applications and one application can span compartments. The detailed cost and usage report, delivered to an object storage bucket, is the source of truth that turns interactive console views into a repeatable report you build every period and reconcile against Universal Credits drawdown. Set up all three and every line of spend has an owner and a purpose; rely on the console and compartments alone and you get exploration without durable accountability.
Here is how compartments structure cost, how tags complete the picture, and how to build reporting that drives action.
How do compartments structure OCI cost?
A compartment is OCI's primary organising container. Every resource lives in a compartment, compartments enforce access control through policies, and they can nest to mirror an organisation, so a division contains teams, a team contains projects, and resources sit at the leaves. For cost, this structure is a gift, because the cost analysis console and the cost reports can group spend by compartment, and nested compartments roll up, so you can read cost at project level and aggregate it to team and division without any extra work. The practical move is to design the compartment hierarchy with cost ownership in mind from the start: a compartment per team or project means the spend report has a natural owner for every line. The common failure is a flat compartment design where most resources sit in a single large compartment, which collapses the allocation and forces you to rely entirely on tags to recover the breakdown. A thoughtful compartment hierarchy does most of the allocation work before tags are even considered.
Why do you still need defined tags?
Compartments give one axis, but cost questions come on two. A compartment usually maps to organisational ownership, which team or project holds the resource, but you also need to ask what the resource is for: which application, which cost centre, which environment. Because a single team compartment can run several applications, and one application can have components across compartments, the compartment alone cannot answer the second question. Defined tags solve this. A defined tag namespace with a small set of mandatory tag keys, such as application, cost centre, and environment, attaches a consistent, governed second axis to every resource, and those tags flow into the cost and usage report alongside the compartment. Defined tags are governed centrally, unlike free form tags that drift, so you can enforce the namespace and the allowed values. With both axes present, a single report answers who owns this through the compartment and what it is for through the tags, and you can pivot cost either way, which is what cross team optimisation requires. Tag defaults applied at the compartment level help ensure new resources inherit the mandatory tags automatically rather than depending on every engineer remembering.
A Fortune 500 enterprise ran most of its OCI estate in a handful of broad compartments with inconsistent free form tags, so the cost analysis console could show totals but not who owned what across shared compartments. We redesigned the compartment hierarchy to a compartment per team and project, introduced a governed defined tag namespace with mandatory application, cost centre, and environment keys applied through tag defaults, and built a repeatable report off the cost and usage report files loaded into a query layer, reconciled against Universal Credits drawdown. Allocatable spend rose from roughly half the estate to nearly all of it, the monthly review moved from arguing about whose cost was whose to deciding fixes with named owners, and the teams retired idle resources they could finally see. Steady state OCI spend fell by close to a quarter. The figures are verified against billing data and anonymised.
How do you build the report and budgets?
Use the right tool for each job. The cost analysis console is for interactive exploration and quick answers, but multi compartment reporting that has to be repeatable and reconciled belongs on the detailed cost and usage report, which OCI delivers as files to an object storage bucket on a schedule. Load those files into a query layer, build the standard report grouped by compartment and by tag, and run the identical query every period so trends are comparable rather than reconstructed by hand each month. Reconcile the report against Universal Credits drawdown so finance sees both the resource level allocation and the commitment burn in one view, since an OCI estate on annual flex Universal Credits cares as much about pacing the drawdown as about per resource cost. Layer OCI budgets on each major compartment with alert thresholds so a team is warned before it overruns, giving you an automated backstop under the human review. The result is a reporting system that surfaces variance by owner every period and feeds the spend review cadence with decisions rather than dashboards, which is the whole point of allocating cost in the first place.
Frequently asked questions
What is a compartment in OCI?
How do tags and compartments work together for OCI cost?
Where does the OCI cost and usage report fit?
Give your OCI spend an owner
We design the compartment hierarchy and defined tag model, stand up repeatable cost and usage reporting reconciled against Universal Credits, and feed it into a review that drives action, with no provider commission and answering only to you. Our guarantee is plain: we reduce your cloud spend or we reimburse our service fee, on either a Fixed Fee or a no risk Gainshare basis. Book a strategy call to scope it, and follow more in The Cloud Spend Navigator.
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.