Running PeopleSoft on virtualised infrastructure or in the cloud introduces licensing complexity that many organisations underestimate. Oracle's virtualisation policies, processor core factor calculations, Named User Plus minimums, and cloud-specific rules create a compliance landscape where a single architectural decision can multiply licensing costs by a factor of three or more. This guide explains how PeopleSoft licensing works across virtualised and cloud environments.
This guide is part of our PeopleSoft Licensing series. For related guides, see: PeopleSoft Licensing Guide: 4 Ways of Licensing | PeopleSoft Compliance and Audit Best Practices.
PeopleSoft applications are licensed under Oracle's standard licence metrics, primarily Named User Plus (NUP) and Processor. Understanding which metric applies and how it interacts with virtualisation and cloud infrastructure is the foundation for managing costs in these environments.
| Metric | How It Works | Impact in Virtual/Cloud |
|---|---|---|
| Processor | Licences the physical or virtual cores running PeopleSoft, multiplied by Oracle's core factor for the specific CPU architecture. Intel/AMD typically 0.5 (two cores = one licence). SPARC varies 0.25 to 0.5 | Directly affected by virtualisation policy. VMware soft partitioning can multiply required licences by 10x to 30x. Cloud vCPU counting rules differ by provider |
| Named User Plus (NUP) | Licences individual named users who access the PeopleSoft system. Subject to minimum user-per-processor requirements that vary by product | Immune to the soft partitioning cost multiplier. User count does not change based on infrastructure. A 500-user deployment costs the same on VMware or dedicated hardware |
| Technology Tier | Licensing Requirement | Key Consideration |
|---|---|---|
| Oracle Database (usually Enterprise Edition) | Licensed separately from PeopleSoft. Own metric, pricing, and virtualisation rules apply independently | Database licensing frequently exceeds PeopleSoft application licensing cost. $47,500 per Processor at list price. Soft partitioning on VMware is the #1 cost risk |
| PeopleSoft Application Server (PeopleTools) | Licensed based on PeopleSoft modules deployed and metric chosen (NUP or Processor) | Same virtualisation rules apply but per-core cost typically lower than database tier |
| Web Server (PIA) | Typically included in the PeopleSoft application licence. No separate Oracle licensing | Underlying OS and middleware may have their own licence requirements |
| Process Scheduler | Licensed as part of the PeopleSoft application tier | Runs batch processes. Same licensing rules as app server. Consider right-sizing vCPU allocation |
PeopleSoft deployments involve multiple technology tiers, each with its own licensing requirements. The database tier is licensed separately from the application tier, and Oracle's virtualisation and cloud policies apply independently to each. Virtualisation decisions on the database server (such as running Oracle Database on VMware) have different cost implications than the same decision on the application server. The database tier and application tier do not need to be on the same infrastructure. Separating them to optimise database licensing is a common architecture pattern.
Oracle's virtualisation policy is the single most important factor determining PeopleSoft licensing costs in virtual environments. Oracle classifies virtualisation technologies into two categories, and the classification determines whether the organisation can licence only the cores allocated to the PeopleSoft virtual machine or must licence every physical core on the host server.
| Classification | Technologies | Licensing Rule | Cost Impact |
|---|---|---|---|
| Hard partitioning (approved) | Oracle VM (OVM), Oracle Solaris Zones (capped), IBM LPAR, Oracle Linux KVM (since 2020) | Licence only the cores allocated to the partition running PeopleSoft. A 32-core server with an 8-core hard partition requires licensing only 8 cores (x core factor) | Minimal. You pay for what you allocate. CPU pinning must be configured and documented |
| Soft partitioning (not recognised) | VMware vSphere, Microsoft Hyper-V, Nutanix AHV, KVM (non-Oracle Linux), Citrix Hypervisor | Licence all physical cores on every host server where the PeopleSoft VM could potentially run. In a VMware cluster with vMotion, this means all hosts in the cluster | Catastrophic. A 4-host cluster with 32 cores each requires licensing 128 cores even if PeopleSoft runs on a single 4-vCPU VM |
| Cost Impact Example | Detail |
|---|---|
| Scenario | PeopleSoft on a 4-vCPU VM within a VMware cluster of four hosts, each with 32 Intel Xeon cores (core factor 0.5) |
| Hard partitioning (OVM) | 4 cores x 0.5 = 2 Processor licences required |
| Soft partitioning (VMware) | 128 physical cores x 0.5 = 64 Processor licences required |
| Cost difference | 32x increase. Potentially millions of dollars in additional licensing depending on which PeopleSoft modules and Oracle Database editions are deployed |
Organisations running PeopleSoft on VMware have several options: migrate PeopleSoft workloads to Oracle VM (hard partitioning), deploy on dedicated physical hosts outside the VMware cluster, use VMware affinity rules to restrict PeopleSoft VMs to specific hosts (Oracle does not officially recognise this but it limits practical scope), or migrate to Oracle Cloud Infrastructure where different licensing rules apply. Each option involves trade-offs between infrastructure flexibility, operational complexity, and licensing cost.
Oracle Cloud Infrastructure (OCI) offers the most favourable licensing terms for PeopleSoft deployments. Under Oracle's BYOL (Bring Your Own Licence) policy on OCI, each Processor licence covers two Oracle Compute Units (OCPUs), where each OCPU corresponds to a physical core with hyper-threading. This effectively means one on-premises Processor licence covers twice the compute capacity on OCI.
| OCI Advantage | Detail |
|---|---|
| 2:1 OCPU-to-licence ratio | Each Processor licence covers 2 OCPUs on OCI versus 1 physical core on-premises (at 0.5 core factor). This effectively halves the Processor licence requirement for equivalent compute capacity. A workload requiring 8 Processor licences on-premises needs only 4 on OCI |
| No soft partitioning problem | OCI instances are metered and licensed based on the specific OCPU allocation. No requirement to licence the underlying physical infrastructure. Oracle manages the hypervisor layer and guarantees compute isolation |
| PeopleSoft Cloud Manager | Oracle provides PeopleSoft-specific reference architectures and migration tools. PeopleSoft Cloud Manager automates provisioning, lifecycle management, and patching of PeopleSoft environments on OCI |
| Combined savings potential | Eliminating soft partitioning plus the 2:1 OCPU ratio can reduce PeopleSoft Processor licensing costs by 50% or more compared to on-premises VMware deployments |
For PeopleSoft workloads where the database and application tiers run on OCI, the BYOL model can reduce the total Processor licence requirement by approximately 50% compared to the same workload running on equivalent on-premises hardware. OCI eliminates the soft partitioning problem entirely and provides native PeopleSoft tooling. This is why Oracle actively promotes OCI migration for PeopleSoft customers.
Running PeopleSoft on third-party cloud providers is technically supported but introduces licensing considerations that differ significantly from OCI deployments. Oracle's Authorised Cloud Environment policy permits BYOL to certain approved cloud providers, but the terms are less favourable than OCI.
| Cloud Provider | Licensing Rule | Comparison to OCI |
|---|---|---|
| AWS | Each vCPU counts as equivalent to one physical core for licensing purposes (assuming hyper-threading enabled). One Processor licence covers one vCPU (with 0.5 core factor: 2 vCPUs = 1 licence) | Effectively doubles the Processor licence requirement for equivalent compute capacity compared to OCI. One licence covers 2 OCPUs on OCI but only 2 vCPUs on AWS |
| Azure | Same rules as AWS. Each vCPU counted as one core. Apply core factor to determine Processor licences | Same cost disadvantage versus OCI. Decision must weigh additional Oracle licensing cost against operational benefits of single-cloud standardisation |
| Google Cloud | Same Authorised Cloud Environment rules apply. vCPU-to-core mapping follows Oracle's published ratios | No OCI BYOL advantage. Verify Oracle agreement includes Authorised Cloud Environment provisions before deploying |
| Environment | Licensing Calculation | Licences for 8-Core Workload |
|---|---|---|
| On-premises (Intel, hard partition) | Physical cores x 0.5 core factor | 8 x 0.5 = 4 Processor licences |
| VMware (soft partition, 4-host cluster) | All host cores x 0.5 core factor | 128 x 0.5 = 64 Processor licences |
| OCI (BYOL) | OCPUs / 2 (1 licence per 2 OCPUs) | 8 / 2 = 4 Processor licences |
| AWS/Azure (BYOL) | vCPUs x 0.5 core factor | 8 x 0.5 = 4 Processor licences |
Named User Plus licensing on third-party cloud providers follows the same rules as on-premises. The licence count is based on the number of named users accessing PeopleSoft, not the underlying infrastructure. This makes NUP licensing in cloud environments straightforward and avoids the vCPU counting complexity that affects Processor licensing. However, the NUP minimum per Processor still applies. Organisations deploying on AWS, Azure, or GCP should also verify that their Oracle licence agreements include the Authorised Cloud Environment provisions. Older contracts may not include these terms.
The Oracle Database that underpins PeopleSoft is licensed separately from the PeopleSoft application itself. Database licensing cost frequently exceeds the PeopleSoft application licensing cost, particularly when Enterprise Edition with options such as RAC, Partitioning, Advanced Security, or Diagnostics and Tuning Packs is deployed.
| Database Licensing Factor | Detail | Cost Impact |
|---|---|---|
| Oracle Database Enterprise Edition | List price approximately $47,500 per Processor licence. Licensed independently from PeopleSoft application modules | Soft partitioning on VMware can multiply required licences dramatically. A DB VM on a 4-host cluster with 32 cores each could require 64 Processor licences at list = $3M+ |
| RAC (Real Application Clusters) | $23,000 per Processor at list price. Requires licensing on every node in the RAC cluster | RAC adds $23,000 per Processor on top of the base database licence. On a VMware cluster this compounds with the soft partitioning multiplier |
| Partitioning | $11,500 per Processor at list price | Additional per-Processor cost stacked on base licence and RAC |
| Advanced Security / Diagnostics and Tuning | Additional per-Processor options frequently deployed with PeopleSoft | Each option is licensed per Processor and multiplied by the same soft partitioning rules |
| Combined VMware exposure | Database EE + RAC + Partitioning on a standard 4-host VMware cluster | Can exceed $5M for a single PeopleSoft database instance. This is the single largest compliance risk in most PeopleSoft estates |
Organisations should evaluate whether the Oracle Database tier specifically should be moved to OCI (gaining the 2:1 OCPU advantage and eliminating soft partitioning), deployed on Oracle VM (qualifying for hard partitioning), or hosted on dedicated physical servers outside the VMware cluster. The database tier and application tier do not need to be on the same infrastructure. Separating them is a common and well-established architecture pattern. The high-cost database tier gets isolated on licence-optimised infrastructure while the application tier, where per-core costs are typically lower, may remain on VMware with a more manageable licensing impact.
The PeopleSoft application tier comprises the application server, web server, Process Scheduler, and Elasticsearch/Kibana components. It is licensed based on the PeopleSoft application modules deployed and the licence metric (NUP or Processor). The same virtualisation rules apply but cost impact per core is typically lower because PeopleSoft application Processor licence prices are generally lower than Oracle Database Enterprise Edition.
| Component | Licensing Requirement | Key Consideration |
|---|---|---|
| PeopleTools | Included with PeopleSoft application licences. No separate licensing required when used exclusively to support licensed PeopleSoft modules | If PeopleTools components (Integration Broker, Application Engine) provide services to non-PeopleSoft applications, additional licensing considerations may apply |
| Application Server | Licensed as part of the PeopleSoft application modules. Same metric and virtualisation rules apply | Deploy on same licensed infrastructure as PeopleSoft applications. Ensure integration services are accounted for |
| Web Server (PIA) | Typically included in the PeopleSoft application licence. No separate Oracle licensing required | Underlying OS and any middleware deployed on the web tier may have their own licensing requirements |
| Process Scheduler | Licensed as part of the application tier | Runs batch processes that may require significant compute. Right-size vCPU allocation to minimise core-based licence calculations |
| Elasticsearch/Kibana | Open source components. No Oracle licensing required for the search engine itself | Infrastructure hosting Elasticsearch may still require OS licensing. Separate from Oracle-licensed tiers if possible |
Oracle requires licensing for all PeopleSoft installations, including development, test, QA, staging, training, and disaster recovery environments. There is no automatic exemption for non-production use.
| Non-Production Rule | Detail |
|---|---|
| Full licensing required by default | Every instance of Oracle Database and PeopleSoft application running in a non-production environment requires licence entitlements unless a specific contractual provision applies. This includes dev, test, QA, staging, training, and DR |
| NUP minimums still apply | Even in non-production environments, Oracle's minimum Named User Plus requirements per Processor apply. For Oracle Database Enterprise Edition, the minimum is 25 NUP per Processor. For PeopleSoft applications, module-specific minimums apply |
| Development licence discounts available | Oracle offers discounted development and test licences through its price list at reduced rates. These carry restrictions: no production workloads, no live business data, no end-user access. Availability and pricing should be confirmed during contract negotiations |
| Negotiate non-production provisions | During licence purchases, ULA negotiations, or contract renewals, negotiate explicit provisions: specified non-production environments at no additional cost, or discounted licensing for dev and test instances. Document in the contract for audit-safe coverage |
| Disaster recovery considerations | Oracle's DR policy requires full licensing for active DR instances (hot standby) but permits a 10-day annual testing allowance for cold or warm failover environments. Specific terms depend on the Oracle licence agreement and any DR provisions negotiated |
Non-production licensing can double or triple the total PeopleSoft licence requirement if not managed proactively. During Oracle licence purchases, ULA negotiations, or contract renewals, always negotiate explicit non-production provisions. Document DR environment classifications and test schedules for audit evidence. Right-size non-production VM allocations to minimise core-based licence calculations.
The choice between Named User Plus and Processor licensing has significant cost implications for PeopleSoft in virtualised and cloud environments. The optimal metric depends on the relationship between the number of PeopleSoft users and the infrastructure footprint.
| Factor | Named User Plus (NUP) | Processor |
|---|---|---|
| Virtualisation impact | Immune to the soft partitioning multiplier. User count does not change based on infrastructure architecture | Directly affected by soft partitioning. VMware can multiply required licences by 10x to 30x |
| Cost scaling | Scales linearly with user count. A 500-user PeopleSoft HCM deployment costs the same whether it runs on a single server or a 20-host VMware cluster | Scales with core count and infrastructure architecture. Cost-effective when user population is very large relative to infrastructure footprint |
| Best for | Relatively few PeopleSoft users on large VMware clusters. Dramatic savings possible because user count is unaffected by virtualisation | Large user populations (thousands) on compact, hard-partitioned infrastructure where NUP costs scale linearly but core count is contained |
| Administrative burden | Requires accurate user counting and ongoing management. Must track named users across all environments | Infrastructure-based. Requires accurate inventory of cores, hosts, and virtualisation topology |
| Switching metrics | Switching between metrics after initial purchase requires negotiation with Oracle and may involve true-up costs or unfavourable commercial conditions. The metric decision should account for long-term infrastructure strategy | |
Organisations should model both NUP and Processor against their actual user counts and infrastructure configurations, including the full soft partitioning implications for Processor licensing, before committing to a licensing approach. The crossover point depends on the specific PeopleSoft modules, their NUP and Processor list prices, the infrastructure architecture, the NUP minimum requirements per Processor, and any negotiated discount levels. Make this decision with a long-term infrastructure strategy in mind, accounting for planned virtualisation changes, cloud migration timelines, and expected user growth.
The most effective strategies target the three largest cost drivers: virtualisation architecture (particularly the database tier), licence metric selection, and non-production environment management.
| Strategy | Impact | Detail |
|---|---|---|
| Isolate PeopleSoft from VMware clusters | High | The single highest-impact optimisation. Deploy PeopleSoft (particularly the Oracle Database tier) on dedicated physical hosts, Oracle VM, or OCI. Eliminates the soft partitioning cost multiplier that can increase licensing by 10x to 30x. Even if the rest of the estate stays on VMware, isolating Oracle workloads saves millions |
| Evaluate OCI migration for database tier | High | Migrating the Oracle Database tier to OCI eliminates soft partitioning and gains the 2:1 OCPU ratio, halving the Processor licence requirement. The application tier can remain on existing infrastructure. Oracle's PeopleSoft Cloud Manager simplifies OCI deployment. The database tier is typically the easiest component to migrate |
| Right-size virtual machine allocations | Medium | For hard-partitioned or cloud environments where licensing is based on allocated cores, reducing vCPU allocations directly reduces licence requirements. Many PeopleSoft environments are over-provisioned. Reducing from 8 to 4 vCPUs in a hard-partitioned environment halves the Processor licence requirement for that tier |
| Select the optimal licence metric | Medium | Model NUP vs Processor against actual user counts and full infrastructure configuration including soft partitioning implications. For organisations with few users on large VMware clusters, switching to NUP can eliminate millions in Processor licensing exposure |
| Negotiate non-production and DR provisions | Medium | Negotiate explicit non-production terms during every Oracle contract event. Discounted dev/test licences, included non-production environments, and documented DR testing allowances reduce total licensing cost by 30-50% for the non-production estate |
| Conduct regular infrastructure reviews | Ongoing | Infrastructure changes such as VMware cluster expansions, host additions, or cloud migrations may have been implemented without considering Oracle licensing implications. Regular reviews identify new risks before they become audit findings |
Yes. Oracle classifies VMware as soft partitioning, which means the organisation must licence all physical cores on every host server where the PeopleSoft VM could potentially run, not just the cores allocated to the VM. In a VMware cluster with vMotion enabled, this can mean licensing all cores across all hosts. This is Oracle's most impactful virtualisation policy. The only ways to avoid it are using Oracle-recognised hard partitioning technologies, deploying on dedicated physical servers, or migrating to Oracle Cloud Infrastructure.
Oracle Cloud Infrastructure provides two significant advantages. First, each Processor licence covers two OCPUs (versus one physical core on-premises), effectively halving the licence requirement. Second, OCI eliminates the soft partitioning issue entirely because licensing is based on the OCPUs allocated to your instance, not the underlying physical infrastructure. Combined, these advantages can reduce PeopleSoft Processor licensing costs by 50% or more compared to on-premises VMware deployments.
Yes. Oracle's Authorised Cloud Environment policy permits BYOL to AWS, Azure, and Google Cloud. However, the licensing terms are less favourable than OCI: each vCPU counts as one core (with the applicable core factor), compared to OCI where one licence covers two OCPUs. Organisations should compare total cost of ownership across cloud providers, factoring in both infrastructure costs and Oracle licensing implications. Verify that your Oracle agreement includes the Authorised Cloud Environment provisions, as older contracts may not.
Yes. The Oracle Database that supports PeopleSoft is licensed independently from the PeopleSoft application modules. It follows its own metric rules, pricing, and virtualisation policies. The database tier frequently represents the largest single licensing cost in a PeopleSoft deployment, particularly when Enterprise Edition with options such as RAC, Partitioning, or Advanced Security is used. Evaluate database and application tier licensing separately and consider different infrastructure strategies for each.
Yes. Oracle requires licensing for all PeopleSoft and Oracle Database installations, including development, test, QA, staging, and training environments. There is no automatic non-production exemption. Manage costs through negotiated contractual provisions (included non-production environments), discounted development licences from Oracle's price list, right-sized VM allocations, and environment rationalisation to minimise the number of non-production instances.
The optimal metric depends on the ratio of PeopleSoft users to infrastructure cores. NUP is typically more cost-effective when the user population is small relative to the infrastructure footprint, particularly in VMware environments where Processor licensing is affected by the soft partitioning multiplier. Processor may be more cost-effective for large user populations on compact, hard-partitioned infrastructure. Model both metrics against actual user counts and infrastructure configurations before committing.
Oracle's core factor is a multiplier applied to physical cores to determine the number of Processor licences required. The factor varies by CPU architecture. Intel and AMD processors typically have a core factor of 0.5, meaning each physical core requires half a Processor licence. Oracle SPARC processors have a core factor of 0.25 or 0.5 depending on the model. The core factor applies to PeopleSoft application licensing and Oracle Database licensing independently. For a 16-core Intel server, the requirement would be 16 x 0.5 = 8 Processor licences per licensed product.
Oracle Linux KVM has been recognised as an approved hard partitioning technology since 2020, providing the same licensing benefit as Oracle VM (OVM). You licence only the vCPUs allocated to the PeopleSoft VM, not the entire physical host. Must be Oracle Linux KVM specifically, not upstream QEMU/KVM on other distributions. CPU pinning must be configured and documented. Both OVM and Oracle Linux KVM are viable options for eliminating the VMware soft partitioning cost multiplier.
Yes. This is a common and well-established architecture pattern specifically used to optimise Oracle licensing costs. The database tier (highest per-core cost) can be isolated on OCI, Oracle VM, or dedicated physical hosts to eliminate soft partitioning exposure, while the application tier (lower per-core cost) remains on VMware with a more manageable licensing impact. This split-tier approach is one of the most effective PeopleSoft licensing optimisation strategies.
Maintain accurate and current documentation of: virtualisation configurations (which hosts, which hypervisor, CPU pinning if applicable), VM affinity rules, licence entitlements for each tier, non-production environment inventory with DR classifications and test schedules, user counts for NUP-licensed products, and a mapping of every PeopleSoft and Oracle Database installation against your licence inventory. Regular reviews identify risks created by infrastructure changes before they become audit findings. See: PeopleSoft Compliance and Audit Best Practices.
Redress Compliance provides independent Oracle and PeopleSoft licensing assessment, audit defence, virtualisation strategy, cloud migration advisory, and contract negotiation. No Oracle partnerships, reseller relationships, or referral arrangements. Vendor-independent. Fixed-fee engagements.
Oracle Licence Management ServiceIndependent PeopleSoft licensing advisory. Virtualisation compliance. Cloud migration strategy. Audit defence. Contract negotiation. 100% vendor-independent, fixed-fee engagement.