What is Named User Plus?
Named User Plus is an Oracle license metric that counts the individuals and devices authorised to use a program, and it is counted as the higher of your actual named users and a per processor minimum. The metric is designed for environments where the user population is known and bounded, such as an internal database with a defined set of staff. It is the main alternative to the Processor metric, which counts the hardware rather than the people. The two produce very different numbers from the same server, which is why getting the count right starts with understanding how Named User Plus is actually measured.
The phrase that trips people up is the minimum. Named User Plus is never simply a headcount of users. It is the larger of two figures: the real number of named users with access, and a minimum number of licenses required per processor. Counting only the users, and ignoring the minimum, is the mistake that produces a classic audit finding.
How do the per processor minimums work?
The per processor minimums require a set number of Named User Plus licenses for each processor, calculated after the core factor is applied, so the minimum scales with the hardware even when the user count is small. If a server carries a Named User Plus minimum and your actual users fall below it, you must still license up to the minimum. On a powerful server with few users, the minimum, not the headcount, sets the license requirement. This is precisely where undercounting happens: an organisation licenses the users it can see and overlooks the floor the hardware imposes.
Named User Plus is the higher of real users and the per processor minimum. License the larger number. The minimum is calculated after the core factor, so the hardware sets a floor the user count cannot fall below.
| Input | What it contributes |
|---|---|
| Actual named users | Every individual or device authorised to access the program |
| Processor count after core factor | Sets the per processor minimum to apply |
| Per processor minimum | The floor the licensed quantity cannot fall below |
| Required licenses | The higher of the user count and the minimum |
Who counts as a named user?
A named user is any individual authorised to use the program and any non human operated device that does so, which means the count can be wider than the list of human logins. Batch accounts, service accounts that represent people, and devices that feed the database can all fall within the definition, and an audit will read the definition broadly. The buyer side discipline is to count honestly but precisely: include everyone and everything the contract requires, but do not let the definition be stretched past what your agreement actually says. The contract governs the definition, and the policy document is not the contract.
Should you license by Named User Plus or Processor?
The choice between Named User Plus and Processor depends on your user population measured against the minimums, and it is contract dependent rather than universal. Named User Plus tends to suit low, bounded user counts on modest hardware, where the headcount comfortably exceeds the minimum and the metric is cheaper than licensing every processor. Processor tends to suit high or public facing populations, where users are too many to count or unbounded, so paying for the hardware is simpler and often cheaper. Modelling both before an audit, server by server, tells you which metric each environment should sit on and whether your current licensing matches.
What is the buyer move?
The buyer move is to count Named User Plus as the higher of real users and the per processor minimum on every server, then model whether Named User Plus or Processor is the right metric for each environment. Build an honest user count to the contract definition, apply the correct core factor, derive the minimum, and license the larger figure. Where the minimum dominates a low user environment on heavy hardware, consider whether Processor would be cheaper or whether the hardware should be resized. Getting this right before an audit removes a classic finding entirely, and where a finding has already landed, correcting the metric and the minimum is part of the line by line review that typically cuts the claim 60 to 80 percent. For the wider context, read the core factor table explained and the Oracle database licensing guide.
If you are unsure whether your Named User Plus counts clear the minimums, a buyer side review will model it server by server. We reduce your Oracle exposure or we reimburse our service fee, on a Fixed Fee or Gainshare basis with no risk to you.
FAQ
How is Named User Plus counted? As the higher of the actual named users with access and the per processor minimum for that product. You license whichever number is larger, which is why minimums drive the count.
What is the Named User Plus minimum? A required number of Named User Plus licenses per processor, applied after the core factor. Undercounting against these minimums is one of the classic Oracle audit findings.
Should I license by NUP or Processor? It depends on user count against the minimums. Named User Plus suits low user counts, Processor suits high or public facing populations, and the right choice is contract dependent and worth modelling before an audit.