An Oracle Unlimited License Agreement (ULA) is a commercial program overlay, not a license metric. The Oracle License Definitions and Rules booklet (effective 15 June 2024) defines Processor, Named User Plus, Employee, and other metrics for covered Programs; it does not define ULA or PULA as metrics.[1] The strongest sourced ULA rule in the retrieved PDFs is in Licensing Oracle Software in the Cloud Computing Environment (as of 12 June 2024): licenses acquired under unlimited license agreements (ULAs) may be used in Authorized Cloud Environments, but customers may not include those licenses in the certification at the end of the ULA term.[2]
Editions
ULA and PULA are not commercial editions of a Program. Edition lists for Database, Java SE, WebLogic Server, and VirtualBox live on those encyclopedia pages. The Oracle Technology Global Price List dated 3 August 2026 is marked educational only and does not name ULA or PULA as products, SKUs, or metrics.[3]
Metrics
A ULA is not a metric, and the catalog has no ULA metric row. Metrics stay those of the Programs listed in the ordering document: Processor, Named User Plus, Employee, and the other metrics named in License Definitions (effective 15 June 2024).[1]
Oracle Cloud Infrastructure License Manager documentation (a tracking console, not a license grant) records Oracle product licenses against Processors or Named User Plus. Separately, it lets the operator mark a license record as unlimited (Unlimited License Agreement licenses) versus a specific count (Full Use licenses), and as Perpetual or Term-Limited.[4] That UI split is consistent with ULA being a quantity overlay on an existing metric, not a replacement metric. It is not a source for certification math.
Counting
The ACE policy names a “certification at the end of the ULA term” and excludes ACE-used ULA licenses from that certification. It does not publish a certification formula, a remaining-term true-up, or a conversion quantity.[2] No ULA- or PULA-specific floor, rounding rule, or SKU math is stated in the License Definitions booklet or the Technology Global Price List.[1][3]
Virtualization
The retrieved License Definitions booklet, ACE policy, and Technology Global Price List do not state a ULA-specific virtualization or partitioning rule. Partitioning and virtualization for the underlying Programs are covered on the Program encyclopedia pages, not by this overlay.
Cloud
That policy applies to Amazon Web Services Amazon Elastic Compute Cloud (EC2), Amazon Relational Database Service (RDS), Microsoft Azure Platform, and Google Cloud Platform (GCP), collectively Authorized Cloud Environments (ACE).[2]
Quoted ACE rule (as of 12 June 2024): “Licenses acquired under unlimited license agreements (ULAs) may be used in Authorized Cloud Environments, but customers may not include those licenses in the certification at the end of the ULA term.”[2]
ACE Processor and Named User Plus counting for those environments (including that the Oracle Processor Core Factor Table is not applicable when counting Processor licenses in ACE) remains the counting method for the underlying Programs. It is not a ULA metric and is not restated here as ULA math.[2]
ACE names ULAs only. It does not name PULA, and it does not say whether a perpetual unlimited overlay is certified at term-end. Do not extend the ACE certification exclusion to PULA from this PDF.
An Oracle Global Licensing Advisory Services (GLAS) corporate page names the Unlimited License Agreement as a vehicle that deploys specified Oracle software across on-premises, cloud, and multicloud environments. That page is a GLAS offering page, not a contract, and it is not a source for certification or conversion quantities.[5]
Programs
ULA. In the ACE policy, Oracle writes “unlimited license agreements (ULAs)” and pairs that name with an end-of-term certification, without defining the overlay as a metric.[2] An Oracle GLAS blog (31 July 2025) describes a ULA as “a contractual arrangement where a customer can purchase the right to deploy and use an unlimited number of specified Oracle software products for a specified period of time.” That blog is not a contract and is not the License Definitions booklet.[6]
PULA. PULA is not named in the License Definitions booklet (effective 15 June 2024), the ACE policy (as of 12 June 2024), or the Technology Global Price List (3 August 2026).[1][2][3] The same GLAS blog defines PULA in one sentence: “A PULA is similar to a ULA except that there is no specified time period. A customer has the right to use the Oracle software perpetually, within the terms and conditions of the contract.”[6] Treat all other PULA terms as contract-specific and unpublished here.
The same blog names Pool of Funds (POF) as a third Enterprise Agreement form. POF terms are unpublished in the retrieved PDFs and are not defined on this page.[6]
Out of scope
- Certification formulas for converting unlimited-term deployments into perpetual Processor, Named User Plus, or other quantities. ACE names certification; it does not publish the math.[2]
- Remaining-term true-up and any conversion quantity. Not in the retrieved PDFs.
- PULA SKU math and PULA contract schedules beyond the one-sentence GLAS blog definition. Contract-specific; unpublished here.
- ASFU (Application Specific Full Use) and other restricted-use labels, unless a retrieved vendor PDF states them for this overlay. The retrieved ULA/PULA PDFs do not.
- Support-stream pricing, typical term length, and “using more costs nothing more” claims. Those are not in the retrieved PDFs.
- White-paper gallery pages titled ULA vs. PULA in this wiki. They are archives, not this encyclopedia article, and were not overwritten.