Every Oracle license is two decisions, and most buyers made only one
An Oracle license type is two decisions, not one: the metric sets the quantity you buy, and the grant sets what you are allowed to do with it, printed beside each program on the ordering document in two or three words that change the value of the license by an order of magnitude. Most buyers can quote their metric and have never read their grant, and across our reviews the metric was almost always picked years before the invoice that exposed it, by someone who had left.
Prepared by Redress Compliance · August 8, 2026 · Oracle advisory. Based on 30 to 40 Oracle license and metric reviews run 2024 to 2025.
Executive summary
Two numbers decide the metric, and both are arithmetic.
Enterprise Edition lists at $47,500 per Processor and $950 per Named User Plus, so the breakeven sits at 50 users per Processor.
And the NUP floor is 25 per Processor on EE and 10 per server on SE2, with Oracle licensing the higher of the real count or the floor: the floor applies after the core factor, a 32 core x86 server being 16 Processor licenses and therefore a 400 user floor, not 800.
Estates on Named User Plus with growing populations overpaid 20 to 50 percent against a Processor fit, because the metric picked at 30 users per Processor was never revisited at 80.
The grant taxonomy runs from Full Use to embedded, and the discounts price the restrictions.
Full Use permits any internal application at full list; ASFU restricts to one named third party application at a material discount; the Embedded Software License buries the database inside a partner product at the lowest price.
Proprietary Application Hosting adds the right to host your own application for third parties; developer licenses are free and audited anyway.
And term licenses price time at roughly 20 percent of perpetual for one year and 70 for five, against perpetual plus five years of support at about 210 percent that never expires, an arithmetic comparison run across the workload's life, not the budget year.
The grant breach is the audit finding, and ASFU breaks in three shapes.
A second reader appears, a reporting tool or warehouse extract pointing at the ASFU schema; the application is replaced, the ISV product retired while the database runs under a new front end.
Or custom tables arrive for convenience: each breaches the restriction the day it happens, priced as the gap up to full use, and changing grant afterward costs the difference between list positions applied to the current quantity with the support base moving up permanently.
The most expensive routine transaction in the Oracle catalogue.
The Enterprise metrics price the business, and your own database can prove the count.
Eight Enterprise metrics in Oracle's License Definitions and Rules price applications off revenue, cost of goods sold, employees, budget, and freight rather than usage, moving with the business and never with the deployment.
The counting defense is native, V$LICENSE and the LICENSE_MAX_USERS parameter letting your own database tell you the count before Oracle does.
And BYOL keeps the metric while changing the conversion, two vCPUs with multithreading equaling one Processor in authorized cloud, with eligibility misjudged in a third of cloud moves because support had lapsed on the owned licenses.
The grant taxonomy, widest to narrowest
| Grant | What it permits | Price position |
|---|---|---|
| Full Use | Any application, any internal purpose | Full list, the reference point |
| Application Specific Full Use | Only the one named third party application | Materially below list |
| Embedded Software License | Inside a partner product, invisible to users | The lowest, priced into the product |
| Proprietary Application Hosting | Hosting your own application for third parties | Full use plus the hosting right |
| Term license | Full rights for one to five years | About 20 to 70 percent of perpetual by length |
| ULA and PULA | Unlimited deployment inside the named scope | Negotiated; no list price exists |
The grant is on paper, and only on paper.
It is not visible in the database and not in your CMDB: it sits in the ordering document's description line, the license schedule attached to the support renewal.
And the definitions the contract incorporates, which is why estates that never pulled the paper run ASFU databases as if they were Full Use until the audit prices the difference.
Plan the grant at purchase, because changing it afterward is priced as the full gap between list positions with the support base repricing permanently.
The metric arithmetic, floors and breakevens
- The breakeven: $47,500 over $950 is 50 users per Processor, below it NUP wins, above it Processor does, and the crossing population is the review trigger nobody sets.
- The floor after the factor: 25 NUP per Processor applied to post factor Processors, so the 32 core x86 server floors at 400 users, and misreading this doubles small estates.
- The term comparison: five years at 70 percent of perpetual against perpetual plus support at 210 percent that never expires, compared across the workload's life.
- The BYOL conversion: the metric survives the cloud move at two vCPUs per Processor with multithreading, and lapsed support voids the eligibility a third of moves assumed.
- The native count: V$LICENSE and LICENSE_MAX_USERS report the sessions and configured maximums your own estate can defend before any script runs.
The NUP versus Processor brief
The breakeven arithmetic, the floor mechanics, the grant taxonomy, and the metric selection method worked end to end.
Get the white paper →The Enterprise metrics, pricing the business
The eight Enterprise metrics named in Oracle's License Definitions and Rules price applications off the business rather than the deployment, revenue, cost of goods sold, employees, operating budget, and freight among them, which means the bill moves with acquisitions, growth.
And reorganizations while never responding to usage: the metric definition is the entire negotiation, exactly as the Java per employee metric demonstrated at scale, and the counted population defends against the definition's own words.
The restricted grants each carry their own deep file, the ASFU guide for the named application restriction, the ESL guide for the embedded boundary where one connection voids the discount, and the ULA lifecycle for the unlimited scope.
The metric orientation across the whole estate runs in the Oracle licensing guide, and the cloud conversion rules in the Oracle on Azure analysis.
- 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 metric reviews, 2024 to 2025
Across the 30 to 40 Oracle license reviews Fredrik Filipsson ran in 2024 and 2025, the metric was almost always picked years before the invoice that exposed it, by someone who had left:
On estates whose populations grew past the breakeven nobody was watching.
Recovering far less value than expected where scope had drifted during the term.
The review discipline the file argues for is periodic re measurement of a decision everyone treats as permanent: the population against the 50 user breakeven annually, the grant against the actual usage before any audit reads it, the ASFU schemas swept for second readers and custom tables.
And the BYOL eligibility confirmed against live support before any cloud move relies on it.
The license type is two decisions, and the estates that revisit both on a calendar hold defensible positions, while the estates that inherited them from a departed decision maker discover the mismatch at the invoice, which is always the most expensive place to learn it.
Your first five moves
- Pull the grant from the ordering document for every program, the two or three words most buyers never read.
- Check every NUP population against the 50 user breakeven, where growing estates overpaid 20 to 50 percent.
- Apply the floor after the core factor, the 400 against 800 user difference on a 32 core box.
- Sweep the ASFU schemas for second readers and custom tables, the breaches that price at the full gap.
- Confirm live support before any BYOL move, the eligibility a third of migrations assumed wrongly. The Oracle practice runs the review with you.
Frequently asked questions
What are the Oracle license types?
Two dimensions: the metric setting the quantity, Processor or Named User Plus for technology and eight Enterprise metrics for applications, and the grant setting the permitted use, from Full Use through ASFU, the Embedded Software License, Proprietary Application Hosting, developer, term, perpetual.
And the unlimited ULA and PULA constructs.
The grant is printed beside each program on the ordering document, and it changes the license's value by an order of magnitude.
When does Named User Plus beat Processor licensing?
Below 50 users per Processor: Enterprise Edition lists at $47,500 per Processor and $950 per NUP, making the breakeven arithmetic exact, with the floor of 25 NUP per Processor applied after the core factor, so a 32 core x86 server at 16 Processors floors at 400 users.
Estates whose populations grew past the breakeven without a review overpaid 20 to 50 percent against a Processor fit.
What is an Oracle ASFU license?
Application Specific Full Use: a discounted full use license restricted to one named third party application, the cheapest legitimate way to run Oracle Database under an ISV product, and the most common source of a compliance finding.
The three breach shapes are a second reader pointing at the schema, the named application being replaced while the database runs on, and custom tables arriving for convenience, each priced as the gap up to full use.
Are Oracle term licenses worth it?
Only for genuinely short lived workloads: term pricing has run around 20 percent of perpetual list for one year and 70 percent for five, while perpetual plus five years of support at 22 percent costs about 210 percent of list and never expires.
The comparison runs across the life of the workload rather than the budget year, and the five year term that renews once has already lost the arithmetic.
How does Oracle BYOL work in the cloud?
The metric survives and the conversion changes: in authorized cloud environments, two vCPUs with multithreading enabled equal one Processor license, with the core factor table excluded.
The eligibility condition is active support on the owned licenses, and it was misjudged in close to a third of cloud moves we reviewed because support had lapsed, voiding the BYOL position the migration assumed.
How do you verify an Oracle user count?
From your own database before Oracle asks: V$LICENSE reports session high water marks and the LICENSE_MAX_USERS parameter carries the configured maximum, giving the estate a native count to defend against the floor and breakeven arithmetic.
The count pairs with the grant check, because the same review that measures the population should read the two or three words on the ordering document that most buyers never have.
