Oracle prices the same software through several metrics. Named User Plus, Processor, Application User, and the ULA each carry a different risk and a different defense. Pick the wrong one and you overpay for years.
Oracle prices the same software through several metrics, each with its own risk and defense. This guide covers Named User Plus, Processor, Application User, Enterprise Metrics, BYOL, and the ULA for the buyer side.
User based metrics count people and devices. They fit workloads with a known, contained user population.
The primary user metric is Named User Plus. Oracle sets the definitions and minimums in the technology price list and the wider pricing guidance.
Processor licensing counts hardware, not people. It fits large or unknown user populations where counting users is impractical.
The processor count is physical cores multiplied by the core factor, rounded up. Virtualization scope is governed by the partitioning policy.
Oracle license metrics at a glance
| Metric | Counts | Best fit |
|---|---|---|
| Named User Plus | Individuals and devices | Small, known populations |
| Processor | Cores times core factor | Large or unknown users |
| Application User | Module users | Defined application groups |
| Enterprise Metric | Business measure | Whole enterprise apps |
| ULA | Unlimited for a term | High growth deployments |
Beyond per unit metrics, Oracle offers agreement structures that change how licenses are consumed and counted.
BYOL carries owned licenses into authorized cloud environments, set out in the Oracle cloud licensing policy. A ULA grants unlimited deployment of named products for a fixed term, ending in a certification that converts usage into perpetual licenses.
White Paper ยท Oracle
The Oracle Buyer Side Framework
The moves we use across Oracle Database, Java and ULA estates. Read it free.
The common advice is to standardize on Processor licensing because it removes user counting and audit headaches. We disagree. In the reviews we have run, Processor licensing on a workload with a small, stable user base meant the buyer paid for cores that served a handful of people, often double what Named User Plus would have cost. The buyer side move is to fit the metric to the workload, not to a blanket policy. Use Named User Plus where the population is known and contained, Processor where it is large or unknown, and never let convenience pick the most expensive metric by default.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Oracle sells metrics, not software. The buyer who fits the metric to the workload controls the bill. The buyer who defaults to convenience pays Oracle to choose.
The choice is a fit decision per workload. Three questions settle most cases.
The core metrics are Named User Plus, Processor, Application User, Enterprise Metrics, and the Unlimited License Agreement. BYOL is an agreement structure that carries owned licenses into authorized cloud environments at a reduced rate.
Named User Plus counts each individual or device authorized to use the software, with a minimum number of users required per processor. It fits workloads with a small, known, and contained user population.
Processor licensing fits large or unknown user populations where counting users is impractical. The count is physical cores multiplied by the core factor, rounded up, with virtualization scope set by the partitioning policy.
A Unlimited License Agreement grants unlimited deployment of named Oracle products for a fixed term. At the end, a certification counts deployed usage and converts it into perpetual licenses, so the certification position matters from day one.
Bring Your Own License lets you carry owned Oracle licenses into authorized cloud environments and pay a reduced infrastructure rate. The owned license must stay on active support to remain eligible.
No. A blanket policy can put small, stable workloads on Processor licensing, paying for cores that serve few users. Fit the metric to each workload rather than defaulting to one for convenience.
In the reviews we ran, estates on the wrong metric overpaid by 20 to 50 percent. The same Oracle product can cost roughly twice as much under an ill fitting metric, so the choice outranks the discount.
Profile each workload by user population, scale, and growth. Known and contained favors Named User Plus, large or unknown favors Processor, and rapid growth may favor a ULA with a modeled exit plan.
Oracle ULA exit moves, Java audit defense posture, certification framework, and the buyer side moves across the Oracle Database, Java, and EBS estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
Engage independent buyer side Oracle licensing experts. We do not resell. We do not implement. We sit on your side of the table.
See engagement scope, comparison vs Big4 and resellers, and the buyer side framework.
Visit page →Oracle does not sell software, it sells metrics. The buyer who understands which metric fits which workload controls the bill. The buyer who lets Oracle choose pays for the metric that suits Oracle.
