What cloud deploy rights cover.
Cloud deploy rights are the contractual clauses inside an Oracle Unlimited License Agreement that govern where the unlimited deployment can take place. The default ULA position is that deployment is permitted on customer owned and operated infrastructure. The cloud deploy clause extends this default to permit deployment on authorised cloud providers including Amazon Web Services, Microsoft Azure, Google Cloud Platform, and Oracle Cloud Infrastructure. The specific list of authorised cloud providers varies by ULA and the licensing rules that govern the deployment also vary by cloud provider.
The certification implication.
The cloud deploy clause has a material certification implication. At the end of the ULA term the customer certifies the deployed quantity, which becomes the perpetual entitlement. The certification typically includes both on premises deployment and authorised cloud deployment. The cloud deployment counts toward the certified quantity at a metric that varies by cloud provider. Oracle Cloud Infrastructure deployments typically count one for one. AWS, Azure, and GCP deployments typically count under a formula that includes a multiplier reflecting the vCPU to processor conversion ratio that Oracle publishes for that cloud.
Cloud deploy certification factors
- OCI: one to one conversion in most ULAs. The most generous cloud deploy ratio.
- AWS: 2 vCPUs per processor for licensed cloud regions, with hyper threading considerations.
- Azure: similar 2 vCPUs per processor convention with documented exceptions.
- GCP: 2 vCPUs per processor convention with specific machine type rules.
- Other clouds: typically not authorised in standard ULA cloud deploy clauses.
The negotiation opening.
Cloud deploy rights are negotiable at ULA entry and are routinely improved in well prepared negotiations. The standard Oracle cloud deploy clause permits deployment on authorised cloud providers but applies the published vCPU to processor conversion. Buyer side negotiation can secure improved conversion ratios, expanded provider lists, and inclusion of regions that would otherwise be excluded. Each improvement has a direct material impact on the certifiable quantity at ULA exit.
The single most valuable negotiation move on cloud deploy rights is securing a documented certification methodology for each authorised cloud provider. Oracle's published methodology is updated periodically and the version in force at the date of certification can materially change the outcome. The buyer side response is to fix the certification methodology in the ULA contract so that subsequent changes to the published methodology do not apply to the deployment under this contract.
The deployment strategy.
The cloud deploy clause shapes the buyer's deployment strategy during the ULA term. Customers entering a ULA with the intent to certify out at the end of the term should deploy aggressively on the cloud provider that offers the most favourable conversion ratio under the contract. For most ULAs in 2026 this is OCI for the certification quantity. Customers entering a ULA without intent to certify out and planning to renew the ULA at the end of the term face a different strategic question. The deployment strategy in this case is shaped by the renewal pricing, not by the certification quantity.
The audit interaction.
Cloud deploy rights interact with Oracle audits in two ways. First, the audit can be initiated during the ULA term and is typically focused on products outside the ULA scope. Cloud deployments of in scope ULA products are unlimited under the contract and are not the audit target. Cloud deployments of products outside the ULA scope are licensed under the standard rules and are audited under the standard methodology. Second, the audit at ULA certification is a defined process under the ULA contract and is run by Oracle to verify the certified quantity. The cloud deploy data is part of this certification audit and the documentation requirements are higher than for a standard Oracle audit.
The exit discipline.
The buyer side exit discipline on cloud deploy rights begins twelve months before the certification date. The discipline covers the deployment inventory, the certification methodology documentation, the cloud provider attestations, and the buyer side rehearsal of the certification submission. The rehearsal runs the Oracle certification scripts internally before submission and produces a buyer side certified quantity that is compared against the Oracle script output. Discrepancies are resolved before the formal submission. This rehearsal process has prevented certification disputes in every engagement where we have run it.
Related resources.
- ULA Negotiation pillar guide
- ULA Negotiation service
- ULA deal type page
- OCI product page
- The ULA Exit Framework 49 page reference paper.
- Oracle ULA True Up Process related sub article.