Oracle Cloud: Tenancy, Compartments and the Upgrade Path

Oracle Cloud Infrastructure uses vocabulary that differs from its competitors, which makes it feel unfamiliar even to people comfortable elsewhere. The concepts underneath are recognisable once the names are translated.

Tenancy and compartments

A tenancy is the top-level account: one per customer, holding everything. Inside it, compartments act as logical containers for resources. Compartments can nest, and policies are written against them.

The closest analogue elsewhere is a project or resource group, with one important difference: compartments are a first-class part of the permission model rather than mainly an organisational convenience. Policy statements reference compartments directly, so the way you divide them shapes how access control reads later.

For a small team, one or two compartments beyond the root is usually enough. Deep hierarchies are easy to create and awkward to simplify afterwards.

Trial versus upgraded state

Oracle draws a sharper line here than most. A trial tenancy carries a promotional balance and a restricted set of shapes. When the trial period or the balance ends, the tenancy does not simply start charging; it moves into a restricted mode where much of what was running becomes unavailable.

Upgrading converts the tenancy to a paid relationship. The practical effects are access to a broader range of compute shapes, the removal of trial ceilings, and continuity for anything already running.

This is why the catalogue distinguishes a trial profile from an upgraded one so clearly. They are not different sizes of the same thing; they behave differently at the moment the trial ends.

Current catalogue options

Choosing between them

A trial profile suits evaluation: trying the console, testing whether a workload runs, measuring performance before committing. An upgraded profile suits anything you intend to keep running, because it removes the cliff at the end of the trial window.

The general pattern of promotional balances is covered in trial versus paid cloud accounts.

After taking control

1. Change the password and enrol multi-factor authentication.
2. Review users, groups and policies across all compartments.
3. Rotate API signing keys and remove unknown ones.
4. List compute instances and block volumes in every compartment, including nested ones.
5. Confirm the tenancy state, trial or upgraded, and any remaining balance.
6. Set budget alerts.

Oracle’s terms of service continue to govern the tenancy throughout.