A hybrid baseline is the single reconciled count of all qualifying deployment across on premises, public cloud, and Oracle Cloud Infrastructure at the cutoff. Each platform is measured by its own rule, then combined into one total you can defend. Done loosely, a hybrid estate produces gaps and double counting. Done well, it captures everything once.
Few Oracle estates sit in one place anymore. A typical ULA holder runs databases on premises, a growing share in public cloud, and increasingly some on Oracle Cloud Infrastructure, with workloads that have moved between them over a three to five year term. Certifying that estate is not a matter of adding three separate counts. It is a reconciliation problem. Each platform is counted by a different rule, the same workload can appear in more than one place across the term, and the contract treats the platforms differently. The certification baseline is the single, reconciled total that results when this is done properly, and it is where a hybrid estate either captures its full value or leaks it.
It is the single reconciled count of all qualifying Oracle deployment across every platform at the cutoff date. A hybrid baseline applies one consistent overall method, measures each platform by its own counting rule, and then combines them into the total you declare and must defend. The word that matters is reconciled. You are not certifying an on premises number plus a cloud number plus an Oracle Cloud Infrastructure number as if they were independent. You are establishing, for each real deployment, where it sat at the cutoff, which rule applies to it there, and the evidence behind it, so the combined figure counts every workload exactly once. That single reconciled number is the baseline, and it becomes the perpetual entitlement at exit.
A hybrid estate is not three counts. It is one reconciliation. Place every workload on a single platform at the cutoff, apply the right rule, evidence it, and count it once.
Each platform has its own counting logic, and a hybrid baseline has to respect all of them. On premises deployment is counted by physical processors and Oracle core factors, the familiar method. Public cloud follows the contract cloud clause, which may impose a continuous run condition such as 365 days, may define a virtual processor counting method, and may exclude a provider entirely or stay silent on it, in which case silence is not inclusion. Oracle Cloud Infrastructure is usually treated favourably and countable. The work is to apply the correct rule to each deployment based on where it actually lives at the cutoff, not to average across them or assume one rule fits all. Getting the per platform rule right is what makes the combined baseline both maximal and defensible.
The summary below is general orientation. Your contract language governs cloud in every case and must be read before applying any of it.
| Platform | Counting rule | Baseline consideration |
|---|---|---|
| On premises | Processors and core factors | Capture production, test, and DR fully |
| Public cloud, AWS or Azure | Contract cloud clause, often a run condition | Confirm each instance qualifies before the cutoff |
| Google Cloud | Often silent in the contract | Check whether it counts at all for your agreement |
| Oracle Cloud Infrastructure | Usually countable | Often the cleanest home for excluded cloud workloads |
Because movement creates both double counting and gaps. Over a long term, a workload may have started on premises, moved to public cloud, and perhaps landed on Oracle Cloud Infrastructure, leaving traces in inventories at each stage. Counted loosely, the same logical workload can be claimed two or three times, which inflates the number with deployments that do not exist at the cutoff and turns into exposure. Counted too cautiously, a workload that moved can fall through the cracks and be missed altogether. The reconciliation fixes both by fixing a single moment, the cutoff, and placing each deployment on exactly one platform at that moment, with the right rule and evidence. A clean hybrid baseline is complete, has no overlaps, and survives scrutiny precisely because the reconciliation is explicit rather than assumed.
Consider an anonymized organisation with databases split across on premises, two public clouds, and Oracle Cloud Infrastructure, after several migrations during the term. The first measurement either double counted migrated workloads or omitted them, depending on the source used. A reconciliation fixed the estate at the cutoff, assigned each workload to one platform, applied the correct counting rule to each, and checked cloud instances against the contract clause. Workloads on a silent public cloud were repositioned to Oracle Cloud Infrastructure or on premises in time to count. The figures are indicative and the result turned on the contract, but the reconciled baseline was both higher and cleaner than any of the loose counts, because it captured everything once and could prove it.
A hybrid baseline depends on cloud rules and full estate counting working together. Read cloud deployments and ULA certification for the cloud counting rules, and cloud counting language to negotiate up front for shaping those rules before exit. For the complete method that ties contract, counting, and timing together, see the ULA exit strategy guide.
It is the single reconciled count of all qualifying Oracle deployment across on premises, public cloud, and Oracle Cloud Infrastructure at the cutoff. A hybrid baseline applies one consistent method, with each platform measured by its own counting rule, then combined into the total you certify and can defend.
On premises is counted by processors and core factors. Public cloud follows the contract cloud clause, which may set a continuous run condition or a virtual processor method, and may exclude a provider. Oracle Cloud Infrastructure is usually countable. Each platform is measured by its own rule, then reconciled into one baseline.
Because the same workload can move between platforms during the term, creating double counting or gaps if measured loosely. A hybrid estate needs one reconciliation that places each deployment on exactly one platform at the cutoff, applies the right counting rule, and evidences it, so the baseline is complete without overlaps.
Book a confidential assessment and we will reconcile your hybrid estate at the cutoff, apply the right rule to each platform, and build a baseline that is both maximal and defensible.