Oracle UPK (User Productivity Kit) may be end-of-life, but its licence requirements remain fully enforceable. This guide covers UPK's licensing metrics, Standard vs Professional pricing, pre-built content module costs, common compliance pitfalls, and strategic end-of-life planning for ITAM professionals, CIOs, and procurement teams still managing legacy UPK deployments.
This guide is part of our Oracle Applications Licensing series. For related guides, see: Oracle E-Business Suite Licensing | Oracle PeopleSoft Licensing | Oracle Technology Price List Guide.
Oracle UPK (User Productivity Kit) is a software tool used to create training materials, simulations, and in-application help for enterprise systems. It has historically helped organisations accelerate user adoption for Oracle E-Business Suite, PeopleSoft, and other enterprise applications by providing interactive guides and documentation.
| Status | Detail |
|---|---|
| Product status | Oracle officially discontinued new development of UPK and ended Premier Support in late 2022. No new features, updates, or patches are planned |
| Remaining support | Only sustaining support (limited technical assistance without new fixes) remains available, if at all. No new bug fixes or security patches |
| Licence enforcement | Oracle's licence audit rights remain fully in effect for UPK. Compliance cannot be neglected. Your usage must still comply with the licences you own |
| Current deployment | UPK is still widely deployed in enterprises running Oracle E-Business Suite, PeopleSoft, and JD Edwards. Many organisations continue active use even without Oracle support |
| Audit risk | Oracle can audit historical and current UPK usage at any time. Non-compliance could result in costly true-up fees regardless of the product's age or end-of-life status |
For ITAM professionals, the end-of-life status elevates the importance of managing existing UPK licences carefully. The software remains in active use at many organisations even without Oracle support, and Oracle can audit historical and current usage at any time. Non-compliance could result in costly true-up fees regardless of the product's age. If your organisation uses Oracle E-Business Suite, PeopleSoft, or JD Edwards with integrated UPK content, you need to understand how UPK is licensed.
Oracle UPK licensing is based on three core metrics. Understanding these is critical for proper compliance. The most common audit finding is under-counting authorised users, because Oracle's definition of "authorised" is broader than most organisations expect.
| Metric | Who Is Counted | Minimum | Key Compliance Rule |
|---|---|---|---|
| UPK Developer | Each individual who authors or develops content in UPK. Every person who installs and uses the UPK developer client to record or create training content needs a licence | 1 licence | Applies to both Standard and Professional editions. If you have 5 instructional designers creating simulations, you need 5 Developer licences, even if not all are active simultaneously |
| Application User | Each end user authorised to access UPK content, whether or not they actually use the training materials. Based on authorised users, not concurrent usage | 50 licences | If 200 employees have access to an Oracle ERP system integrated with UPK help, you must licence 200 Application Users, even if only 100 actually use the training content |
| Employee | All employees (including FTEs and contractors) for enterprise-wide deployment. A broader metric covering the entire organisation or a defined subset | 500 licences | If using the Employee metric, you count every employee including full-time equivalents and contractors. This approach is most cost-effective for very large user bases where counting individual named users is impractical |
Oracle requires at least 1 Developer licence, 50 Application User licences, and 500 Employee licences. If you only have 30 end users needing UPK content, Oracle's terms still require you to buy 50 Application User licences. These minimums exist regardless of your actual user count. For context on how Oracle applies minimum licensing requirements across its product line, see: Oracle Technology Price List Guide.
Oracle UPK comes in two editions, Standard and Professional, with identical licensing metrics but different pricing. The Professional edition includes additional features (multi-language support, LMS integration, UI customisation) beyond what Standard offers.
| Edition | Metric | Licence Price (USD) | Annual Support (USD) | Min Qty |
|---|---|---|---|---|
| UPK Standard | UPK Developer (per developer) | $17,500 | $3,850 | 1 |
| UPK Standard | Application User (per named user) | $90 | $19.80 | 50 |
| UPK Standard | Employee (per employee) | $45 | $9.90 | 500 |
| UPK Professional | UPK Developer (per developer) | $17,500 | $3,850 | 1 |
| UPK Professional | Application User (per user) | $100 | $22.00 | 50 |
| UPK Professional | Employee (per employee) | $50 | $11.00 | 500 |
Choosing between Application User and Employee metrics can significantly impact costs. If you have thousands of users, paying per named user ($90-$100 each) may be more expensive than an enterprise-wide Employee metric ($45-$50 per employee). But the Employee metric requires counting all staff. ITAM managers should analyse which metric yields the lowest total cost for their user base. Oracle's list prices are often negotiable, especially since UPK is no longer a strategic product for Oracle. Volume discounts or legacy product discounts may be available.
In addition to the base UPK software, Oracle offered pre-built UPK content modules for many of its applications (Oracle E-Business Suite modules, Hyperion, PeopleSoft, and others). These are packaged training content libraries that Oracle developed to save time in creating documentation from scratch.
| Organisation Size | Example Module Cost | Annual Support | Notes |
|---|---|---|---|
| Up to 4,000 employees / $1B revenue | Approximately $35,000 per module | Approximately $7,700 | Smaller tier. Some modules for smaller applications priced as low as approximately $8,800 |
| Over 4,000 employees / $1B revenue | Approximately $70,000 per module | Approximately $15,400 | Larger tier. More complex suites cost tens of thousands of dollars per module |
The licensing uses a "UPK Module" metric, which is essentially a flat licence fee per module. Once you licence a module, you can use the pre-built content internally for your users. There is no per-user metric on the content itself.
These modules require that you have the corresponding Oracle application licensed. They are meant to accelerate training for software you have already licensed. They are strictly for internal use. You cannot legally redistribute Oracle's content outside your organisation or use it for training external clients without permission. ITAM professionals should inventory any UPK content modules and verify they are still needed, given their high cost and UPK's end-of-life status.
These common pitfalls have exposed enterprises to audit findings and unexpected costs. Each one is preventable with proper planning and licence governance.
| Pitfall | Risk | How to Avoid |
|---|---|---|
| Under-counting authorised users | Licensing only active UPK users rather than all authorised users. Oracle's definition is broad: even if a user has never launched UPK help, if they have access to the system with UPK content, they need coverage | Always licence based on the full scope of potential users, not just those who actively use training content. Count every user with access to UPK-integrated applications |
| Ignoring minimum licence requirements | Purchasing fewer than the minimum (50 named users, 500 employees) violates Oracle's terms even for small deployments | Meet the minimum licensing quantities regardless of actual user count. The minimums are contractual requirements, not suggestions |
| Confusing User vs Employee metrics | Misinterpreting the Employee metric as a way to exclude certain users. If licensed by Employee, typically every employee counts | If covering only a subset of users, use Application User. If enterprise-wide, ensure you switch to Employee and count all staff including contractors and FTEs |
| Unlicensed content developers | Focusing on end users while forgetting anyone who uses the UPK Developer tool. Any business analyst, trainer, or IT staff who authors content needs a Developer licence | Audit who has the UPK Developer tool installed or has accessed developer functionality. Every content creator needs a Developer licence regardless of their job title |
| Not accounting for external users | If UPK content is accessible via supplier portals or partner interfaces, external parties may need licensing. Standard metrics generally cover internal use only | Clarify external user licensing requirements with Oracle. Special arrangements may be needed for any non-employee access to UPK content |
| Assuming UPK is "free" post-EOL | Some assume that because Oracle stopped developing UPK, licensing is no longer enforced. This is false. Oracle can audit historical and current usage at any time | Treat UPK licensing as an active compliance obligation. Maintain documentation and usage data throughout the product's remaining lifecycle in your environment |
Oracle's audit teams can and do review legacy product usage. During any Oracle licence audit, whether triggered by an EBS review, a ULA certification, or a broader compliance check, UPK usage may be examined. Having your user counts, developer records, and licence documentation organised is your best defence. For a complete guide to Oracle's audit process, see: Oracle Licence Audits: A Strategic Guide for CIOs.
With Oracle UPK now in end-of-life status, ITAM professionals should take a proactive approach. The end-of-life creates both challenges and opportunities.
| Strategic Area | Detail | Action |
|---|---|---|
| Support renewal evaluation | If you are still paying annual support on UPK licences, question what you are receiving. Oracle no longer provides patches or new content. Support may only grant access to old knowledge bases | Negotiate with Oracle to repurpose those support dollars toward other products or cloud services. Oracle sales teams are often amenable to converting on-prem support into cloud credits or discounts on newer software for legacy products |
| Freezing or reducing licence scope | Since no new UPK features are coming, many organisations have stopped expanding usage. If your user count is decreasing as you retire old systems, you may be able to terminate some licences or avoid renewing support on unused ones | Be mindful of Oracle's rules around support cancellation (typically you cannot drop support on a subset without penalty), but since UPK is end-of-life, Oracle may allow flexibility. Always check the contract before making changes |
| Audit readiness | End-of-life does not mean Oracle will not audit. Oracle can review UPK usage during any broader licence compliance check | Keep records of the number of users authorised for each system with UPK content, plus the names of UPK developers. If your organisation has scaled down usage, ensure the number of licences owned covers peak usage during the audited period |
| Transition planning | Align your UPK licence strategy with your transition timeline. If decommissioning UPK in two years, you might decide not to renew support and accept using it "as-is" for that period | Develop a high-level migration plan. Identify alternative tools and assign a timeline. Renew UPK support only until migration is complete, then sunset the licences |
Oracle's UPK end-of-life creates negotiation opportunities you would not have with active products. Ask about discounts, credits toward Oracle Guided Learning or cloud subscriptions, or the ability to drop support without standard penalties. Oracle may be willing to be flexible to maintain goodwill and future business. For negotiation strategies with Oracle, see: Oracle Contract Negotiation Service.
These recommendations apply to any organisation still running Oracle UPK, whether you plan to keep it for another year or five years.
| Recommendation | Detail |
|---|---|
| Audit your UPK deployment | Conduct a thorough internal audit of where UPK is installed, who uses the Developer tool, and which applications have UPK content enabled. Map your licence requirements and identify any gaps before Oracle does |
| Match licences to usage | Ensure sufficient Application User licences for every user with access to UPK-guided applications. Document any excess for potential renegotiation, but never under-licence actual usage |
| Evaluate Named User vs Employee licensing | For large enterprises, periodically assess whether the Employee metric would reduce costs. If your UPK user base approaches the entire company, switching to Employee-based licensing may save money significantly |
| Leverage EOL in negotiations | Use UPK's end-of-life as a discussion point with Oracle. Ask about credits toward newer solutions, the ability to drop support without penalties, or discounts on Oracle Guided Learning subscriptions |
| Consider third-party or self-support | If you need to keep UPK running but do not want to pay Oracle's support fees, explore whether third-party support providers cover UPK, or ensure your team can self-support with no new patches expected |
| Begin transition to alternatives | Do not invest in expanding UPK. Evaluate alternatives: Oracle Guided Learning (OGL) for Oracle Cloud apps, or independent digital adoption platforms like WalkMe, Whatfix, or uPerform. Having an alternative eliminates the compliance concern entirely |
| Keep documentation of entitlements | Maintain copies of Oracle UPK licence agreements, proof of purchases, and support renewals. These documents are your defence in any audit dispute. Store them where they can be accessed quickly if needed |
Five actions every organisation running Oracle UPK should take immediately.
| # | Action | Detail |
|---|---|---|
| 1 | Inventory your UPK users and developers | Gather data on how many content developers (authors) you have and how many end users have access to UPK-driven content. Use HR records or system access logs to identify all individuals with such access |
| 2 | Verify licence counts vs Oracle agreements | Cross-check your inventory against purchased licences in each category (Developer, Application User, Employee). Confirm you meet minimum requirements and note any shortfalls or excesses |
| 3 | Review support contracts | Check when your UPK support renewal is due and what you are paying. Decide if continuing support is justified given the end-of-life status. If you plan to drop support or reduce licences, prepare to discuss with your Oracle account manager in advance |
| 4 | Engage stakeholders | Discuss with IT training leaders and application owners how long they plan to keep using UPK. Ensure everyone knows it is unsupported after 2022. Build urgency around migrating to new solutions |
| 5 | Plan a migration timeline | Develop a high-level plan for replacing UPK. Identify alternative tools, start a pilot evaluation, and assign a timeline for content migration. This guides your licence strategy: renew UPK support only until the migration is complete, then sunset licences |
Oracle has ceased active sales and development of UPK. Premier Support ended in December 2022. You can continue to use existing licences indefinitely (perpetual), and you may receive only sustaining support if you maintain a support contract. No new UPK versions will be released. However, your existing licences remain valid and Oracle's audit rights remain fully enforceable.
If you use UPK strictly as an authoring tool and distribute static outputs (PDF manuals, printed guides), those end readers typically do not need UPK user licences. The Application User licensing primarily applies when users access interactive UPK content (via the UPK Player or in-app help integration). Clarify with Oracle if in doubt, but in practice, reading a PDF generated by UPK would not constitute using the UPK software.
The licence metrics (Developer, Application User, Employee) are the same for both editions, but the cost per user is slightly higher for Professional ($100 vs $90 per Application User, $50 vs $45 per Employee). Functionally, UPK Professional offers more features including multi-language support and LMS integrations. If you have Standard and need those features, you can upgrade by paying the licence fee difference. Keep track of which edition you own, as mixing them may have implications for support.
Yes. Oracle reserves the right to audit customers' use of any of its software, whether active or legacy. An audit can check if you have more UPK developers or users than you have licensed. UPK is still part of your licence agreement. Always remain audit-ready by keeping usage data and licence proof organised. UPK usage may be examined during any broader Oracle compliance check, including EBS reviews or ULA certifications.
Many enterprises are migrating to modern digital adoption platforms. Oracle offers Oracle Guided Learning (OGL) for its cloud applications, essentially the cloud-era answer to UPK. Third-party options include WalkMe, Whatfix, Pega Knowledge, and Ancile uPerform. The best choice depends on your application landscape (on-premise vs cloud) and budget. Evaluate these options sooner rather than later, since UPK's shelf life is limited and investing in expansion makes no strategic sense.
Oracle's definition of "authorised user" for UPK is broad. It includes any individual who has access to a system where UPK content is integrated, regardless of whether they actually use the training materials. If 500 employees have access to an Oracle EBS system with UPK in-app help enabled, all 500 are considered authorised users who need Application User licences, even if only 50 regularly access the UPK content. This is one of the most common audit findings.
You can choose not to renew support, which means you lose access to Oracle's knowledge base and any sustaining support services. Your perpetual licence remains valid. However, be aware of Oracle's reinstatement policy: if you drop support and later want to resume it, Oracle may charge a reinstatement fee (typically 150% of the back support you missed). Since UPK is end-of-life with no new patches coming, many organisations choose to drop support and self-maintain.
Pre-built content modules are licensed separately from the UPK software itself, using a flat "UPK Module" fee based on organisation size. They require that you have the corresponding Oracle application licensed (e.g., you need an EBS licence to use the EBS UPK content module). The content is for internal use only and cannot be redistributed. You still need UPK Developer licences for anyone modifying the pre-built content, and Application User or Employee licences for anyone accessing it.
Absolutely. UPK's end-of-life status gives you negotiation leverage. Include UPK in broader Oracle renewal or new purchase discussions. Ask about credits toward Oracle Guided Learning or cloud subscriptions, the ability to drop support without standard penalties, or discounts that reflect the product's discontinued status. Oracle sales teams have discretion to make concessions on legacy products, especially when the discussion is part of a larger deal. See: Oracle Contract Negotiation Service.
UPK was designed for on-premises Oracle applications. If you migrate to Oracle Cloud applications (Fusion ERP, HCM, CX), UPK is not the designated training tool. Oracle Guided Learning (OGL) is the cloud equivalent. Your existing UPK licences remain valid for any on-premises applications you continue to run. However, you cannot use UPK for Oracle Cloud applications. Plan your UPK sunset to align with your cloud migration timeline.
Whether you are managing legacy UPK deployments, planning a transition to modern digital adoption tools, or preparing for an Oracle audit covering application licences, our Oracle licensing specialists can help you optimise costs and eliminate compliance risk. Every recommendation is made purely in your commercial interest. We have no relationship with Oracle.
Oracle Licence Management ServiceIndependent Oracle licensing advisory. Compliance assessment. Audit defence. Legacy product strategy. 100% vendor-independent, fixed-fee engagement.