Oracle PeopleSoft Licensing:The Complete Buyer-Side Guide for 2026

Short answer: PeopleSoft licensing is a modular, per-user model. Each application suite is bought separately and metered on Named User Plus, Application User, or Concurrent User counts, with a 25 NUP per processor floor. Technology underneath PeopleSoft is never bundled in — it is licensed on its own.

Oracle PeopleSoft is an on-premises enterprise applications suite that Oracle acquired in 2005 and continues to sell and support. It is licensed by application module: HCM (Human Capital Management), FSCM (Financial and Supply Chain Management), CRM (Customer Relationship Management), and Campus Solutions (higher education). Each module is an independent license grant — you own rights only to what you have explicitly purchased.

The default metric is Named User Plus (NUP). A Named User Plus is an individual authorized to use the program, whether or not they are actively using it at any given time. PeopleSoft NUP carries a minimum of 25 NUP per processor where a processor-based floor applies, which sets a hard cost baseline for any deployment. Some modules can alternatively be licensed on a Concurrent User or Application User metric, each with its own counting rules and price multiplier.

Critically, the PeopleSoft license grant covers PeopleTools and the application code only. It does not include Oracle Database, Oracle WebLogic Server, or any Oracle Database options. Those are separate products under Oracle's standard technology metrics and standard audit rules. Treating the database and middleware as "part of PeopleSoft" is one of the most common — and most expensive — budgeting mistakes we see. For the underlying database rules, our Oracle Database Licensing Guide is the companion reference to this page.

Oracle also sells bundled "PeopleSoft Enterprise" agreements that combine multiple modules at a 15-20% discount to buying each one separately. For multi-module estates, negotiating a bundle at renewal is a primary cost lever — but only after you have audited which modules you actually run in production.

Short answer: Named User Plus counts everyone authorized to access PeopleSoft, including self-service employees who never "log in" in the traditional sense. Concurrent User counts only peak simultaneous sessions and can cut cost 40-70% where total population dwarfs concurrency.

The metric you choose determines both your cost and your audit exposure. Named User Plus is the default, and it counts every authorized individual — HR professionals, managers approving timesheets, contractors, and the entire self-service population. Self-service employees viewing payslips, submitting expenses, or requesting absence all count as named users, and they typically make up 60-80% of the total. Organizations that licensed PeopleSoft in the 1990s and 2000s frequently never counted them, which is exactly what Oracle's LMS scripts surface during an audit.

Concurrent User licensing counts only the peak number of simultaneous sessions. It suits estates with a huge user population but low simultaneity — 10,000 self-service employees but only 400 concurrent sessions at payroll peak. The CU unit price runs roughly 10x the NUP price, but where concurrency is a fraction of headcount, CU can reduce cost by 40-70%. The break-even is simple: if (peak concurrent count × 10) is less than your total named user count, Concurrent User wins.

We break down the full metric comparison, the counting traps, and the self-service exemption arguments in the dedicated spoke: PeopleSoft User Licensing: Named vs Concurrent. For HCM-specific employee metrics, see PeopleSoft HCM Licensing & Employee Metrics.

Short answer: Every PeopleSoft pillar is a separate license grant. Sub-modules within a licensed pillar are usually included, but add-on products such as Talent Management, Absence Management, and Time & Labor are licensed separately — and enabling them without a grant is a standard audit finding.

PeopleSoft modules are independent. Running FSCM grants no rights to HCM; running HCM grants no rights to CRM. Within a licensed pillar, core sub-modules generally come along — license HCM and you can run Payroll and Compensation — but extension products are sold on top. The architecture makes it dangerously easy to switch on functionality you have not licensed, and Oracle's LMS team is practised at finding it years later and back-assessing both the license and the support owed on it.

Campus Solutions deserves special mention because higher-education institutions license it under distinct rules, often tied to student records and enrollment volumes rather than employee counts. We cover those mechanics in PeopleSoft Campus Solutions Licensing for Higher Ed. The defensive posture for every module is the same: audit your running instance quarterly, align security roles to license grants, and update your agreement in writing before any new module goes live.

Short answer: A PeopleSoft license never includes the database. PeopleSoft runs on Oracle Database — usually Enterprise Edition with RAC and Data Guard — which is licensed and supported on its own, and options such as Diagnostics and Tuning Pack add further separately licensed cost.

PeopleSoft requires Oracle Database for its back end, and that database is a separate license obligation under Oracle's Processor or NUP metrics. Most production PeopleSoft estates run Database Enterprise Edition for the high-availability features PeopleSoft demands — Real Application Clusters for resilience, Data Guard for disaster recovery. Each carries 22% annual support in its own right.

The trap is database options. Diagnostics Pack and Tuning Pack are frequently enabled for performance monitoring and then left running indefinitely, each adding licensable cost per processor. In practice the full Oracle stack — application, database, options, and WebLogic — runs 40-60% above the PeopleSoft application support figure alone. The detail, including how Oracle's USMM and LMS scripts detect option usage, is in PeopleSoft Database Licensing Requirements.

Short answer: There is no hard PeopleSoft shutdown date. Oracle has committed sustained engineering for PeopleSoft 9.2 through at least 2031, with Premium Support running into the early 2030s — but customers face a downgrade to degraded Sustaining Support and constant pressure to move to Fusion Cloud.

Oracle's PeopleSoft roadmap promises "continuous delivery" of selective adoption updates and sustained engineering for 9.2 well into the next decade. That is genuinely reassuring on paper, but the practical issue is the support tier. Premium Support delivers patches, regulatory updates, and proactive fixes. Once a release moves to Sustaining Support — at the same 22% price — you keep security fixes and existing patches but lose new regulatory updates, non-security bug fixes, and enhancements. The product freezes in place while you keep paying full freight.

Oracle's messaging deliberately blurs this line, positioning Sustaining Support as adequate while steering you toward Fusion Cloud HCM and ERP. For most enterprises Sustaining Support is not adequate — payroll and tax regulations change every year. We map the version timeline, the regulatory-update gap, and the realistic options in PeopleSoft End-of-Life & Support Options 2026.

Short answer: The four proven levers are right-sizing the named user count before renewal, switching to independent third-party support for roughly 50% savings, dropping unused modules, and negotiating support caps and true-down rights into the contract.

Right-sizing comes first because it is the lever you fully control. Audit the named user population, remove departed staff, role-changers, and migrated users, document the reduced count, and use that evidence to challenge Oracle's support base at renewal. A reduction from 5,000 to 4,000 named users drops annual support by 20% directly.

Independent third-party support — from providers such as Rimini Street and Spinnaker — delivers a genuine ~50% cut versus Oracle's 22%, typically covering both the PeopleSoft application and the Oracle Database stack under one relationship. It is the right answer for stable estates with no planned Oracle expansion. The transition mechanics, coverage scope, and the BYOL restrictions to watch for are in PeopleSoft Third-Party Support: Options & Savings and our Support Reduction service.

Short answer: Only on your own financial timeline, not Oracle's. Model the full Oracle stack cost over 5-7 years against Fusion subscription plus migration cost — and remember migration is usually 3-5x the annual Fusion subscription and is the most underestimated number in the analysis.

The decision hinges on three figures: your current total Oracle stack cost, the Fusion Cloud HCM/ERP subscription cost, and the one-time migration cost. Fusion's per-user subscription often looks cheaper than PeopleSoft support, but it is not a like-for-like comparison — and the migration itself (implementation, data conversion, customization rework, testing, training) frequently runs 3-5x the annual subscription for complex, heavily customized estates.

Oracle's migration incentives — cloud credits, conversion credits, bundled HCM+ERP promotions — are real but come with strings: multi-year subscription commitments and pressure to use Oracle's own implementation services. Do not let end-of-life marketing or timeline pressure drive the call. The full financial model, the incentive fine print, and the negotiation angles are in PeopleSoft to Fusion HCM Migration Licensing. Use our Contract Negotiation service before signing any Fusion order form.

This pillar is the map. Each topic below has a dedicated, deep-dive guide with the counting rules, audit scripts, and negotiation tactics in full:

• PeopleSoft User Licensing: Named vs Concurrent — the metric mechanics and self-service exemptions.
• PeopleSoft HCM Licensing & Employee Metrics — how headcount drives HCM cost.
• PeopleSoft Database Licensing Requirements — the separately licensed stack.
• PeopleSoft End-of-Life & Support Options 2026 — the support timeline and tiers.
• PeopleSoft Campus Solutions Licensing (Higher Ed) — the education-specific model.
• PeopleSoft to Fusion HCM Migration Licensing — the migration financial analysis.
• PeopleSoft Third-Party Support: Options & Savings — the ~50% support cut.

PeopleSoft is licensed per application module — HCM, FSCM, CRM, and Campus Solutions — each priced on the Named User Plus metric with a 25 NUP per processor minimum, or on Application User or Concurrent User metrics. The underlying Oracle Database, WebLogic, and database options are licensed separately under Oracle's standard technology rules.

Yes. Named User Plus counts every individual authorized to use the application, whether or not they log in. Employee self-service users — payslip viewing, time entry, expenses, absence requests — all count, and they typically represent 60-80% of the total PeopleSoft named user population in a large HCM deployment.

There is no hard shutdown date. Oracle has committed sustained engineering for PeopleSoft 9.2 through at least 2031, with Premium Support running into the early 2030s. The practical risk is a downgrade to degraded Sustaining Support at the same 22% price, plus ongoing pressure to migrate to Fusion Cloud.

Oracle charges 22% of net license value per year for Premium Support on PeopleSoft, and that same 22% continues under the degraded Sustaining Support tier. Independent third-party support providers cut the annual figure by roughly 50% while covering both the application and the database stack.

Yes. A PeopleSoft license grant does not include the right to run Oracle Database. The database (usually Enterprise Edition), WebLogic, and any database options such as Diagnostics Pack and Tuning Pack are each separately licensed and separately supported at 22% per year.

Yes. Right-size your named user count before renewal, switch to independent third-party support for a roughly 50% reduction, drop unused modules, and negotiate support caps and true-down rights. An independent user-population audit before renewal is the highest-impact step and the one Oracle least wants you to take.

Former Oracle licensing and contracts specialist, now working exclusively buyer-side. Reviewed by the Oracle Licensing Experts editorial board.

We identify named user overcounting, module gaps, and support reduction opportunities — before Oracle does. Independent, buyer-side, and built on 600+ engagements.