Oracle license types, explained.

Oracle sells software on seven core license metrics. Each metric carries a distinct math, a distinct audit posture, and a distinct cost trajectory. A buyer who reads the contract on metric alone misses two thirds of the licensing risk. The metric is the start of the conversation, not the end.

This article reads as a buyer side reference. Use it with the Oracle practice, the ULA decision framework, the Java audit guide, the Oracle Database 23ai guide, and the Database licensing calculator.

Why metrics matter

The metric on the Oracle ordering document determines three things. The audit count math. The contractual right to deploy. The renewal envelope. Two contracts at the same headline price can carry different cost trajectories on the same workload because the metric differs.

Three reasons the metric is the contract

• Audit count. Oracle counts the deployed footprint against the metric on the ordering document.
• Right to deploy. The metric defines where and how the software can run.
• Renewal envelope. The metric carries the price uplift mechanism at renewal.

Processor licensing

The Processor metric counts physical CPU cores in the deployed footprint multiplied by the Oracle Core Factor Table value for the chip family. The metric is unrestricted on user count. The math is unrestricted on session count. The metric scales with the silicon, not the user base.

The Oracle Core Factor Table

Oracle publishes a Core Factor Table. The table maps chip families to a multiplier. Intel x86 sits at 0.5. AMD x86 sits at 0.5. SPARC sits at 0.25 to 0.75 depending on chip. IBM Power sits at 1.0. The multiplier changes the Processor count meaningfully.

When Processor wins

• Large user populations. Web facing or B2C systems.
• Internet facing systems. Where the user count is uncountable.
• High concurrency workloads. Where Named User Plus minimums lose.

Named User Plus licensing

The Named User Plus metric counts named individuals plus non human operated devices that access the software. The metric carries a minimum per processor. The minimum varies by Oracle product. Database Enterprise Edition carries 25 Named User Plus minimum per Processor.

When Named User Plus wins

• Small user populations. Internal users on heavyweight infrastructure.
• Development environments. Where the per Processor minimum is acceptable.
• Specialty workloads. Where the named user count is well below the per Processor scaling.

Application licensing

The Oracle applications layer uses different metrics. The Application User metric counts authorized users. The Enterprise Metric counts the enterprise size by revenue, employee count, or transaction volume. The metric varies by product line and by historical contract.

The main application metrics

• Application User. Per named user. The most common metric on E Business Suite, JD Edwards, PeopleSoft.
• Enterprise Employee. Per full time equivalent employee at the enterprise.
• Hosted Named User. The cloud applications equivalent of Application User.
• Custom Application User. A product specific variant on the user metric.

Cloud and BYOL

The Oracle Authorized Cloud Environment construct allows Oracle licenses to run on AWS, Azure, and Google Cloud. The counting rules differ by cloud. Oracle Cloud Infrastructure carries its own counting model. The BYOL model translates Processor and Named User Plus licenses into cloud deployments.

Cloud counting rules at a glance

Cloud	Counting unit	Conversion rule
AWS EC2	vCPU	Two vCPUs equal one Oracle Processor on hyper threaded x86
Microsoft Azure	vCPU	Two vCPUs equal one Oracle Processor on hyper threaded x86
Google Cloud	vCPU	Two vCPUs equal one Oracle Processor on hyper threaded x86
Oracle Cloud Infrastructure	OCPU	One OCPU equals one Oracle Processor regardless of chip family

Enterprise Metric licensing

Enterprise Metrics count the size of the enterprise rather than the deployed footprint. The most common Enterprise Metrics are Enterprise Employee, Enterprise Revenue, Enterprise Customer, and Enterprise Transaction. The metric is set at the time of contract and audited against the current enterprise scale.

When Enterprise Metrics fit

• Wide deployment. Software in use across the entire enterprise.
• Predictable scale. Stable employee count, revenue, or transaction volume.
• Avoid the count cycle. No need to count users or processors annually.

The Unlimited License Agreement

The Unlimited License Agreement is a fixed fee contract for unlimited deployment of a defined product set over a fixed term, usually three years. The certification at the end of the term converts the unlimited right into a fixed Processor or Named User Plus count for ongoing support.

The four ULA decision points

1. Product scope. What is in the ULA and what is excluded.
2. Term length. Three years is standard, five years is possible.
3. Certification math. The deployment at the certification date sets the ongoing count.
4. Renewal posture. Renew the ULA, certify out, or migrate to OCI under BYOL.

Metric mapping table

The table below maps each Oracle license metric to the main use cases, the audit posture, and the typical renewal trajectory. Read it before committing to any new Oracle order.

Oracle license metric mapping 2026

Metric	Best fit	Audit posture	Renewal trajectory
Processor	Large or uncountable user populations	Core counting and Core Factor disputes	3 to 5% annual uplift
Named User Plus	Small user populations on heavyweight infrastructure	User counting and per Processor minimum	3 to 5% annual uplift
Application User	Oracle applications named users	Role and user count	4 to 6% annual uplift
Enterprise Metric	Wide enterprise deployment	Enterprise size verification	4 to 8% with size adjustment
Authorized Cloud Environment	BYOL to AWS, Azure, GCP	vCPU counting under hyper threading	Linked to underlying on premises support
ULA	Fast growth or estate consolidation	Deployment scope at certification	Renewal or certify out decision

What to do next

The eight step checklist below moves an Oracle estate from a metric mismatch to a defensible license position. Open it before any new Oracle order or any renewal.

1. Pull the deployment inventory. By product, by environment, by core count.
2. Map each product to its current metric. Read the ordering documents end to end.
3. Compute the per Processor minimums. Especially on Named User Plus.
4. Verify the core factor on each chip family. Read the current Oracle Core Factor Table.
5. Score the metric fit. Tag each product as right metric, wrong metric, switch candidate.
6. Build the metric switch case. Where the wrong metric carries audit risk or cost uplift.
7. Run the BYOL math. Where cloud deployment is in plan.
8. Open the renewal 12 months out. Metric switches need calendar time.

Related advisory: Oracle audit defense services, Oracle negotiation and advisory, and how to reduce Oracle licensing costs before renewal.

Frequently asked questions

How Redress engages on Oracle license metrics

Redress runs the Oracle metric assessment as a three to four week workstream. The work pulls the deployment inventory, reads every ordering document, computes the per Processor minimums and Core Factor values, and lands the metric fit recommendation across the Oracle estate.

Read the related Vendor Shield, the Renewal Program, the Benchmark Program, the Software Spend Assessment, the Benchmarking framework, the about us page, the management team page, the locations page, and the contact page.