Oracle Analytics Server carries one of the highest per-processor list prices in Oracle's technology portfolio at $221,250 per processor. Yet Named User Plus licensing at $2,000 per user creates a massive cost differential that makes licence model selection one of the most consequential decisions in analytics infrastructure planning. This guide covers the complete OAS licensing framework: model comparison with breakeven analysis, pricing mechanics, included component restrictions, database and middleware obligations, virtualisation and cloud rules, OBIEE upgrade rights, OAS vs OAC comparison, common audit findings, and cost optimisation strategies.
This guide is part of our Oracle technology licensing coverage. See also: Oracle BI Suite Foundation Edition Licensing | Oracle Licence Metrics & Definitions | Oracle Database Licensing Guide
Oracle Analytics Server is licensed under Oracle's standard perpetual licensing framework with two primary metrics: Named User Plus (NUP) and Processor. The choice between them determines both the cost structure and the compliance governance burden. NUP licensing is dramatically cheaper for small, controlled user populations. Processor licensing is necessary when user counts are large, unpredictable, or external-facing. Oracle also offers OAS Standard Edition One for small deployments with lower pricing but significant feature and scalability restrictions.
| Attribute | Named User Plus (NUP) | Processor | Standard Edition One |
|---|---|---|---|
| List price | $2,000 per named user | $221,250 per processor | ~$1,200 per named user |
| Annual support (22%) | $440 per user per year | $48,675 per processor per year | ~$264 per user per year |
| User coverage | Each named individual accessing OAS must be licensed | Unlimited users on the licensed server | Typically capped at ~50 users; single server |
| Minimum requirement | 10 NUP per processor of the server | All occupied cores x core factor = processor count | ~5 NUP minimum |
| Best for | Small, defined internal analytics teams (10 to 100 users) | Enterprise-wide deployments; external-facing dashboards; large or unpredictable user populations | Small business or departmental use only |
NUP vs Processor breakeven analysis. The breakeven point where NUP and Processor costs converge is approximately 443 users on a 4-processor server. Below that threshold, NUP is cheaper. Above it, Processor is cheaper. At 25 users on a 4-processor server, NUP is 94% cheaper than Processor ($50,000 vs $885,000 at list). At 200 users, NUP is still 55% cheaper ($400,000 vs $885,000). The difference is enormous. Getting this decision right is one of the highest-value licensing optimisations available for analytics infrastructure.
Oracle requires a minimum of 10 Named User Plus licences per processor of the server running OAS, calculated using the core factor. On a 2-socket, 16-core Intel server (core factor 0.5 = 8 processors), the minimum NUP is 80 licences = $160,000 even if only 5 people use the system. This minimum frequently surprises organisations that deploy OAS for a small analytics team on a large server. The fix: either right-size the hardware (deploy on smaller infrastructure to reduce the processor count and therefore the NUP minimum) or evaluate whether the minimum NUP cost is still cheaper than processor licensing for your specific scenario. See our Oracle NUP minimum requirements guide.
| Component | Included? | Usage Restriction | Compliance Risk if Exceeded |
|---|---|---|---|
| Oracle BI Publisher | Yes (included) | Only for generating reports within OAS; not for standalone enterprise reporting | Using BI Publisher outside OAS context requires separate BI Publisher licensing |
| WebLogic Server Standard Edition | Yes (restricted-use) | Only for deploying and running OAS; no custom applications, no clustering beyond OAS scope | Deploying custom apps on OAS WebLogic = full WebLogic licensing required ($25,000/proc) |
| Oracle Database (repository) | NOT included | OAS requires a database for its metadata repository; must be licensed separately | Using Oracle DB for OAS repository without separate licence = $47,500/proc EE exposure |
| Oracle Data Integrator (ODI) | NOT included | Required for Oracle BI Applications ETL; must be separately licensed if used | ODI usage without licence = separate compliance finding |
| Oracle Database options | NOT included | Any database options used on OAS repository or connected data sources require separate licensing | DBA enabling Diagnostics Pack on OAS repository DB = full EE + option licensing |
| Oracle Analytics Cloud (OAC) | Separate product | Cloud subscription service; entirely different licensing model (per user/per OCPU) | OAC subscription does not cover on-premises OAS usage (and vice versa) |
OAS includes a restricted-use licence for WebLogic Server Standard Edition, limited to running the OAS application only. If a system administrator deploys any custom application, web service, or middleware component on the same WebLogic instance, Oracle considers the restricted-use licence violated and requires full WebLogic licensing at $25,000 per processor across the entire server. On an 8-processor OAS server, this creates an additional $200,000 in WebLogic licensing, plus $44,000/year in support, for a configuration change that may have been made for convenience. Additionally, clustering the OAS WebLogic across multiple nodes for HA requires full WebLogic Enterprise Edition licensing. Always isolate OAS WebLogic from any non-OAS workloads.
| Deployment Scenario | Licence Cost (list) | Annual Support (22%) | 5-Year TCO |
|---|---|---|---|
| NUP: 50 users on 4-proc server | $100,000 | $22,000/year | $210,000 |
| NUP: 200 users on 4-proc server | $400,000 | $88,000/year | $840,000 |
| Processor: 4 procs (unlimited users) | $885,000 | $194,700/year | $1,858,500 |
| Processor: 8 procs (unlimited users) | $1,770,000 | $389,400/year | $3,717,000 |
| SE One: 30 users | $36,000 | $7,920/year | $75,600 |
At list price, a mid-size OAS deployment on a 2-socket, 16-core Intel server (8 processors after core factor) costs $1,770,000 under processor licensing, before any database, middleware, or support costs. The 5-year TCO including support reaches $3,717,000 for processor licensing. NUP at 200 users on the same server costs $840,000 over five years. The difference is $2.9M. Enterprise customers typically negotiate 40 to 60% discounts for new deployments. Even with a 50% discount, the 5-year processor TCO is still $1.86M. Licence model selection is the single most impactful cost lever for OAS.
For pricing mechanics and core factor calculations, see our Oracle Technology Price List guide and Oracle Core Factor Table calculator.
| Environment | OAS Licensing Rule | Compliance Strategy |
|---|---|---|
| VMware / Hyper-V / KVM | All physical cores across all hosts in the cluster where the OAS VM could run must be licensed (soft partitioning not recognised). OAS VM on a 10-host cluster: all hosts must be licensed = potentially $4M+ at list. | Dedicate a small server or isolated host for OAS. Pin VMs with affinity rules. Document isolation. |
| Oracle VM (OVM) | Hard partitioning recognised. Licence only the resources assigned to the OAS VM. Significant cost savings vs VMware. | Configure OVM properly. Document partition assignments for audit defence. |
| AWS / Azure / GCP (BYOL) | Standard cloud BYOL rules: 2 vCPUs = 1 processor licence (with hyper-threading). 8-vCPU instance = 4 processor licences = $885,000 at list. | Right-size cloud instances to minimise processor count. Consider OAC as alternative. |
| Oracle Cloud Infrastructure (OCI) | BYOL or licence-included. 1 OCPU = 1 processor licence. OCI BYOL applies existing on-premises licences. | OCI can be cost-effective for OAS BYOL. Compare against OAC subscription pricing. |
For OAS at $221,250 per processor, virtualisation misconfiguration creates the largest compliance exposures we see. A single OAS VM on a shared 10-host VMware cluster could theoretically expose the organisation to licensing demands for every core across all 10 hosts. The solution is isolation. For comprehensive virtualisation guidance, see our Oracle Partitioning Policy guide and Oracle Licensing in Virtualised Environments.
| Scenario | Licensing Requirement | Key Risk |
|---|---|---|
| Existing OBIEE with active support | No new licence purchase required. OAS is included as an upgrade under active OBIEE support. Same metric and quantity carry forward. | If support was terminated, upgrade rights are lost. Must purchase new OAS licences. |
| OBIEE with lapsed support | Must reinstate OBIEE support (with back-dated fees + 20% penalty) or purchase new OAS licences. | Running OAS without valid licence = full compliance exposure at current list price. |
| New OAS deployment (no OBIEE history) | Full OAS licence purchase required at current pricing. Standard Oracle procurement. | List prices are very high. Negotiate 40 to 60% discounts for new deployments. |
| OBIEE metric conversion (NUP to Processor) | Requires new licence purchase or negotiated conversion. Existing NUP cannot be automatically converted to Processor. | Conversion without negotiation = paying full processor price with no credit for existing NUP investment. |
The OBIEE-to-OAS upgrade path is straightforward when support is current. But we regularly encounter organisations that let OBIEE support lapse, deployed OAS assuming the upgrade right was permanent, and are now facing full list price compliance exposure. Oracle's position is clear: no active support means no upgrade entitlement. Always verify OBIEE support status before deploying OAS. For details on Oracle support reinstatement policies, see our Oracle Support Policies guide.
| Attribute | OAS On-Premises | Oracle Analytics Cloud (OAC) |
|---|---|---|
| Pricing model | Perpetual licence (one-time purchase) + 22% annual support | Subscription: per user/month or per OCPU/hour. No perpetual ownership. |
| Infrastructure | Customer-managed servers. Customer responsible for patching, upgrades, HA. | Oracle-managed. Automatic updates. Built-in HA. |
| Cost structure | High upfront CapEx. Predictable annual OpEx (support). | Pure OpEx. Lower entry cost but recurring and potentially escalating. |
| Customisation | Full control over configuration, extensions, integrations. | Limited customisation. SaaS constraints apply. |
| Data residency | Complete control. Data stays on-premises. | Data in Oracle Cloud. May have regional residency options. |
| BYOL option | N/A (already on-premises) | Existing OAS/OBIEE licences can be applied via BYOL. |
| Long-term cost (5+ years) | Often cheaper for large, stable deployments. | Often cheaper for small/variable deployments. Can be more expensive long-term at scale. |
Oracle audits of OAS environments find compliance gaps in 35 to 50% of cases, with findings typically ranging from $100K to $2M+. These are the findings we encounter most frequently.
| Audit Finding | How It Occurs | Typical Cost Impact |
|---|---|---|
| NUP under-count | Actual users accessing OAS exceed licensed NUP count. Includes users connecting through portals, middleware, or embedded reports. | $50K to $500K+ ($2,000 per additional user + back support) |
| NUP minimum not met | Organisation licences 20 NUP for a server that Oracle counts as 4 processors. Minimum is 40 NUP. | $40K to $160K (shortfall x $2,000/NUP) |
| WebLogic scope violation | Custom application or web service deployed on OAS restricted-use WebLogic instance. | $100K to $500K+ (full WebLogic licensing across all OAS server processors) |
| Database repository unlicensed | Oracle Database used for OAS metadata repository without separate database licence. | $190K to $760K+ (full Oracle DB EE processor licensing for repository server) |
| VMware cluster-wide licensing | OAS VM on shared VMware cluster. Oracle requires licensing all hosts. Processor count far exceeds what was licensed. | $500K to $5M+ (entire cluster licensed at OAS processor rates) |
| Hardware change without licence adjustment | Server upgraded to more cores or migrated to larger infrastructure without adjusting processor licence count. | $200K to $1M+ (additional processor licences required) |
For audit defence strategies, see our Oracle Audit Strategic Guide.
1. Right-size hardware. Deploy OAS on the smallest server that meets performance requirements. Fewer cores = fewer processors = lower NUP minimum or processor licence cost. Reducing from 8 to 4 processors halves processor licence cost, saving $200K to $1M+.
2. Licence model selection. Choose NUP for 400 users or fewer. Switch to Processor only when NUP exceeds processor cost. NUP for 200 users = $400K vs Processor at $885K to $1.77M. Savings: $400K to $1.5M.
3. Virtualisation isolation. Move OAS from shared VMware cluster to dedicated host or Oracle VM to reduce licensed infrastructure. Avoids cluster-wide licensing. Savings: $500K to $3M+.
4. Repository database optimisation. Use existing licensed Oracle DB for OAS repository. Or use Oracle XE (free) or a non-Oracle DB if supported. Avoids separate DB licence purchase. Savings: $190K to $760K.
5. Negotiate discounts. Leverage Oracle's fiscal calendar, competitive alternatives (Power BI, Tableau), and multi-product deals for 40 to 60% off list. Savings: $350K to $1M+ on a 4-processor deployment. For negotiation strategies, see our guide on managing Oracle contracts.
6. Evaluate OAC migration. For growing user populations, compare OAC subscription cost against OAS on-premises TCO. Use BYOL to apply existing licences. OAC can be cheaper for small/variable deployments. OAS is typically cheaper for large/stable ones. Factor in BYOL credits, data migration costs, and long-term subscription escalation.
Quarterly user access reconciliation. For NUP-licensed deployments, audit all OAS user accounts against the licensed quantity. Include users accessing OAS through portals, embedded reports, middleware, and APIs. Remove dormant accounts. Verify the 10-NUP-per-processor minimum is met based on current hardware.
Hardware and processor tracking. Maintain an accurate inventory of all servers running OAS, including core counts, socket counts, and applicable core factors. Require ITAM approval before any hardware change, migration, or server consolidation. Recalculate licence requirements after every infrastructure change.
Restricted-component scope verification. Confirm that OAS restricted-use WebLogic hosts no non-OAS applications or services. Verify that BI Publisher usage is limited to OAS-integrated reporting. Audit WebLogic deployments quarterly.
Database licence compliance. Verify that the OAS metadata repository database is separately licensed (if using Oracle DB). Check DBA_FEATURE_USAGE_STATISTICS on the repository database for accidentally enabled options.
Virtualisation isolation documentation. If OAS runs in a virtualised environment, document the isolation architecture (dedicated hosts, affinity rules, hard partitioning). Confirm that OAS VMs cannot migrate to unlicensed hosts. Maintain documentation for audit defence.
OBIEE upgrade entitlement verification. If OAS was deployed as an upgrade from OBIEE, confirm that the original OBIEE licences are valid with active support. Maintain documentation of the OBIEE-to-OAS upgrade path.
OAS Enterprise Edition offers two licensing models: Named User Plus (NUP) at $2,000 per user (list price), and Processor at $221,250 per processor (list price). NUP requires a minimum of 10 licences per processor of the server. Processor licensing counts cores x core factor and provides unlimited user access. OAS Standard Edition One is available at ~$1,200/NUP for small deployments (single server, ~50 users). The choice depends on user count: NUP is cheaper below approximately 443 users per 4-processor server; Processor is cheaper above that threshold.
Yes, if your OBIEE licences are current with active Oracle support. OAS is the on-premises successor to OBIEE, and existing OBIEE customers with active support can upgrade to OAS at no additional licence cost. The same metric (NUP or Processor) and quantity carry forward. However, if your OBIEE support has lapsed, you must either reinstate support (paying all back-dated fees plus a 20% penalty) or purchase new OAS licences at current pricing. Always verify entitlement documentation before deploying OAS.
No. The OAS licence does not include an Oracle Database licence. OAS requires a relational database for its metadata repository, and if you use Oracle Database for this purpose, it must be licensed separately under Oracle's standard database licensing rules ($47,500/processor for Enterprise Edition or $17,500/socket for Standard Edition 2). Alternatives include using an existing licensed Oracle DB, Oracle Database Express Edition (free but limited), or a supported non-Oracle database to avoid additional Oracle licensing costs.
The WebLogic Server Standard Edition included with OAS is restricted-use. It can only run the OAS application. Deploying any custom application, web service, or middleware component on the same WebLogic instance violates the restricted-use terms. Oracle treats this as requiring full WebLogic licensing at $25,000 per processor across the entire server. On an 8-processor OAS server, this creates a $200,000+ additional licensing obligation. Always keep OAS WebLogic completely isolated from non-OAS workloads.
Yes, but Oracle's soft partitioning policy applies. Oracle does not recognise VMware as a licensing boundary. All physical cores across all hosts in the VMware cluster where the OAS VM could potentially run must be licensed. For OAS, with its $221,250/processor list price, this can create enormous exposure on shared clusters. The solution is to isolate OAS VMs to a dedicated host or small cluster, use VM affinity rules to prevent migration, and document the isolation. Oracle VM (OVM) is an alternative that Oracle recognises as hard partitioning. See our Oracle Partitioning Policy guide.
It depends on deployment scale, user variability, and strategic direction. OAS on-premises is typically cheaper for large, stable deployments over 5+ years (perpetual licence amortised over time). OAC is often better for small or variable user populations, organisations moving to cloud-first strategies, or those wanting Oracle-managed infrastructure. If you have existing OAS/OBIEE licences, you can apply them to OAC via BYOL, reducing the cloud subscription cost. Always model the 5-year TCO for both scenarios before deciding.
Our Oracle advisory team regularly uncovers OAS compliance gaps and equally often finds that organisations are over-licensed. An independent review can save you from audit exposure or unnecessary spend. Typical savings: $200K to $2M+. Independent. Fixed-fee. No Oracle bias.
Oracle Advisory ServicesIndependent Oracle Analytics Server licensing advisory. Compliance assessment, cost optimisation, audit defence. Fixed-fee. Vendor-independent.