Oracle in the cloud, counted by vCPU and priced by the policy
Oracle Database in a public cloud is counted by vCPU, and the Processor Core Factor Table does not apply: that one sentence explains most budget surprises in Oracle cloud migrations. Three documents govern the position, your master agreement, your ordering document, and Oracle's cloud policy, and only the first two are contractual.
Prepared by Redress Compliance · August 7, 2026 · Oracle advisory. Based on 40 to 55 database cloud migrations benchmarked 2024 to 2025.
Executive summary
Four environments are named, and the counting is by vCPU. Oracle's policy lists Amazon EC2, Amazon RDS, Microsoft Azure, and Google Cloud Platform as Authorized Cloud Environments, Google Cloud included despite the older guidance still circulating.
The rule: two vCPUs equal one processor license where hyperthreading is enabled, one vCPU equals one where it is not.
And the core factor table is explicitly not applicable, which is where migrations from favorable hardware lose value: the loss added 20 to 40 percent of unplanned license demand across our benchmarks.
A routine infrastructure change can double the bill. The hyperthreading line is the only place in Oracle licensing where an instance family change or a rebuild doubles a license requirement without anyone touching the database, and nothing in the cloud console flags it.
In our migrations, rebuilds that disabled hyperthreading doubled the requirement on the affected estate, discovered at audit rather than at deployment.
Standard Edition has hard ceilings in the cloud. Every four vCPUs, rounded up, converts to one socket: SE2 caps at eight vCPUs on the three named providers with a Named User Plus floor of 10 per 8 vCPUs, and Standard Edition at sixteen.
A twelve vCPU instance is therefore not an SE2 deployment at all; it is an Enterprise Edition deployment nobody budgeted for.
The policy is not a contract, in either direction.
Oracle's cloud licensing document states it is educational only and may not be incorporated into any contract: Oracle can revise it without amending your agreement, a compliant design can go noncompliant at a revision, and a finding built on it is weaker than one built on your ordering document.
Both arguments lead to the same action: get the counting rule written into the ordering document at purchase. OCI sits outside the policy entirely, on its own OCPU based terms.
The BYOL math, one workload on six platforms
| Platform, 100 vCPUs with hyperthreading | Counting rule | Licenses needed |
|---|---|---|
| Amazon EC2 | Authorized Cloud Environment: two vCPUs per license, no core factor | 50 |
| Amazon RDS for Oracle | Named directly in the policy, same ratio | 50 |
| Microsoft Azure | Authorized Cloud Environment, same ratio | 50 |
| Google Cloud Platform | On the named list, despite older guidance | 50 |
| Oracle Cloud Infrastructure | OCPU based under separate terms: one OCPU is two vCPUs | 50 |
| Bare metal or dedicated host | On premises rules, core factor applies | 25 to 100, by processor model |
Compare capacity, not instance labels. On 0.5 factor hardware, 100 physical cores need 50 licenses on premises. Move the workload at 100 vCPUs and you still need 50, but 100 physical cores of capacity is 200 vCPUs with hyperthreading, which needs 100.
The core factor loss hides inside the unit conversion, which is exactly why cloud business cases built on compute pricing miss it until the audit finds it.
The counting rules, stated exactly
- Hyperthreading enabled: two vCPUs count as one Oracle processor license. Not enabled: one vCPU counts as one, doubling the requirement at a stroke.
- The core factor table does not apply in Authorized Cloud Environments, stated explicitly, the rule that strips migrations from favorable hardware of their multiplier.
- Named User Plus survives the move: standard NUP rules and minimums apply in the cloud, including the SE2 floor of 10 per 8 vCPUs regardless of how few people log in.
- Outside the named services, on premises rules return: private and hosted clouds, bare metal, dedicated hosts, and unnamed providers all carry the core factor and the virtualization reachability questions with them.
- OCI is not covered by the policy at all: Oracle's own cloud runs on OCPU counting under separate contractual terms, one reason the arithmetic differs there.
The Oracle CIO complete playbook
The five year Oracle plan the cloud position sits inside: the estate map, the audit calendar, the BYOL paths, and the contract levers that outlast the policy.
Get the white paper →The policy's legal status, and what to do about it
The cloud licensing document, most recently working from guidance dated 12 June 2024, states it is for educational purposes only and may not be incorporated into any contract. Buyers usually act on only one consequence of that, and there are two.
Against you: Oracle can revise the counting rules without amending your agreement, so a design compliant today can be noncompliant after a revision, and nothing obliges Oracle to keep the current vCPU ratio.
For you: an audit finding built on a non contractual policy is weaker than one built on your ordering document, a weakness worth pricing into any settlement.
Both cut to the same move, the counting rule written into the ordering document at purchase, alongside the BYOL terms the migration depends on. The multicloud constructions that sit above single provider deployments are worked in the multicloud licensing analysis and the Oracle on Azure guide.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What we saw across cloud migrations, 2024 to 2025
Across roughly 40 to 55 Oracle database cloud migrations Fredrik Filipsson benchmarked between 2024 and 2025, the license position, not the compute bill, set the final cost:
Unplanned license demand on the named public clouds, invisible in business cases built on compute pricing.
Enterprise Edition options enabled in the base image, licensable from first boot and unbudgeted.
The hyperthreading doubling was the sharpest single finding: rebuilds and instance family changes that disabled it silently moved the estate from the two to one ratio to one to one, with no console warning and no database change.
The cloud footprint is among the first data requests in any Oracle audit because it is easy to measure and easy to get wrong, and the on premises side of the same audit runs on the core factor arithmetic and the virtualization positions, priced line by line against the technology price list.
Your first five moves
- Inventory the cloud estate under the vCPU rule: instance families, vCPU counts, and hyperthreading state, per database, because the ratio is the bill.
- Alarm the hyperthreading state in your infrastructure pipeline, since a rebuild that disables it doubles the requirement silently.
- Audit the base images for enabled options, the 6 in 10 finding: EE options on in the image are licensable whether or not anyone uses them.
- Check every SE2 instance against the eight vCPU ceiling, because a twelve vCPU instance is an unbudgeted Enterprise Edition deployment.
- Write the counting rule into the ordering document, and never build a five year case on a policy that can move. The Oracle practice runs the position with you.
Frequently asked questions
How is Oracle Database licensed in public clouds?
By vCPU under Oracle's cloud licensing policy: in Authorized Cloud Environments, Amazon EC2 and RDS, Microsoft Azure, and Google Cloud Platform, two vCPUs count as one processor license with hyperthreading enabled and one vCPU counts as one without it.
The Processor Core Factor Table explicitly does not apply.
Is Google Cloud an Oracle Authorized Cloud Environment?
Yes. Oracle's policy names Google Cloud Platform alongside Amazon EC2, Amazon RDS, and Microsoft Azure, though older guidance written before the addition still circulates and leads buyers to price GCP workloads under the wrong rule.
The vCPU counting rule applies on GCP exactly as on the other named providers.
Why does moving Oracle to the cloud increase license costs?
The core factor is lost: hardware at the 0.5 factor halves the on premises count, and the cloud counts raw vCPUs instead. Matching 100 physical cores of capacity takes about 200 vCPUs with hyperthreading, needing 100 licenses against 50 on premises.
Across our migrations the loss added 20 to 40 percent of unplanned license demand.
What happens if hyperthreading is disabled on a cloud instance?
The counting ratio moves from two vCPUs per license to one per license, doubling the requirement, and an instance family change or rebuild can do it silently with nothing in the console flagging the licensing consequence.
It is the only place in Oracle licensing where routine infrastructure work doubles a bill without touching the database.
Can Oracle Standard Edition 2 run in the cloud?
Within hard ceilings: every four vCPUs count as one socket, SE2 caps at eight vCPUs on the named providers, and the Named User Plus floor is 10 per 8 vCPUs regardless of actual users.
An instance sized at twelve vCPUs is not an SE2 deployment at all, but an Enterprise Edition deployment nobody budgeted.
Is Oracle's cloud licensing policy legally binding?
No: the document states it is educational only and may not be incorporated into any contract. Oracle can revise it without amending your agreement, and a finding built on it is weaker than one built on your ordering document.
Both facts point the same way: negotiate the counting rule into the ordering document at purchase.
