Oracle Named User Plus is the alternative to Processor licensing for Oracle Database — and Oracle's sales teams will present it as the "cheaper" option when it benefits Oracle's position. In low-user environments, NUP genuinely is cheaper. But Oracle's indirect access rules mean that any user of any application that retrieves data from Oracle — even through middleware, APIs, or integration platforms — may need to be counted as a Named User Plus. A 50-person internal team accessing Oracle directly might have a legitimate 50-NUP license at $47,500. A web application backed by the same Oracle database serving 100,000 external customers requires 100,000 NUP licenses — at $95M. This guide explains exactly how the NUP metric works, where the traps are, and how to optimize your position.
Oracle Named User Plus (NUP) is a licensing metric that grants a specific, identified individual (or device) the right to access Oracle software — in contrast to the Processor metric, which licenses the hardware on which Oracle runs. One NUP license covers one person who accesses Oracle, either directly or indirectly.
"Named" is important: Oracle NUP licenses are not concurrent user licenses. You cannot have 100 NUP licenses shared by a population of 200 people who access the system at different times, on the basis that only 100 are concurrent at any given moment. Oracle NUP requires a count of all authorized users — everyone who is entitled to access the system, regardless of when they actually do so. A user who accesses the database once per month still requires a NUP license.
The "Plus" in Named User Plus distinguishes it from Oracle's older Named User metric, which was more restrictive. NUP includes the right to access by named users or devices and covers both direct and indirect access scenarios. NUP is available for Oracle Database EE ($950 list), Oracle Database SE2 ($350 list), and various Oracle middleware products at different price points.
Oracle imposes a minimum NUP count per processor for most products. For Oracle Database Enterprise Edition, the minimum is 25 Named User Plus licenses per processor license that would be required under the Processor metric. This floor is designed to prevent organizations from using NUP as a cheap alternative to Processor in very low-user environments.
The minimum floor creates an important dynamic: even if your actual user count is only 10 people, you still need 800 NUP licenses on this server configuration. If your actual user count is 10, paying for 800 NUP at $760,000 is still cheaper than the $1.52M Processor cost — but you are paying for 790 licenses you are not using. This is a situation worth identifying and potentially addressing through hardware right-sizing or application consolidation.
For Oracle Database SE2, the NUP minimum is 10 users per processor. At $350 per NUP and $17,500 per processor, the economics work differently — see the SE2 section below.
Oracle's indirect access rules are the most commercially aggressive element of the NUP metric — and the source of the majority of large NUP-related audit claims. Indirect access is defined as any situation where a user or device accesses Oracle software through an intermediary layer: a web application, middleware, API gateway, integration platform, or any other system that queries Oracle on the user's behalf.
Oracle's licensing policy is explicit: if a user of a front-end application retrieves data that originates from an Oracle Database — even if that user never directly queries Oracle, never sees a SQL prompt, and has no knowledge that Oracle exists in the stack — that user requires a NUP license for the Oracle Database that stores the data.
The E-Commerce Database Trap: An organization runs Oracle Database EE on a server with 16 processor licenses. Their internal team of 200 employees accesses Oracle directly — they have 200 NUP licenses, well above the 400 NUP minimum floor (16 × 25). However, their customer-facing e-commerce platform also retrieves product, order, and inventory data from the same Oracle Database. The e-commerce platform serves 500,000 registered customers. Oracle's position: all 500,000 customers require NUP licenses — adding $475M to the license requirement. This scenario is not hypothetical. Oracle has pursued and settled indirect access claims of this scale.
Oracle's indirect access policy requires that any user who accesses Oracle data through a non-Oracle system counts as a NUP. The critical test is not whether the user knows Oracle is involved — it is whether they receive data that originated in Oracle. The chain can be long: User → Frontend App → REST API → Middleware → Oracle Database. Every user of the frontend app counts.
The only defences against indirect access claims are: (a) the intermediary system is itself licensed under an Oracle Application User or equivalent metric that specifically covers indirect access (some Oracle Applications EBS, PeopleSoft, and Fusion Cloud licenses include indirect access for their users); (b) a specific contractual carve-out exists; or (c) you can demonstrate that the data returned to the user does not originate from Oracle. Our Oracle Audit and Indirect Licensing guide covers this in detail, and our compliance review service maps every data flow in your environment to identify indirect access exposure before Oracle does.
Our compliance review maps every application that touches Oracle Database data — directly or indirectly — and quantifies the NUP exposure Oracle would claim in an audit. Most enterprises with web-facing applications have unmapped indirect access risk.
Oracle NUP has an alternative counting basis for device-heavy environments. Where it is impractical to count individual users — for example, a kiosk, point-of-sale terminal, automated machine, or shared workstation — Oracle allows a device to be licensed as one NUP. One device = one NUP license, regardless of how many people use that device.
Device licensing is commercially attractive in scenarios like retail point-of-sale (100 terminals serve thousands of customers — 100 NUP vs potentially thousands), factory-floor terminals (shared among shift workers), and shared workstations in healthcare environments. However, device licensing requires that the device itself is fixed and identifiable, and that access to Oracle occurs only through that device. Oracle auditors scrutinise device claims carefully to ensure devices are not being used to circumvent proper user counting in disguised circumstances.
The decision between NUP and Processor should be driven by a formal cost model that accounts for both current and projected user counts, indirect access risk, hardware configuration, and the 25-user minimum. The following framework applies to Oracle Database EE.
The crossover formula is: NUP is cheaper when (actual NUP count × $950) < (processor count × $47,500). The processor count is physical cores × Core Factor. The NUP count must include all direct and indirect users, subject to the minimum floor.
The critical caveat: this calculation assumes the NUP count is limited to direct users. If indirect access applies and pulls in thousands of external users, the NUP count can multiply by orders of magnitude, making Processor licensing dramatically cheaper. The right answer depends on a complete and accurate count of all authorized users and devices — including indirect access paths. See our detailed NUP vs Processor comparison guide for extended worked examples.
NUP audits follow a different methodology from Processor audits. Rather than querying hardware inventories, Oracle's LMS team requests user access reports, HR records, system user counts, and application architecture diagrams. The audit scope includes both the Oracle database layer and the application layer — specifically looking for non-Oracle systems that query Oracle data.
LMS auditors ask specific questions designed to identify indirect access: What applications connect to this Oracle Database? What external systems send queries to Oracle? What APIs expose Oracle data to external users? Each affirmative answer triggers a further investigation into user counts for that application. The audit process frequently uncovers NUP shortfalls in organizations that believed they were compliant because they counted only their direct Oracle users.
Preparation for NUP audits requires a complete application inventory, data flow mapping, and a defensible user count methodology. Our audit defense service has successfully challenged NUP claims by demonstrating that application users accessing Oracle data through licensed Oracle Applications were already covered by the application metric — eliminating the need for separate NUP licenses for those users.
Oracle Standard Edition 2 can be licensed under NUP at $350 per Named User Plus (versus $950 for EE). The minimum for SE2 NUP is 10 users per processor — lower than EE's 25-user minimum. SE2 is limited to 2-socket servers, and the SE2 NUP metric applies the same indirect access rules as EE NUP.
For organizations that qualify for SE2 (workloads not requiring EE-exclusive features), SE2 NUP can be the lowest-cost Oracle Database licensing option. A 2-socket 16-core server (8 processor licenses at 0.5 Core Factor) requires a minimum of 80 NUP (8 × 10) at $350 = $28,000 — compared to $140,000 for the Processor equivalent. That is an 80% reduction versus SE2 Processor, and a 98% reduction versus EE Processor. The trade-off is the SE2 hardware cap and feature set limitations, which must be evaluated against the workload requirements.
Our license optimization service assesses whether your Oracle Database deployments qualify for SE2, models the NUP savings, and manages the migration planning — including EE option analysis and architectural validation.
Reducing NUP license costs and compliance exposure requires a structured approach to user counting, access control, and application architecture. The following strategies are the most effective across enterprise Oracle Database environments.
The most immediate NUP cost reduction comes from removing stale user accounts from Oracle access control lists. Former employees, contractors, and users who moved to different roles are frequently left with Oracle access entitlements that require them to be counted as NUP. A quarterly access review that deactivates unused accounts directly reduces your NUP count — and therefore your license requirement. Oracle NUP licenses can only be reduced at contract renewal (not mid-term), but demonstrating a reduced user count at renewal provides the justification for a lower renewal quantity.
If the same Oracle Database serves both a small internal user population (eligible for NUP at 50 users) and an external-facing application (triggering indirect access for 500,000 customers), separating the workloads onto separate Oracle instances allows each to be licensed appropriately. The internal instance is licensed at 50 NUP; the external instance may need to be migrated to a different database technology, or the application metric may apply if it is an Oracle Application. This architectural separation is a legitimate and common compliance remedy.
Oracle's Applications licenses (EBS, PeopleSoft, JD Edwards, Siebel, Fusion Cloud) include specific user metrics that cover access to Oracle Database by application users. If your external user exposure is through a licensed Oracle Application, the application's user metric may already cover the indirect access to the underlying Oracle Database. Confirming this coverage eliminates the NUP requirement for those users. Our compliance review service validates which application metrics cover which database access patterns.
NUP counts in Enterprise Agreements are negotiated at renewal. Bringing an evidence-based, independently validated user count analysis to the renewal table — with deprovisioning documented, indirect access scope defined, and application metric coverage confirmed — creates a defensible basis for a lower NUP quantity than Oracle's assumed count. Our contract negotiation service has consistently achieved 15–40% NUP count reductions against Oracle's initial renewal proposals.
Weekly briefings on Oracle pricing changes, audit trends, and cost reduction tactics — from former Oracle insiders.
Our compliance review maps every user, every device, and every indirect access path to Oracle Database — and gives you a defensible NUP count before any audit arrives.
Free Research
Download our Oracle JD Edwards Licensing Guide — expert analysis from former Oracle insiders, 100% buyer-side.
Download the JDE Licensing Guide →