Oracle pricing metrics, decoded. The CIO playbook on every license metric.

Oracle uses six pricing metrics across the catalog. Named User Plus, Processor, Employee, Application User, Custom Suite User, and Authorized User. Each metric carries a different sizing rule, audit posture, and renewal lever.

The wrong metric on the wrong product can move a contract by a factor of three to five on list price. The right metric tied to a documented sizing baseline drops the renewal bill by 20% to 40%.

Read this alongside the Oracle hub, the Oracle services page, the Oracle database licensing guide, the Oracle on VMware reference, the Java license calculator, and the Vendor Shield subscription.

The six core Oracle pricing metrics

The Oracle price list ships every product with one or more metrics. Choosing the right metric per product is the first move on every Oracle deal.

Oracle pricing metric catalog summary

Metric	Definition	Typical product	Audit risk
Named User Plus (NUP)	Each named individual or device with access	Database EE, Options, Packs	Minimums per processor
Processor	Cores times core factor	Database, WebLogic, Middleware	Virtualization and partitioning
Employee	All employees plus contractors	Java SE Universal Subscription	Headcount disclosure
Application User	Defined module user	Oracle Cloud Applications	Module level minimums
Custom Suite User	Named user with mixed modules	E Business Suite Custom Bundle	Suite definition drift
Authorized User	Each named individual	Oracle Cloud Infrastructure services	Service usage reporting

Named User Plus and the per processor minimum

Named User Plus is the most common Oracle Database metric. The metric counts every named individual or device authorized to access the database, not the concurrent user count.

The four Named User Plus sizing rules

1. Count every named user. Active, inactive, and indirect users all count if access is technically possible.
2. Count every device. Each non human accessor, including batch and integration endpoints.
3. Apply the per processor minimum. Database EE requires 25 NUP per processor. Standard Edition 2 requires 10 NUP per server.
4. Apply the per option minimum. Each option (Partitioning, RAC, Advanced Compression) carries its own NUP count separate from the base.

The Named User Plus trap on small estates

A two processor database server with 15 actual users still requires 50 NUP licenses on Enterprise Edition. The minimum overrides the actual count.

Processor metric and core factor

The processor metric counts cores, not sockets, and applies the Oracle Processor Core Factor Table.

Core factor for common chips in 2026

Chip family	Core factor	Notes
Intel Xeon (all current)	0.5	One processor license per two cores
AMD EPYC (all current)	0.5	Same Intel like factor
IBM Power9 and Power10	1.0	One processor license per core
SPARC M8 and S7	0.5 to 0.75	Varies by chip generation
Oracle Cloud (BYOL OCPU)	0.5 OCPU equivalent	Two OCPU per processor license
Authorized cloud (AWS and Azure)	0.5 vCPU when hyperthreaded	Two vCPU per processor

Employee metric and Java SE Universal Subscription

The Employee metric arrived in 2023 with the Java SE Universal Subscription and now defines the bill for every Oracle Java deal.

Three Employee metric rules every CIO should carry

• All employees count. FTE, part time, contractor, outsourced staff, and temporary agency workers.
• One employee one count. The metric is not per user of Java, it is the total enterprise headcount.
• Volume tiers. The list price tiers from 15 USD per employee per month at the smallest band down to under 6 USD at the largest band.

Employee metric worked example

A 25,000 employee enterprise running Java on 200 servers carries the Employee metric, not the legacy NUP metric. The annual list bill lands at roughly 12 USD per employee per month, or 3.6M USD per year before any discount.

Application user metrics across Oracle Cloud Applications

Oracle Cloud Applications ship module specific user metrics. Fusion ERP, HCM, EPM, and CX each ship their own metric variants.

The four most common Oracle application user metrics

1. Hosted Named User. Each individual authorized to use the cloud application.
2. Hosted Employee. All employees inside the enterprise, regardless of application use.
3. Hosted Order Lines. A metric for Order Management modules priced on document count.
4. Hosted Plan Item. A metric for Planning modules priced on planning records.

Worked example: metric choice on a mid sized estate

The math below uses a 4,000 employee manufacturer running Oracle Database EE on 16 cores, Java on 800 servers, and Oracle ERP Cloud on 600 users.

Two metric paths compared

Product	Metric path A	Metric path B	Annual list cost
Database EE	16 cores times 0.5 factor = 8 processor	200 Named User Plus	$380,000 vs $190,000
Java SE	Employee at 4,000 staff times $12	Legacy NUP not available 2026	$576,000 only path
ERP Cloud	600 Hosted Named User	Hosted Employee on 4,000 staff	$172,000 vs $290,000

Choosing Named User Plus over Processor on the database, and Hosted Named User over Hosted Employee on ERP Cloud, lands the annual bill at 938K USD against 1.25M USD on the alternative metric path. That is 25% off without any discount move.

Seven CIO moves on Oracle pricing metrics

The seven moves below are the buyer side checklist for every Oracle renewal cycle.

The seven moves in order

1. Document the metric per product. Pull every Oracle ordering document for the active metric on every line.
2. Validate the sizing baseline. Count actual cores, actual users, actual employees against the contracted entitlement.
3. Score the metric mismatch. Where Processor is contracted but NUP is cheaper, where Hosted Employee is contracted but Hosted Named User is cheaper.
4. Quote the metric swap. Oracle allows metric conversion at renewal under the right terms.
5. Lock the core factor. Document the chip family per server, the partitioning technology, and the hard partitioning posture.
6. Quote the Java employee shift. The Java SE Universal Subscription on Employee is mandatory in 2026, choose the right tier band.
7. Carry the metric position into the procurement memo. Document the position before the Oracle account team starts the renewal conversation.

What to do next

The seven step checklist takes an Oracle estate from a default metric posture to a documented, defensible position before the next renewal cycle.

1. Run the inventory. Every Oracle ordering document, every active metric, every product.
2. Run the audit baseline. Cores, users, employees, modules, options, packs.
3. Score the metric gap. The dollar value of every contracted metric versus the right metric.
4. Draft the swap quote. Metric conversion language for the renewal amendment.
5. Lock the Java posture. Employee count, tier band, FTE plus contractor coverage.
6. Brief the CFO. Position memo, dollar value, renewal timing.
7. Open the renewal. Eight months before the renewal date, not three.

Frequently asked questions

How Redress engages on Oracle pricing metric reviews

Redress runs Oracle metric advisory inside the Vendor Shield subscription, the Renewal Program, the Benchmark Program, and the Software Spend Assessment.

Read the related Oracle hub, the Oracle services page, the Oracle database licensing guide, the Oracle on VMware reference, the benchmarking page, the about us page, the locations page, and the contact page.