Oracle WebLogic and WebLogic Suite licensing in the cloud. Why the same cores can need twice the licenses.

On AWS, Azure and Google Cloud, Oracle counts WebLogic by vCPU and drops the core factor, so a lift and shift can double the license count. Right size the shapes, confirm the edition, and write the counting basis into your ordering document.

Oracle counts WebLogic differently in the cloud than in your data center, and the difference works against you. On AWS, Azure and Google Cloud the Processor Core Factor Table does not apply, so the same physical capacity can need twice the licenses it needed on premises.

This page covers WebLogic in every cloud, including Oracle's own. If your target is Amazon, read this one first, then the WebLogic licensing on AWS guide for EC2 instance families, autoscaling groups and Optimize CPUs.

• Support. The support stage question that runs alongside a migration is in the WebLogic support tiers guide.
• Database. The database follows the same counting logic, set out in the Oracle Database licensing guide.

What do you have to license when WebLogic runs in the cloud?

You license an edition, on a metric, for a number of counted processors. The cloud changes only the last of those three, but it changes it enough to break a business case built on data center arithmetic. The edition still deserves a fresh look, because cloud reference designs tend to push it upward.

Which WebLogic edition does a cloud design need?

WebLogic Server Standard Edition does not permit clustering. Enterprise Edition does, and adds dynamic clusters, failover, whole server migration and Java SE Advanced. WebLogic Suite adds Coherence Enterprise Edition, Active GridLink for Real Application Clusters and iAS Enterprise Edition on top of Enterprise Edition.

That boundary matters more in the cloud than on premises. Cloud reference architectures default to clustered designs spread across availability domains or zones, so an architect who draws a resilient design has also chosen an edition, usually without knowing it.

The WebLogic management pack is a separate purchase at every edition, including Suite. Budget it on the same counted processors if your operations team uses it.

When does WebLogic Suite licensing pay for itself?

Suite earns its premium only if Coherence Enterprise Edition or Active GridLink for Real Application Clusters actually run. The premium over Enterprise Edition is $20,000 per processor at list, before any cloud counting rule multiplies it. If your applications use neither component, Suite buys optionality you pay for every year in support.

Coherence ships inside every WebLogic release, which makes the question harder to answer from the installation alone. What you may run is set by the edition you hold, as the Coherence licensing guide explains.

• iAS Enterprise Edition. The iAS licensing guide covers the third Suite component.
• An open edition decision. For a migration where you can still change edition, see our note on choosing between Suite and Standard Edition.

Processor or Named User Plus in the cloud?

Processor is the default metric for anything reachable by an unbounded user population, such as a customer portal. Named User Plus is priced at $200, $500 and $900 for the three editions, with a floor of 10 Named User Plus per processor.

The floor rises with the count. Because the cloud counting rule inflates the processor number, it also inflates the Named User Plus minimum, so a small internal user base ends up paying for users it does not have. The Processor price rises faster, though, which makes Named User Plus relatively more attractive after a move.

• Where the break even sits. At all three editions, one Processor license costs the same as 50 Named User Plus. Below 50 named users per counted processor, Named User Plus is cheaper, and because the floor is 10, the floor alone can never make it the dearer metric.
• How the floor rises. Say an internal application runs on 16 physical x86 cores. On premises that is 8 processors and a floor of 80 Named User Plus. On a 32 vCPU cloud instance it is 16 processors and a floor of 160.
• What that costs at Enterprise Edition. The cloud floor of 160 users is $80,000 at list, against $400,000 for 16 Processor licenses. Named User Plus stays the cheaper metric up to 800 named users, twice the 400 user break even on premises.

How does the Authorized Cloud Environment rule count WebLogic?

Oracle counts vCPUs and ignores the core factor. The rule sits in Oracle's Licensing Oracle Software in the Cloud Computing Environment policy, which names Amazon Web Services, Microsoft Azure and Google Cloud as the Authorized Cloud Environments.

How are vCPUs converted to WebLogic Processor licenses?

Where hyperthreading is enabled on the instance, two vCPUs count as one Oracle Processor license. Where it is not enabled, one vCPU counts as one Processor license. The count is taken per instance and summed across every instance that runs WebLogic.

• An 8 vCPU instance with hyperthreading on needs 4 WebLogic Processor licenses.
• A 32 vCPU instance with hyperthreading on needs 16 WebLogic Processor licenses. At Enterprise Edition list that is $400,000 for one machine.
• Instance families without hyperthreading count one for one and double the cost of the identical vCPU count. This includes several Arm and high performance shapes. AWS Graviton instances have no simultaneous multithreading, and neither do the C7a, M7a and R7a families, where each vCPU is a physical core.

The last point bites during routine instance refreshes. A C6a instance with 16 vCPUs runs on 8 physical cores, while a C7a with 16 vCPUs runs on 16. Swap one for the other at the same vCPU size and the WebLogic count goes from 8 to 16 processors.

Why does the missing core factor double the count?

On premises you multiply physical cores by the factor in the Processor Core Factor Table, which is 0.5 for most x86 cores. In an Authorized Cloud Environment that table is expressly not applicable.

A 16 core x86 server on premises is 8 Processor licenses. The same 16 cores presented as 32 vCPUs in the cloud are 16 Processor licenses.

The OCI row follows Oracle's own bring your own license guidance, which maps one Processor license to two OCPUs. That row is why Oracle sales teams open almost every middleware migration conversation with OCI. Their case rests on the counting unit, and the compute price comes second.

Which clouds are inside the policy and which are not?

The policy names AWS, Azure and Google Cloud. Everything else, including VMware Cloud on AWS, private hosting providers and any sovereign or partner cloud, falls outside it and is treated as ordinary third party hosting under your existing agreement.

Outside the policy the core factor comes back, but so does Oracle's partitioning position, which usually means licensing the whole underlying cluster. For any provider not on the list, get written confirmation of the counting basis before the first instance is built.

Is Oracle's cloud policy part of your contract?

No. Oracle's cloud licensing document is published policy. It is not incorporated into the Oracle Master Agreement, it carries no commitment to remain in force, and Oracle has revised it before, including when Google Cloud was added.

Oracle applies the policy in audits, yet it can rewrite it before your next audit, and you have no contractual claim to the older version. For any material cloud deployment, name the conversion you relied on in the ordering document, which turns a policy you cannot enforce into a term you can.

What do the WebLogic Server for OCI images include?

They include the WebLogic binaries, the domain provisioning automation and the surrounding OCI plumbing. If you pick the bring your own license variant, they include no license at all. Oracle documents the stack in Using Oracle WebLogic Server for OCI.

Bring your own license or Universal Credits?

Two commercial models sit behind the same marketplace listing. Under bring your own license you are billed for compute only and you supply the WebLogic entitlement. Under Universal Credits the WebLogic Enterprise Edition or Suite license is metered per OCPU hour alongside the compute.

One asymmetry matters before you plan. WebLogic Server Standard Edition is available only as bring your own license, so there is no license included route to the cheapest edition. If the workload runs as a single instance, the saving only exists if you already own Standard Edition.

What the image gives you

• A provisioned WebLogic domain across compute instances, with the administration server and managed servers created by the stack.
• A supported release line. The current listings cover WebLogic 15.1.1, 14.1.2, 14.1.1 and 12.2.1.4. The 11g and 12.2.1.3 images were withdrawn from the marketplace in December 2021.
• Optional Java Required Files components for the releases that support them, which is what a Fusion Middleware layered product needs underneath it. Oracle's documentation excludes 14.1.1 and 15.1.1, so a JRF domain today means 12.2.1.4 or 14.1.2.
• Network and load balancer provisioning through the same stack, so the domain arrives with its networking in place.

What the image does not include

• A database. A JRF domain connects to an existing database in your tenancy, and you pay for it separately. That is a second license or subscription decision with its own cost line.
• Any other Fusion Middleware product. SOA Suite, WebCenter and the rest can be installed on the domain only if you already hold the licenses for them, and their own counting rules apply on top.
• A wider Coherence grant. Coherence ships with the WebLogic release, but the edition you hold still decides what you may run.
• OCI Vault. The stack stores domain passwords in OCI Vault, a separate service you must have in the tenancy.

What is the WebLogic restricted use trap, and does the cloud change it?

A restricted use WebLogic license may run only the Oracle product it was bundled with. Moving that product to a cloud does not widen the grant by a single application, because the restriction travels with the software, whatever infrastructure it lands on.

Where do restricted use rights come from?

Several Oracle products ship with a WebLogic entitlement scoped to themselves. Oracle applications, Fusion Middleware components and various Oracle appliances all do it, which is why so many companies hold WebLogic they never bought. The scope for each product is written in its Licensing Information User Manual, and that document is what an auditor reads.

How do cloud migrations break restricted use?

• Co deployment. A second, unrelated application is deployed into the same domain because the domain is already there and already running.
• Shared cluster. The restricted domain is folded into a shared cluster serving several business applications during a consolidation.
• Image reuse. The restricted build becomes the golden image, and every new instance in the cloud inherits an entitlement that does not cover it.

The cloud makes all three easier and all three more visible. Instance counts and images are logged, tagged and billed, so the evidence trail that proves a breach is the same trail your finance team built for cost allocation.

Does WebLogic include Java SE?

WebLogic includes a restricted Java SE entitlement scoped to running WebLogic itself. Using that Java runtime for anything else, including other applications on the same instance, falls outside the grant and lands in the Java subscription conversation instead. The Java SE coupling note covers how that surfaces during migrations.

For WebLogic, SOA Suite and Coherence priced side by side, see our guide to Oracle Fusion Middleware licensing.

What have we seen in WebLogic cloud migrations in 2024 and 2025?

In most of them, the migration business case was written before anyone read the counting rule. That held across roughly 25 to 35 WebLogic environments we reviewed between 2024 and 2025, and three problems came up again and again.

None of these came from the cloud provider. Each came from a sizing, purchasing or deployment decision made without a license number on the page.

Where do WebLogic cloud deployments overspend?

They overspend on shape, on edition and on environments no one counted, in that order and by a wide margin on the first. In an Authorized Cloud Environment the same x86 cores need 2x the licenses they needed on premises, so every one of these gaps is doubled too.

Which five cost leaks should you measure?

• Shape headroom. An instance sized for peak plus comfort carries every spare vCPU as a license. Right sizing the shape is the highest yield action available.
• Edition creep. Suite bought for optionality, then multiplied by the cloud counting rule. Once vCPUs are counted, the Suite premium is paid on twice as many processors.
• Non production sprawl. Oracle offers no free development or test entitlement for WebLogic. Every running non production instance counts.
• Standby and disaster recovery. Oracle's data recovery policy licenses every standby where WebLogic is installed, running or not. A standby stays outside the count only if WebLogic is not installed on it, or within the policy's allowance of ten separate days a year on an unlicensed failover spare.
• Orphaned instances. Machines left running after a cutover, still counted, still on the invoice.

Should you move WebLogic to OCI to cut the license count?

The usual advice is yes, because the OCPU arithmetic in the table above favors OCI. We disagree with using that as the reason to move. The arithmetic is correct, but it is the smallest term in the equation.

In the environments we reviewed, right sizing shapes and correcting the edition cut more than the counting difference between OCI and AWS. Both of those actions work on any cloud.

The cloud question is how many processors your architecture will be counted at, and whether you agreed that count in writing before you moved.

How do you price a WebLogic cloud migration before you commit to it?

Build the license line into the migration model at shape level, with one row per instance and a counted Processor number on each row. That table changes an architecture faster than any policy summary, because it puts a price next to each design choice.

A worked example with twelve domains

Take twelve WebLogic domains on Enterprise Edition, running on 96 physical x86 cores across production, test and a standby site. On premises that is 48 Processor licenses. Lift the same design to an authorized cloud on hyperthreaded shapes and it presents as 192 vCPUs, which counts as 96 Processor licenses.

Nothing about the applications changed between the first two rows. The license position doubled and the support line doubled with it. The third row is the one to put in front of the migration board, because right sizing is engineering work you control and it recovers most of what the counting rule takes away.

The fourth row shows why Suite deserves its own check before any move. On 96 counted processors the Suite premium comes to $1,920,000 in license value and $422,400 a year in support over Enterprise Edition.

Which three questions must the board paper answer?

1. What is the counted processor number for the target design? Give the counted number after the conversion rule, rather than the core count or the vCPU count.
2. Which edition does the target design require? Answer it from the cluster definitions in the target architecture, whatever you hold today.
3. What happens to the support base if the footprint shrinks? Oracle may reprice the remaining lines on a support identifier when quantities fall, so model the residual invoice after the reduction.

If the migration paper cannot answer those three, treat it as a compute plan and send it back.

How do you check which WebLogic edition and processor count you actually use?

Read the domain configuration and the instance settings, since those are what Oracle's auditors read. The purchase order tells you what you bought, while the running topology decides what you need.

Where the evidence sits

• Clusters. Each domain's config.xml lists its cluster elements, including dynamic clusters. Any cluster means Enterprise Edition or Suite. WLST or the administration console shows the same data for a running domain.
• Server and service migration. Automatic server migration settings and migratable targets in config.xml depend on a cluster, so they also mean Enterprise Edition or Suite.
• Coherence. Coherence cluster system resources in the domain configuration show where Coherence is configured. Compare what runs there with what your edition grants before you assume Suite is needed.
• Active GridLink. JDBC data sources defined as GridLink data sources, pointing at a RAC database, are a Suite feature.
• Threads per core. On AWS, the CpuOptions returned for each instance show CoreCount and ThreadsPerCore. On any Linux guest, lscpu reports threads per core. A value of 1 means every vCPU counts as a license.
• OCI shapes. The OCPU count on each x86 OCI instance, halved under Oracle's bring your own license mapping, gives the counted processors.
• Restricted use scope. The Licensing Information User Manual of the bundling product names what its WebLogic grant covers.

What will the Oracle account team say, and how should you answer?

Expect four lines in most WebLogic migration conversations. Each has a factual answer you can give without conceding anything.

Typical lines and replies

• "On OCI your licenses go twice as far." Reply that you will compare after right sizing, on the same architecture, and that any OCI order must record the two OCPU to one Processor mapping for the term.
• "The cloud policy is standard and we cannot change it." Reply that you are not asking for a change. You want the conversion you relied on written into the ordering document for these deployments.
• "A clustered design in the cloud needs Suite." Reply that clustering, failover and whole server migration are Enterprise Edition features, and ask which Suite component they believe will run.
• "Your standby site needs licenses." Agree for every node where WebLogic is installed, then show which nodes have no WebLogic installed and which failover spares stay within the ten day allowance.

Contract wording to ask for

• A named counting basis. State the vCPU conversion for each named cloud, with and without hyperthreading, so a later policy revision cannot change the count on deployments already made.
• Portability between locations. Confirm that licenses may move between your data center, the named clouds and OCI without a new purchase.
• A restricted use schedule. List each restricted WebLogic grant and the product it serves, so the scope is agreed before an audit.
• Standby definition. Ask for a cold standby node, with WebLogic installed but not started, to be written in as unlicensed. Oracle's default policy counts installed software, so this term has to be negotiated and is worth real money on a second site.
• Support pricing on reduction. Get the residual support fee in writing before you terminate any lines on a support identifier.

For the clause language itself, see the Oracle contract clause guide.

How does Redress help with WebLogic cloud licensing?

We map feature use to edition, separate restricted use from full use, and convert the target architecture to a counted processor number before the migration is committed. We do not resell Oracle and we do not implement it.

WebLogic advisory runs inside the Vendor Shield subscription, the Renewal Program and the Benchmark Program, led by a former Oracle licensing executive. For the wider picture see the Oracle services page, the Oracle knowledge hub and the benchmarking page. To have a position reviewed before a board date, use the contact page.

What to do next

1. Inventory every WebLogic instance. Record edition, version, host and whether it is production, non production or standby, including the instances no team claims.
2. Extract the cluster evidence. Cluster definitions and the running managed server topology decide the edition. The purchase order does not.
3. Separate restricted use from full use. List every WebLogic entitlement that arrived bundled with another Oracle product and name the product it is tied to.
4. Convert target shapes to processors. Apply the vCPU rule for the destination cloud before the shapes are chosen, and put the license number in the same table as the compute price.
5. Test each shape one size down. A shape that drops from 16 to 8 vCPU removes 4 Processor licenses and about $22,000 a year of support at Enterprise Edition list.
6. Model three routes side by side. Price on premises, an authorized cloud and OCI for the same architecture, so the counting difference shows as a number.
7. Write the counting basis into the ordering document for any material deployment, so the conversion becomes a contract term.
8. Time the renewal against the migration. Signing a support renewal before the target position is agreed gives away your negotiating room for the next term.

Frequently asked questions