Oracle WebLogic Cloud Licensing:
ACE BYOL Rules for AWS and Azure, Kubernetes Soft Partitioning, and the VMware Cluster Expansion Trap

Oracle WebLogic on Public Cloud Is One of the Most Audited Areas in Oracle's Portfolio

Oracle WebLogic Server is Oracle's Java EE application server — the middleware layer on which many Oracle applications, custom Java applications, and Oracle Fusion Middleware components run. WebLogic licensing is charged per processor on-premises, using the same processor factor table as Oracle Database, and the cloud licensing rules for WebLogic have historically been among the most contentious and frequently audited areas of Oracle's portfolio. The core issue: WebLogic perpetual licences obtained for on-premises deployments cannot simply be re-used on AWS, Azure, or Google Cloud infrastructure without satisfying Oracle's cloud deployment terms — and many organisations have discovered this only during an Oracle licence review, at which point years of unlicensed cloud deployment have accumulated. This guide covers WebLogic on-premises licensing, the Authorised Cloud Environment (ACE) programme for AWS and Azure BYOL, WebLogic on OCI, WebLogic on Kubernetes, and how the post-Broadcom VMware situation changes the risk calculation for WebLogic on VMware. For virtualisation licensing context, see our Oracle Virtualisation Licensing Guide. For container deployment rules, see our Oracle Container Licensing Guide. For WebLogic middleware licensing review, our Oracle advisory team provides independent Oracle middleware licensing assessments.

WebLogic On-Premises: Processor Licensing

Oracle WebLogic Server on-premises is licensed per processor, with the same core factor table that applies to Oracle Database. WebLogic is offered in two editions with different feature sets and price points:

Annual support is 22% of net licence fees — $1,100/processor/year for Standard Edition, $5,500/processor/year for Enterprise Edition, $9,900/processor/year for WebLogic Suite. A 4-socket Intel server (32 cores, 16 processor licences at 0.5 factor) running WebLogic Enterprise Edition: $400,000 in licence cost and $88,000/year in support. WebLogic Suite on the same server: $720,000 licence, $158,400/year support.

WebLogic on AWS and Azure: The Authorised Cloud Environment (ACE) Programme

Oracle's Authorised Cloud Environment (ACE) programme defines the terms under which customers can use existing Oracle perpetual licences (BYOL) on AWS and Azure infrastructure. WebLogic is covered under ACE. The ACE terms for WebLogic BYOL on AWS and Azure:

Licensing basis. WebLogic on AWS/Azure under ACE is licensed based on the number of vCPUs allocated to the virtual machine running WebLogic — with a ratio of 2 vCPUs = 1 Oracle processor licence. An AWS EC2 instance with 8 vCPUs running WebLogic requires 4 WebLogic processor licences. This is distinct from Oracle Database's ACE treatment, which requires licensing all vCPUs in the host (not just those allocated to the Oracle VM) — WebLogic has a more favourable cloud counting methodology than Oracle Database in ACE environments.

What ACE does not permit. ACE does not authorise BYOL WebLogic on Google Cloud. Google Cloud is not an ACE-listed cloud for WebLogic. WebLogic on Google Cloud requires purchasing new WebLogic licences at Oracle's cloud list rates — not reusing existing perpetual licences.

Oracle WebLogic Server images on AWS Marketplace and Azure Marketplace. Oracle provides pre-built WebLogic images on AWS Marketplace and Azure Marketplace with licence-included pricing (PAYG, no perpetual licence required). For organisations deploying new WebLogic capacity on AWS/Azure without existing WebLogic licences, Marketplace licence-included pricing is often more cost-effective for smaller instance counts than purchasing perpetual licences. For large existing WebLogic estates migrating to AWS/Azure, BYOL under ACE is typically more cost-effective.

WebLogic on OCI: BYOL and Licence Included Options

OCI is Oracle's preferred cloud for WebLogic deployments. Oracle provides WebLogic on OCI in two commercial models:

BYOL on OCI. Existing WebLogic perpetual licences can be brought to OCI VMs or OCI Kubernetes Engine (OKE) deployments. The processor count basis for OCI BYOL is OCPUs (each OCPU = 1 physical core = 2 vCPUs) — 1 OCPU = 1 Oracle processor licence. This is equivalent to the on-premises counting methodology and is more favourable than AWS/Azure vCPU counting in some scenarios.

WebLogic for OCI (licence included). Oracle offers a managed WebLogic service on OCI with licence included in the OCPU hourly rate. This eliminates the need for existing WebLogic perpetual licences and provides Oracle-managed patching and updates. The licence-included rate is appropriate for organisations without existing WebLogic licences or those consolidating middleware spend.

WebLogic on Kubernetes: The Soft Partitioning Problem

Oracle WebLogic Server Kubernetes Operator (WLS Operator) is Oracle's supported mechanism for deploying WebLogic on Kubernetes. The licensing rules for WebLogic on Kubernetes follow the same soft partitioning logic as Oracle Database on Kubernetes: if WebLogic pods can run on any node in the Kubernetes cluster, all cluster nodes' processors must be licensed. Node affinity rules, taints, and toleration policies that restrict WebLogic pods to specific nodes are soft partitioning controls — Oracle does not accept them as a hard partitioning boundary for licensing purposes. The only compliant approaches that limit WebLogic processor licensing to a subset of Kubernetes nodes are dedicated physical node pools that are physically isolated from the remainder of the cluster.