WebSphere Liberty Licensing Explained

WebSphere Liberty is the lightweight runtime that replaced the heavyweight traditional profile for many teams, but lightweight in architecture does not mean simple in licensing. The edition you deploy and the entitlement behind it decide whether a given install is free, bundled, or fully chargeable. The runtime is small, the licensing question is not.

Liberty is a runtime, not a single license

Liberty ships in more than one form. There is an unsupported free runtime intended for development and certain limited uses, and there are licensed editions that carry full production entitlement and support. The same Liberty server can therefore be perfectly compliant or completely unlicensed depending on which edition was installed and what the deployment is doing. The audit question is rarely whether Liberty is present, it is which Liberty and under what entitlement.

How the licensed editions are metered

Production Liberty editions are licensed on capacity metrics in the same family as the rest of the WebSphere portfolio. That means PVU, the core based metric where value units per core times allocated cores set the quantity, or VPC for the editions and bundles that meter on virtual processor cores. Since Passport Advantage v11, VPC metered products carry sub-capacity reporting obligations and manual counting is no longer permitted, so a Liberty deployment on a VPC entitlement needs an approved reporting tool just as a PVU deployment does.

• Free runtime used in production: a deployment that needs a licensed edition behind it
• PVU edition: value units per core times the cores allocated to the server
• VPC edition or bundle: virtual processor cores, with sub-capacity reporting required
• Mixed estates: free and licensed Liberty side by side, easily miscounted

Where Liberty audits go wrong

The recurring trap is the free runtime quietly carrying production load. Because Liberty is easy to install and bundle into application images, instances multiply across environments without an entitlement check. In a container estate, a Liberty image replicated across an OpenShift cluster compounds the problem, and a sub-capacity reporting gap there can convert the finding to all cores in the cluster. ILMT or the IBM License Service must see every licensed instance, or the period without reporting defaults to full-capacity.

How buyers defend it

We inventory every Liberty instance, classify each as free runtime or licensed edition, and match the licensed ones to entitlements and the correct metric. Where a finding counts free runtime instances as chargeable without evidence they carry production load, the classification is the counter. Where licensed instances ran without reporting, we rebuild the sub-capacity record from continuous ILMT or License Service data wherever it exists, and correct any miscategorized installs before the number is set.