Oracle cloud licensing, the knowledge hub.

A buyer side knowledge hub on Oracle cloud licensing, covering OCI policy, BYOL math, universal credits, authorized cloud factors and the audit posture for cloud deployments.

Oracle sells cloud licensing under three separate frameworks.

OCI native consumption, BYOL across OCI, AWS, Azure and GCP, and the authorized cloud policy that governs the third party deployments.

This hub explains how each framework works, where the audit risk sits and the buyer side moves that hold across the major cloud deployment shapes.

OCI policy in plain language

OCI consumption shape

OCI prices by OCPU consumption, by service tier and by region.

Universal credits sit on top, deductible against any service across OCI.

OCI BYOL

• Existing Oracle licenses convert to OCI consumption rights under the published BYOL ratio.
• BYOL pricing on OCI Database service is materially lower than license included pricing.
• Conversion ratios change by service. Confirm the ratio referenced in the schedule, not on the website today.

BYOL math across platforms

AWS BYOL

AWS deployments use the authorized cloud computing environments policy.

The two to one vCPU factor applies to per processor licensing.

Azure BYOL

• The same authorized cloud factor applies on Azure.
• Oracle Database on Azure uses the same per vCPU counting rule.
• Azure VMware Solution requires explicit license posture review.

Google Cloud BYOL

Google Cloud follows a separate Oracle partnership for hosted Database services.

Bare metal solution runs under different counting rules from VM based BYOL.

Universal credits

Credit shape

Universal credits are prepaid OCI consumption.

Credits deduct against any service at the published OCPU per service rate.

Credit burn discipline

• Track burn by service to avoid late year surge purchases.
• Tag every workload to a credit budget owner.
• Re forecast burn against the term every quarter.
• Negotiate carry forward language at signature.

The cloud policy version referenced in your schedule is the policy that counts. Read the schedule, not the latest webpage.

Authorized cloud policy

Policy version matters

The authorized cloud policy is updated by Oracle from time to time.

The version referenced in your contract is the version that counts. Read the schedule, not the latest webpage.

Deployment shape

• Reserved instances and savings plans do not waive the license question.
• Spot instances still count under the cloud factor.
• Containerised deployments need a written counting rule per service.

Cloud audit posture

Cloud audit data exchange

Cloud audits read AWS, Azure and OCI deployment data through customer provided exports.

The exports need to match the counting rule, not the seller assumption.

Audit defense for cloud workloads

• Map every workload to a counting rule before the audit notice arrives.
• Run a mock cloud audit at least once a year on production workloads.
• Document any change in cloud architecture against the cloud policy version.
• Pair the audit defense with the renewal calendar to avoid combined leverage loss.

Suggested reading

• Oracle Cloud Licensing Policy 2026. Cross vendor reading from the wider library.
• Oracle BYOL Comprehensive Guide. Cross vendor reading from the wider library.
• Oracle Cloud at Customer Licensing Guide. Cross vendor reading from the wider library.

What to do next

1. Inventory every Oracle workload across OCI, AWS, Azure and Google Cloud.
2. Map each workload to the licensing model and counting rule that applies.
3. Confirm the authorized cloud policy version cited in the contract.
4. Run a quarterly universal credit burn review against the term.
5. Build a written counting rule for every new cloud workload before deployment.
6. Pair cloud audit defense with the renewal calendar to preserve combined leverage.
7. Refresh the cloud baseline at every architectural change.

Frequently asked questions

Is OCI BYOL always cheaper than license included?

On Database service, materially yes. Confirm the conversion ratio in writing before assuming the saving.

Does AWS RDS for Oracle waive any license requirement?

No. AWS RDS for Oracle still requires BYOL or license included pricing. The platform packages the database but not the license cost.

What is the authorized cloud factor in 2026?

The current authorized cloud factor for AWS and Azure is two virtual CPU per per processor license. Check the policy version cited in your contract because previous versions used different ratios.

Do universal credits expire?

Universal credits expire at the end of the term unless the contract carries forward language. Negotiate carry forward at signature.

Is Google Cloud BYOL supported?

Limited. Google Cloud runs an Oracle partnership for hosted services. Bare Metal Solution carries separate counting rules from VM based BYOL.

Does the cloud policy version on the website apply to my contract?

Only if the contract cites the website version explicitly. Otherwise the version referenced in the schedule controls.

Are containers covered by the same rule?

Containers need a written counting rule per service. Treat each managed cloud database service separately.