The metric you pick sets the size of the bill and the shape of your audit exposure for the life of the deployment. This guide gives you the per-processor minimums, the crossover math, and the specific triggers that take the choice out of your hands.
The metric you pick sets the size of the bill and the shape of your audit exposure for the life of the deployment. This guide gives you the per-processor minimums, the crossover math, and the specific triggers that take the choice out of your hands.
Oracle sells the OBIEE stack (and its on-premises successor, Oracle Analytics Server) on two metrics: Named User Plus (NUP) and Processor. They are not interchangeable pricing lines with the same outcome. One counts every human and non-human interface that can reach the analytics tier. The other counts silicon after a core-factor multiplier. Choose wrong and you either overpay by six figures at renewal or you sign up for an open-ended compliance liability that surfaces in an audit two years later. This page gives you the numbers to make the call, sourced to Oracle price lists and Oracle's own license definitions where possible, and flagged as market experience where it is not.
Named User Plus is a per-person and per-device count. You license one NUP for every unique individual and every non-human device or interface authorized to access the program, whether or not they log in during any given month. Processor licensing counts the physical cores of every server the software runs on, multiplied by Oracle's published core factor. For Intel and AMD x86 hardware, which covers the overwhelming majority of enterprise OBIEE deployments, the core factor is 0.5. So a 20-core Intel socket requires 10 Processor licenses (20 cores x 0.5). Get the chip model exactly right, because the factor is published per exact processor family and Oracle will use the correct one, not a convenient one.
The two metrics carry very different list prices. On the Oracle Technology Global Price List, Oracle Analytics Server has been quoted at roughly $2,000 per Named User Plus and $221,250 per Processor (Oracle Licensing Experts, April 2025). Legacy BI Suite EE Plus on a government schedule ran $2,160 per NUP and $238,950 per Processor (Victoria State Purchase Contract, September 2017), and BI Foundation Suite ran $3,969 per NUP and $324,000 per Processor. Whatever line item you hold, the ratio between the two prices is the single number that drives the decision. We work through it below. For the broader stack economics, start with our Oracle BI and Analytics on-premise licensing buyer guide.
The NUP metric has a floor, and buyers coming from the Oracle Database world get it wrong constantly. For OBIEE and OAS (and Fusion Middleware generally, including WebLogic, SOA Suite, WebCenter, and Identity Management), the minimum is 10 Named User Plus licenses per Processor License. That is different from Oracle Database Enterprise Edition, which uses a 25 NUP per processor minimum. If your mental model is 25, you will under-buy on the database side and over-anchor on the BI side. The middleware floor is 10 (Redress Compliance, April 2025).
The rule is a higher-of test: you license the greater of your actual authorized user count or the per-processor minimum. Compute the Processor count first (cores x core factor), then multiply by 10. Two worked examples from our advisory files make the mechanics concrete:
The floor is computed from the hardware, not the headcount. Small user bases on big servers pay for users they do not have.
In authorized cloud environments Oracle adapts the floor proportionally, roughly 10 NUP per 8 vCPUs. The practical consequence is the same: your infrastructure sizing sets a minimum spend that no amount of user discipline can undercut. If your servers are oversized relative to your user base, NUP does not save you what the raw per-seat price suggests.
The decision reduces to one arithmetic comparison. Take the Processor price, divide by the NUP price, and you get the number of users at which one Processor of NUP licenses equals one Processor license. Historically for OBIEE that number is around 50 NUP per Processor equivalent (Redress Compliance, April 2025). Below roughly 50 authorized users per Processor, NUP is cheaper. Above it, Processor wins. The table below shows the crossover for the three common price lines using their published NUP and Processor rates.
| Product line | NUP list | Processor list | Break-even users per processor | Cheaper metric below break-even |
|---|---|---|---|---|
| OAS (2025 quote) | $2,000 | $221,250 | ~111 | NUP |
| BI Suite EE Plus (2017) | $2,160 | $238,950 | ~111 | NUP |
| BI Foundation Suite (2017) | $3,969 | $324,000 | ~82 | NUP |
Two cautions on this table. First, the raw price ratio (111 and 82 in the columns above) is higher than the ~50 rule of thumb because the rule of thumb bakes in real-world discounting patterns and the fact that NUP counts often creep above the nominal user list once you count service accounts, test users, and stale accounts. Treat ~50 as the practical planning number and the raw ratio as the theoretical ceiling. Second, these are list prices; your actual break-even shifts with your negotiated discount, which is usually deeper on Processor than on NUP because Oracle prefers the metric that locks you in. Model both at your real discounts before deciding.
The clean decision rules, from years of running this comparison: pick Named User Plus when your authorized population is small, stable, internally-facing, and you can definitively identify and count every human and system with access, and the post-minimum count sits below roughly 50 per Processor equivalent. Pick Processor when the population is large, external, or unpredictable, when counting every authorized user is impractical, when the deployment is internet-facing, or when you simply want the lowest-effort compliance posture (Redress Compliance, April 2026).
This is where NUP deployments explode. Oracle counts report consumers, not just report authors. Every person who views a dashboard, receives a bursted BI Publisher email, or reads an embedded analytic inside another application is an authorized user and must be licensed. The instinct to license only the fifteen people who build reports, and treat the four hundred who read them as free, is the most expensive mistake in OBIEE licensing.
Buyers try to escape this by routing access through a portal, an integration layer, or a middleware app that pools connections. It does not work. Oracle's own license definitions state the count must be measured at the multiplexing front end: 'This number must be measured at the multiplexing front end' (Oracle License Definitions and Rules, v111815). Applied to BI specifically, if OBIEE is reached through a web portal or aggregation layer that consolidates sessions, Oracle still requires each individual end user to be counted (Oracle Licensing Experts, January 2025). A connection pool showing ten database sessions serving four hundred humans is four hundred Named Users. For the external-facing version of this problem, see counting external and anonymous users in OBIEE partner portals.
A portal that hides four hundred users behind ten connections licenses four hundred users. The front end is where Oracle counts.
When the consumer population is external, anonymous, or unbounded, NUP becomes an open-ended liability that is impossible to defend in an audit. You cannot enumerate members of the public who hit a customer-facing dashboard, so you cannot cap the NUP count, so Oracle treats the obligation as unlimited. For internet-facing deployments where the user population is large, unknown, or unlimited, Processor is almost always the correct and the safer metric (Redress Compliance, April 2026). For broad publishing to all staff or the public, Processor is usually cheaper as well as cleaner (Redress Compliance OAS Guide, October 2025).
The rule of thumb: if you cannot produce a defensible, bounded list of every authorized human and system, you do not qualify for NUP on that deployment. Segment your estate. Keep NUP on the controlled internal analytics environment with a known user list, and put Processor on the anything that faces partners, customers, or the internet. Mixing metrics across servers is permitted and is often the lowest-cost lawful configuration.
If you go NUP, the audit exposure lives in your identity hygiene, not your usage. Oracle's audit method requests a list of all accounts with authorized access regardless of last login. An employee who left six months ago but was never deprovisioned counts as an authorized user until the account is explicitly deleted (Redress Compliance, April 2026). Stale accounts are the single most common cause of a NUP shortfall finding. Two further exposures ride alongside:
OBIEE is at end of life. Its on-premises successor is Oracle Analytics Server, and existing OBIEE entitlements with active support generally include the right to run OAS (Redress Compliance OAS Guide, October 2025), so the NUP-versus-Processor logic carries forward unchanged. Do not let a support renewal be repackaged as a fresh purchase. Before you re-buy anything, read OBIEE end-of-life: migrating to Oracle Analytics Server or off Oracle.
For a total-cost comparison, Oracle Analytics Cloud lists at $80/user/month (Enterprise) and $16/user/month (Professional), with BYOL at $0.3226/OCPU/hour for both tiers (Software Finder, 2026). The Enterprise per-user cloud rate annualizes to $960 per user per year, which crosses the perpetual NUP list price of $2,000 in roughly 25 months. Cloud can look cheap for two years and expensive across a five-year horizon. Run the TCO on your real user count and support percentage, and if you are considering dropping Oracle support entirely, weigh OBIEE on third-party support against the migration cost.
Run this sequence before your next renewal or true-up. It is the same sequence we run on client engagements, and it typically finds either shelfware to retire or a metric mismatch to fix.
The leverage sits with the buyer who arrives with the metric math already done. Oracle's default recommendation is the metric that maximizes its revenue and lock-in, which is usually Processor on large deployments and NUP on small ones with the floor working in Oracle's favor. Your job is to prove which is genuinely cheaper at your scale and to hold the line. Redress Compliance runs this analysis independently, on the buyer's side, with no reseller incentive.
Ten Named User Plus licenses per Processor License. This is the Fusion Middleware floor and it is lower than the Oracle Database minimum of 25 NUP per processor. You license the higher of your actual authorized users or this floor, computed from cores multiplied by the core factor.
The practical planning number for OBIEE is around 50 authorized users per Processor equivalent. Above that, Processor is usually cheaper; below it, NUP wins. The raw list-price ratio is higher (about 82 to 111 depending on the product line), but real NUP counts inflate with report consumers and stale accounts, so use ~50 as your working threshold.
Yes. Oracle counts all report consumers, not just report authors. Anyone who views a dashboard, receives a bursted report, or reads an embedded analytic is an authorized user under NUP and must be licensed. This is the most common reason NUP deployments cost more than expected.
No. Oracle's license definitions require the count to be measured at the multiplexing front end. A portal, integration layer, or connection pool that aggregates sessions does not reduce the count; every individual end user behind it must still be licensed.
You cannot enumerate an external or anonymous audience, so a NUP count cannot be bounded, which creates an open-ended liability Oracle treats as unlimited. For internet-facing or public deployments, Processor is almost always both the correct metric and the cheaper one for broad publishing.
Generally yes. OAS is the on-premises successor to OBIEE, and existing OBIEE entitlements with active support usually include the right to run OAS. The NUP-versus-Processor logic carries forward unchanged, so do not let a support renewal be repackaged as a new purchase.
Oracle sells the same database per user and per processor. The 25 NUP per processor minimum, the 50 user break-even, and how to choose the metric that fits the workload.
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.
