Oracle's Two Licensing Families
Oracle organises its product catalogue into two primary licensing families. The Technology licensing family covers Oracle's infrastructure, database, and middleware products — software that provides computing platform capabilities. The Applications licensing family covers Oracle's business application software — software that provides functional business capabilities to end users. Understanding which family a product belongs to determines not only how it is licensed, but how audits work, how contracts are structured, and which negotiation tactics are relevant.
This distinction has become more complex with Oracle's SaaS transition. Many Application products that were previously sold on-premises under perpetual licences are now available as cloud subscriptions (Oracle Fusion Cloud), which changes the licensing model significantly. Technology products have also expanded into cloud versions (Oracle Autonomous Database, Oracle Cloud Infrastructure), where the pricing and licensing model differs from the on-premises Technology licensing rules.
The most costly Oracle licence errors arise at the boundary between Technology and Application licences — particularly when enterprises assume that an Application licence includes unrestricted use of the underlying Technology infrastructure, or when Technology deployments expand beyond the scope of the restricted-use entitlements bundled with Application licences.
Oracle Technology Licensing: Infrastructure-Tied
Oracle Technology products are licensed based on the computing infrastructure running the software. The two primary metrics — Processor and Named User Plus — tie the licence obligation to the hardware footprint. Oracle Database, Oracle Fusion Middleware (WebLogic, SOA Suite, OSB), Oracle Identity Management, Oracle Developer Tools, and related products are all Technology-family products licensed under these infrastructure-based metrics.
Core Characteristics of Technology Licences
Hardware-driven obligation: The number of Processor licences required is determined by the number of processor cores running Oracle Technology software, multiplied by Oracle's core factor. Adding servers, expanding existing servers, or migrating to infrastructure with higher core counts increases the licence obligation regardless of how the software is used.
Virtualisation policy applies: Oracle's soft partitioning rule — which requires licensing all physical cores in servers running Oracle Technology on VMware, Hyper-V, or similar hypervisors — is a Technology licensing rule. It applies to Oracle Database, WebLogic, SOA Suite, and all other Technology products. See our full guide to Oracle partitioning rules and VMware.
Options add to the base: Technology products have add-on Options (Database Partitioning, Advanced Security, etc.) and Packs (Diagnostics Pack, Tuning Pack) that are priced separately as a percentage of the base Technology licence. Enabling an option without purchasing the corresponding licence creates a compliance gap.
Oracle Application Licensing: User-Based
Oracle Application products are licensed based on the people using the software. The primary metric for on-premises Application licensing is the Application User — typically defined as any individual authorised to access the application's functionality. Unlike Technology licences, Application User counts are not affected by the hardware running the application; adding more servers to an EBS deployment does not increase the Application licence obligation, though it may increase the restricted-use Technology licence requirement.
On-Premises Application Products
The major Oracle on-premises Application products are Oracle E-Business Suite (EBS), Oracle PeopleSoft, Oracle JD Edwards (JDE), and Oracle Siebel CRM. Each is licensed under a specific set of Application User metrics — Full Use, Limited Use, or Employee metrics — defined in the Oracle Applications metrics guide. The user count at renewal is the primary commercial lever: Oracle computes the licence obligation based on the number of named users or employees entitled to use each module.
Oracle Fusion Cloud (SaaS Applications)
Oracle Fusion Applications — Oracle ERP Cloud, Oracle HCM Cloud, Oracle SCM Cloud, Oracle CX Cloud — are sold as SaaS subscriptions priced per user per month or per employee per year. Fusion Cloud licensing eliminates the Technology infrastructure dimension because Oracle manages the underlying database and middleware as part of the cloud service. The licence obligation is purely a function of user counts and the specific modules subscribed to.
Fusion Cloud subscription pricing is substantially more predictable than on-premises Application licensing, but it introduces different commercial risks: annual price escalation clauses, automatic user-count true-ups, and minimum commit levels that may not scale down if the organisation reduces headcount.
Side-by-Side Comparison
How Technology and Application Licences Interact
The most complex Oracle licensing scenarios arise when Technology and Application licences coexist in the same environment. The interaction point is the restricted-use Technology licence that Oracle bundles with most on-premises Application products.
The Restricted-Use Technology Licence
When you purchase an Oracle Application licence (for example, Oracle E-Business Suite), Oracle includes a restricted-use licence for the Oracle Technology products required to operate the application — typically Oracle Database and Oracle WebLogic Server. This restricted-use Technology licence is valid only for running the specific Application it accompanies; it cannot be used for any other purpose.
The restriction has important practical consequences. You cannot run custom database schemas in the EBS Oracle Database instance without a separate full-use Technology licence. You cannot use the WebLogic instance bundled with EBS for any application other than EBS. And if you use Oracle E-Business Suite alongside Oracle APEX, a custom data warehouse, or any other workload on the same Oracle Database instance, the non-application workloads require separate full-use Technology licences.
The EBS to Fusion Cloud Transition Complication
When enterprises migrate from Oracle E-Business Suite (an on-premises Application) to Oracle Fusion Cloud (a SaaS Application), the on-premises Technology infrastructure supporting EBS — Oracle Database, WebLogic, SOA Suite — remains in place during the transition period. These Technology products require their own licences during the parallel-running phase. Enterprises migrating to Fusion Cloud often face a period of double licensing: both the Fusion Cloud SaaS subscription and the on-premises Technology licences for the legacy EBS infrastructure. Negotiating the transition timeline to minimise this overlap is one of the highest-value elements of an Oracle Fusion Cloud migration contract.
Negotiation Differences: Technology vs Applications
Oracle Technology and Application negotiations require fundamentally different strategies because the commercial drivers and Oracle's incentives differ between the two licensing families.
Negotiating Oracle Technology Licences
Technology licence negotiations are primarily driven by hardware decisions. The key levers are: server consolidation (reducing processor count), migration to OCI (where Oracle accepts vCPU licensing), replacement with open-source alternatives (PostgreSQL for Database, JBoss for WebLogic, Apache Camel for SOA Suite), and timing (Oracle's fiscal quarter end unlocks larger discounts). Reducing Oracle support costs is a central focus because Technology products carry significant annual support fees that compound over the agreement lifetime.
Negotiating Oracle Application Licences
Application licence negotiations are primarily driven by user counts and module deployment. Rationalising user counts — removing stale users, consolidating limited-use and full-use licences, identifying departments where module access can be reduced — directly reduces the commercial baseline. For on-premises Applications like EBS and PeopleSoft, the conversion to Fusion Cloud SaaS creates a significant negotiation moment: Oracle values SaaS conversions and will offer commercial incentives (conversion credits, support extensions, pricing commitments) that can materially reduce the total cost of transition.
For comprehensive guidance on Oracle contract negotiation across both licensing families, see our Complete Guide to Oracle Licensing & Contract Negotiation. Our Oracle Negotiation Playbook provides detailed commercial frameworks for both Technology and Application negotiations, including benchmarks from $10M+ Oracle deals.