Oracle argues external partners, customers, and anonymous dashboard viewers into your licensable Named User Plus count unless the contract is structured to stop it. This guide shows where the counting rules break, what Processor and hosting metrics fix, and the exact terms to lock before you deploy a portal.
Oracle argues external partners, customers, and anonymous dashboard viewers into your licensable Named User Plus count unless the contract is structured to stop it. This guide shows where the counting rules break, what Processor and hosting metrics fix, and the exact terms to lock before you deploy a portal.
Named User Plus (NUP) is Oracle's per-person metric, and the word that costs you money is authorized. A NUP license is required for every individual authorized to access the software, not just those who actually log in. The metric does not measure usage, concurrent sessions, or frequency. If a person has the right to reach an OBIEE or Oracle Analytics Server (OAS) dashboard, they count, whether they open it daily or never.
That rule is survivable for internal deployments. A 50-person finance team on OBIEE has 50 countable, employed, badge-carrying humans. Extend the same dashboards to a partner extranet or a customer self-service portal and the model collapses. External customers are explicitly licensable individuals in Oracle's definitions: users can be employees, contractors, and customers who make use of the software directly or indirectly. When your portal serves 100,000 customers, Oracle's own logic says 100,000 NUP. The gap between the two scenarios is not incremental, it is catastrophic.
In the counting decision that governs most of this, see our detailed comparison of OBIEE Named User Plus versus Processor at scale. This page is narrower: it deals only with the populations Oracle argues in that you may believe are out of scope, and the contract structure that keeps them out.
NUP counts the right to access, not the act of accessing. For an external portal, that turns your customer list into your license count.
Buyers assume that an anonymous or shared login shields them. It does not. Oracle counts distinct individuals, not usernames. Ten people behind one generic account are ten Named Users, not one. The same logic drives the anonymous portal viewer straight into the licensable population.
The technical hook is the multiplexing definition in Oracle's own License Definitions. Where multiplexing hardware or software (a TP monitor or a web server product) sits between the human and the Oracle software, the user count must be measured at the multiplexing front end. Middleware does not compress the number. Multiplexing, where many users reach Oracle through a shared middleware connection, does not reduce licenses required. Automated batching of data machine-to-machine is permitted, but a human reading a dashboard through a web tier is not batching, it is access.
This is precisely where the anonymous viewer gets argued in. Oracle's NUP definition extends to indirect access: users who reach Oracle data through an intermediary application such as a BI tool. If the application connects on behalf of users without a separate multiplexing or hosting license, each end user still needs a NUP, or the deployment must be licensed by Processor. Service accounts pile on top. Batch jobs, integration accounts, monitoring tools, and system accounts each count as one NUP when they touch Oracle directly. In our audit-defense experience, undercounted service accounts and unaccounted anonymous viewers are the two findings that most often turn a routine review into a seven-figure claim.
| Scenario | Population Oracle counts | NUP list price at $2,000/user | Processor alternative |
|---|---|---|---|
| Internal BI team | 50 employees | $100,000 | Usually cheaper on NUP |
| Partner extranet | 5,000 partners | $10,000,000 | Processor almost always wins |
| Customer self-service portal | 100,000 customers | $200,000,000 | Processor mandatory in practice |
| Anonymous public dashboard | Unknown / uncountable | Not licensable by NUP | Processor is the only compliant path |
The $2,000 per NUP figure is 2026 OAS list. The point of the table is not the exact totals, it is the shape of the curve. Once the counted population passes the low hundreds, NUP stops being a metric and becomes a trap. Oracle knows this, and the sales conversation is engineered around it.
Processor licensing is Oracle's own recommended structure for uncountable populations, and it is worth saying plainly because sales teams rarely lead with it. It is recommended when BI is accessed by a large or unknown number of users, such as enterprise-wide dashboards or extranet scenarios. You license CPU cores after applying the core factor, and any number of users, internal or external, may then access the dashboards. An 8-core server at a 0.5 core factor equals 4 Processor licenses, and the user count becomes irrelevant.
OAS Processor list price in 2026 is $221,250 per Processor license, one of Oracle's most expensive middleware products. Support runs at 22% of net license price annually and is mandatory for updates and patches. The break-even, from our practice and consistent with published guidance, sits around 50 NUP to one Processor: historically, the cost of roughly 50 NUP licenses equals one Processor license. Above about 50 users per processor, Processor wins. For any external portal, you are far past that line on day one.
Processor licensing is not a concession Oracle grants you. It is the compliant metric for uncountable users, and you should demand it, not negotiate toward it.
Even if you stay on NUP for a modest external group, the floor bites. Oracle's NUP minimum for OBIEE and OAS is 10 Named User Plus per Processor license, applied regardless of actual usage. If OAS runs on a server Oracle counts as 2 processors, you owe at least 20 NUP whether 3 people or 3,000 use the system. For a small partner portal on a two-socket box, the floor alone can exceed the value of the deployment.
Choosing Processor solves the counting problem but opens a different one. Oracle's soft partitioning policy can explode the core count. An OAS VM allocated 4 vCPUs on a VMware host with 32 physical cores could, under Oracle's soft partitioning position, require licensing all 32 cores. At $221,250 per Processor after core factor, that is over $3.5 million at list for a deployment you sized for four cores.
The same virtualization exposure runs through the whole Oracle stack. If your OBIEE repository sits on Oracle Database, review our note on the restricted-use database under the OBIEE stack so you do not license the wrong tier twice.
Buying enough Processor licenses is not, by itself, a licence to host analytics for third parties. Standard Full-Use licenses do not cover third-party hosting. Oracle prohibits offering an Oracle-based solution as a hosted service to external customers under Full-Use without a separate agreement. Three structures matter, and choosing the wrong one is where large claims originate.
| Structure | When it fits | Cost position | Key trap |
|---|---|---|---|
| Full-Use + Processor | Internal enterprise dashboards, no external hosting | Highest, unlimited internal users | Does not permit third-party hosted access |
| Proprietary Application Hosting (PAH) | You host an Oracle-based solution as a service to external customers | Negotiated, controlled third-party terms | Must be a separate, explicit agreement |
| ASFU / ESL (via ISV/OEM) | Analytics embedded in a packaged vendor application | 40% to 70% less than Full-Use | Connecting a BI tool directly to the database is a violation |
Proprietary Application Hosting (PAH) is the correct instrument when you offer an Oracle-based solution as a hosted service to external customers, because it authorizes that third-party use under controlled terms. If your portal serves external parties and you are on Full-Use, you have a compliance gap regardless of how many Processor licenses you own.
Application Specific Full Use (ASFU) and Embedded Software License (ESL) come through Oracle partners and tie the software to one application. They cost 40% to 70% less than Full-Use, which makes them attractive for embedded analytics. The trap is specific and directly relevant here: connecting a business intelligence tool directly to the Oracle database is an ASFU violation. An OBIEE or OAS portal reaching around the packaged application into the database converts a cheap license into a breach. Read the boundary carefully in our coverage of BI Publisher's embedded-use limit, which draws the same line.
Before you accept any net-new quote for an external portal, check entitlement. In most cases, customers with current support on OBIEE have the right to run Oracle Analytics Server under the same entitlement, so net-new licenses are usually not required to migrate. When a rep quotes fresh OAS Processor licenses for a portal built on OBIEE metrics you already own, that is a quote to challenge, not to sign. Our OBIEE end-of-life migration analysis works the entitlement math in full.
Two scope-expansion traps sit near BI portals. First, if OBIEE or OAS connects to an Oracle Database with Diagnostics Pack or Tuning Pack enabled, even incidentally, an Oracle LMS audit can expand to include those database options. Audit database option status before disclosing any environment detail. Second, bundled option packs surface unexpectedly; see the BI Suite EE Plus option packs that appear in an audit. External portals draw attention because they generate the largest theoretical user counts, so they are prime audit targets.
Sequence matters. The cost of a portal is set at contract signature, not at go-live. Take these steps in order:
For the wider stack economics behind these choices, the Oracle BI and analytics on-premise licensing guide maps how the option packs and metrics compound. The external-user problem is severe, but it is solvable: the leverage is entirely in the metric and the contract structure, and both are decided before the first external user ever logs in.
Under Named User Plus, yes, because Oracle counts distinct individuals reaching the software indirectly, not login usernames. Since anonymous viewers cannot be counted, the only compliant path for anonymous or public dashboards is Processor licensing, which permits unlimited users. Deploying anonymous access on NUP is a compliance gap Oracle will find in an audit.
Technically Oracle's definition allows it, but it is almost never viable because external customers are not readily countable and may number in the thousands or hundreds of thousands. At $2,000 per NUP, a 100,000-customer portal implies a $200M obligation. Processor licensing, sized to your cores, is the intended and only practical structure for external populations.
No. Oracle prohibits third-party hosting under standard Full-Use licenses regardless of how many Processor licenses you hold. Offering an Oracle-based analytics service to external customers requires a separate Proprietary Application Hosting (PAH) agreement with controlled terms. Confirm this instrument before you expose any dashboard to external parties.
None. Oracle's License Definitions require the user count to be measured at the multiplexing front end, and multiplexing does not reduce the number of licenses required. A web tier or middleware layer between users and Oracle does not compress the count. Only Processor licensing removes the per-user obligation.
Usually not. In most cases, customers with current support on OBIEE have the right to run Oracle Analytics Server under the same entitlement, so net-new licenses are generally not required to migrate. Challenge any fresh OAS quote against the entitlements you already own before signing.
Oracle requires a minimum of 10 Named User Plus per Processor license, applied regardless of actual usage. If OAS runs on a server Oracle counts as two processors, you owe at least 20 NUP even if only a handful of people use it. For external portals this floor is another reason to move to Processor licensing.
Siebel is licensed on authorization across several user metrics, grants access through responsibilities and custom views, and sits under Oracle lifetime support. The traps and the
Gated with a work email on the download page. No sales follow up you did not ask for.
Get the White Paper →
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One buyer side briefing a week. Renewal signals, audit moves, and the levers that work. No vendor spin.
